Repository navigation
Add UIFlow workbench and validate controls across browser devices - #165
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The browser could run reference firmware, but lacked a validated way to edit and run UIFlow code across its admitted devices. This adds a default UIFlow2 programming environment and MicroPython editor for all 19 browser-runnable devices.
Validation
Scope and remaining limits
Policies require their exact Flash, startup source, fixture, ready marker and patch. Unknown firmware and fixed/classic images retain separate contracts. RUNTIME-07/08/09 remain OPEN; policy passes do not prove a shared C root-cause fix or long-term stability.
PM1 acceptance uses explicit application configuration: a 500 ms click window with unchanged 250 ms input. StopWatch/StickS3 use their public driver; PaperColor/PaperMono explicitly use public I2C RMW. Default-mode PM1 events are not established. Cardputer Fn pointer input includes a grave-key companion. Missing held-iframe CDP fences remain NOT CAPTURED.
Independent local cold samples on the same original fixed images changed from 109.458 to 54.775 s (Matrix) and 90.687 to 39.144 s (Plus). These are source-pinned, single observations for those two images.
Four original-image cold-prime → retained-page warm pairs completed: 53.491 → 76.480 s (75 Matrix), 39.378 → 63.627 s (75 Plus), 109.448 → 108.710 s (3c Matrix), 96.703 → 111.456 s (3c Plus). Warm includes model reconstruction; pure-cache and general speed guarantees remain unestablished. The first observer failure is retained. The two-guest functional gate is not a performance benchmark.
SDK pthread cancellation remains unestablished. Main merge, Pages publication and online acceptance are NOT RUN and await approval; physical equivalence is not claimed.