This website requires JavaScript.
Explore
Help
Sign in
andodeki
/
makepad
Watch
1
Star
0
Fork
You've already forked makepad
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
nigig-traffic-camera-boom-fix
makepad
/
widgets
History
Download ZIP
Download TAR.GZ
Exact
Exact
Union
RegExp
andodeki
b580de105b
fix(fork): refresh widgets from upstream work + re-apply sibling reexports
2026-09-26 03:20:34 +03:00
..
derive_widget
platform: topic hunks the per-commit assembly could not place, the Sep 2–15 dev PRs (#1208–#1236) as adapted to this tree, and the zero-warning chore
2026-09-15 13:40:33 +02:00
fonts
font change
2026-02-19 15:36:56 +01:00
resources
widgets, storybook: the widget catalogue app, some eighty new widgets, a theme store with mixable style sheets, and the rule that a press belongs to whatever took it
2026-09-18 22:56:31 +02:00
src
fix(fork): refresh widgets from upstream work + re-apply sibling reexports
2026-09-26 03:20:34 +03:00
test
splice out a makepad-network crate
2026-02-23 23:21:31 +01:00
tests
platform: render-loop fixes from review, the remote gate,
--focus
, and owned state instead of globals
2026-09-18 12:15:08 +02:00
themes
wm on Android: every app is its own process -- the plain makepad-wm now ships as an Android APK (
cargo makepad android ... proc-pack -p makepad-wm-android
) whose phone apps run as real child processes instead of dylibs loaded into the WM. The interface between WM and app shrinks to what the desktop WM uses: shared GPU buffers and the StudioToApp/AppToStudio protocol. The WM allocates each app's swapchain as AHardwareBuffers and hands them over a unix socket (AHardwareBuffer_sendHandleToUnixSocket, API 26); the child, started through the
libmakepad_launch.so
launcher in nativeLibraryDir (W^X allows it there), imports them into a windowless Vulkan device and renders its window pass into them (android_hosted.rs). Each app library links the engine statically, so the engine-dylib identity handling of wm-dyn is not needed. Children have no JVM: assets are read from the APK file, audio device lookup no longer goes through Java, and the startup/resize extra draw of the Activity build is repeated so the first frame carries its text. On a phone the WM asks for the soft keyboard only while the child reports a focused text field. Proven on a Pixel 11 Pro XL: all twelve phone apps launch as processes (first frame 1.6-2.4 s cold), taps reach them. Not yet: HTTP in children (the Activity build borrows Java's), clipboard/permission/file-picker relays, idle-app reclaim, and on-device builds of app libraries
2026-09-23 22:34:44 +02:00
build.rs
voice input
2026-02-19 14:13:07 +01:00
Cargo.toml
Merge upstream origin/work
5f99533
into nigig fork alongside dev
2026-09-25 17:32:26 +03:00