4 major design choices Makepad’s architecture highlights can be summarized in 4 major designs choice Live designable/codeable UI DSL for all styling and structure co-developed with a realtime IDE/visual designtool. It is Delphi/Visual Basic but for Rust. Immediate mode drawing flow to draw all 2D shapes and output directly to the GPU’s instanced drawing APIs (https://www.youtube.com/watch?v=Ude1zZbf20s) keeping CPU cost very low. No vector processing needed. Shader styling language integrated in UI DSL to style and animate widgets with simple familiar canvas-like API running on GPU Support a mix of immediate mode and retained mode in terms of UI state management so you can choose the optimal form for your problem. Immediate/Retained mixing enables complex widgets (editors, infinite scrollviews, graphs) 1. Live designable/codeable UI DSL for all styling and structure co-developed with a realtime IDE/visual designtool. Think delphi/visual basic for Rust. Use the 'live' connection of makepad studio or write it by hand in vscode to update the application in real-time. Real time live update speeds to iterate the UI design with either a visual designtool (WIP) or code editor

The system should be able to perform automated performance benchmarking tests with minimal manual steps. The two applications currently needs testing are: MockTaoBao: to test scrolling performance comp_demo: to test performance of different UI animation effects Data Points The performance tests should collect the following data metrics:

Makepad is a cross-platform UI framework written in Rust. It is in active development, but is already usable to build quick prototypes and simple (or even complicated UI) applications. One of the key features of the Makepad is its ability to simply, and quickly, build and run applications on multiple platforms, including MacOS, Windows, Linux, Android, iOS, and WebAssembly. Here are the current/latest instructions on how to build and run Makepad applications on the different platforms. Assumptions We will assume the following: Name of application: makepad-example-simple

Yesterday I wrote a post detailing specific instructions on how to build and run Makepad apps on IOS and Android devices. This post is a quick reference that lists most the commands, including sample commands for specific apps in the project-robius repo. For more detailed descriptions, please see: Makepad Build Commands Cargo Tools Installations These are commands that need to be run at least once initially to setup Makepad development environments. They should also be run once in a while or when there are updates to the cargo_makepad script. I personally run them about once a week.

Makepad is a cross-platform UI framework written in Rust. It is in active development, but is already usable to build quick prototypes and simple (or even complicated UI) applications. One of the key features of the Makepad is its ability to simply, and quickly, build and run applications on multiple platforms, including MacOS, Windows, Linux, Android, iOS, and WebAssembly. Here are the current/latest instructions on how to build and run Makepad applications on the different platforms. Assumptions We will assume the following: Name of application: Sample_App

Makepad Widgets is a set of commonly used UI elements toolkit that works with the Makepad ecosystem as part of the Makepad Framework. It is integrated wtih the Makepad Live Designer and Code Editor, as well as the rest of the Makepad Framework. It allows application developers to easily use these UI widget components to build and compose their UI application. Overview A modern GUI application framework should provide a basic set of easy to use widgets or UI components that allow the developers to quickly build the application user interface by combining these widgets. The basic widgets usually contain, at the minimal, support for HTML elements, with additioanl layout support. Additional components are usually provided as well from either the frameworks or via community development. The number of supported widgets for a mature GUI framework will usually be in the hundreds.

There are currently 2 versions. First one is short and sweet and can be put up now. Second one is more full blown (but needs some work toward the end), which I think can be used later after the project official release. VERSION 1 - Short version Contributing to Makepad First, thank you for considering contributing to Makepad. It's people like you that make the open source community such a great community!