036fa2fd86
App and example changes, with the apps that moved to the Stage repository (apps/vj, apps/asset-ui) removed here. Covers work 6f1e44649..2b1a41df4 for apps examples: - wm: the Android super-app compiles tiles on the phone against the host engine - cargo-makepad: the super-app APK is packed by `android dyn-pack`, in Rust - 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 - wm, widgets: the style tween starts with all eight weights, and the new style sheet takes the last number instead of macOS's - platform: the Android desk swipes at 120 Hz — offscreen render passes and framebuffers cached, SVG meshes kept, font families that complete - flow: the flow-ui app and the flowgraph canvas return to the workspace, with staged progress in libs/flow - app_main!: only ship the fonts an app declares (#1247) - platform, widgets, wm: every Vulkan pass renders through a negative-height viewport again, so a Wayland or X11 window stands upright, and no capture - calendar: its own colour contrast is named explicitly, now that the theme store exports one under the same name through the widgets glob - platform, wm, director: a hosted app's software frame arrives as a top-left texture and the window manager and the director carry no flip term at al - wm: the desktop style menu lists each style once - cef, video, platform: what Stage's browser needs from the shared layers - platform, wm: work builds again on iOS, tvOS and wasm, and the window manager is warning-free on Windows - ci: tools/ci, a Splash runtime that watches a branch and runs every ci.splash it finds - ci: the terminal gets its pty helper, director is a desktop tool, and a refused input is asked again - apps: what the CI box found - Remove Flow, asset and VJ applications moved into Stage - ci: a quiet header, a build that visibly moves, and scripts that leave the machine alone - tests: the workspace suite, run as a whole for the first time, passes outside the example UI tests - examples: the UI tests pass, for the reasons they failed - tests: the last three failures of the CI box's night - tools: makepad-screen is makepad-agents, and its binary is `agents` - tests: the three binaries over ten seconds in release come under it - wm: the shell menu says what it did, and the CI waits for that - mail: the phone layout lines up - clock: the phone layout fits both orientations - calendar, reminders, calculator, sheets: the phone layouts fit their space - platform, widgets, wm: a touch that is taken away is cancelled, never released - weather, notes, finance, photos, route: the phone layouts tidy up - files: the phone layout tidies up - wm: the phone shell's surfaces match the app and the grid - wm on Android: every app is its own process - clock: a cancelled release neither opens an alarm nor switches tab - platform, wm: hosted apps ask the WM for what they cannot do themselves - wm on Android: apps build on the phone - wm on Android: app transitions and gestures feel like the phone's - android: rotated Vulkan windows stop rebuilding their swapchain every frame, and hosted children get touch - android: hosted children hand frames over with GPU fences and draw only when they have work - wm on Android: gestures and surfaces settle like the phone's - widgets: touch lists scroll with Android's physics - wm on Android: the shell follows the Pixel launcher's motion - wm on Android: Recents shows the apps over a receding home, and the home screen switches looks - wm on Android: the look switcher stays put, the iOS dock shows its icons, background apps follow a look change - task, cargo-makepad, widgets, audio: the task manager chooses its columns, graphs every process' network and disk traffic and installs itself as a D - files: the tile view's three projections are toolbar buttons - mail: the local view takes a theme-derived palette and line icons, search pages share records - director: agent lanes form a tree and Grok joins the usage bar - widgets, draw: skeuomorphic surfaces light each other through an optional relief buffer - widgets, platform: a texture can light the relief buffer, menus take colour chips, and a style reload recompiles changed shader functions - platform, widgets, audio_route, ai: window crossfades and whole-frame presents, caption controls that click, themed menus, a stereo-pair audio tap, - builder: the Builder TUI matches the new terminal design, Windows executables carry app icons, and every app has one - files: the Files app deletes nothing and never overwrites - director: coding agents ask before acting unless you choose otherwise - sheets, score, git, home: saves cannot cut a file short or overwrite another one, and checkouts cannot write outside the repository - widgets, builder: the big widget families are features, all on by default, and the Builder takes none of them - ai: Claude Desktop drives any app with the F10 panel - wm: starts on Windows - wm: children open no console windows on Windows - wm: the whole deck out of a Builder's source, compiled only when the person opens an app - ai: Connect hands the .mcpb to Claude Desktop itself - wm: the clock and calendar know the date on Windows - wm: opening an app rebuilds it when its binary is out of date; warm instances never build - civil-time: one local wall clock for every app, and it knows the zone on Windows - platform + wm: a hosted child redraws at its tile's new size - calendar: the Calendars sheet is an opaque panel, and the wide layout does not float one over its sidebar - platform: an app's package dir, icons and bundle name rebuild only that app - build: the AI stack, csg, Scope and Source Library join the one workspace - ai chat: the chat's backends are the CLI, MCP and cloud providers; the local model is the `localai` feature - apps: every app that hosts the chat has a `localai` feature for the local model, off unless the app's own job runs one - widgets: every widget family is a crate of its own under widgets/families, and makepad-widgets links, re-exports and registers the ones its features - aichat, widgets: the chat reads the design feedback through the tweaker's hook, so linking the chat no longer needs the tweaker - apps, examples, libs: each crate builds only the widget families it uses, and the design overlay is each app's own default feature - ai chat: a build without local AI starts on the first provider that answers here, not on "No model" - repo: no third-party comic archive, generated models or sample asset in the tree - remove big example media files - wm: in a Makepad Builder installation apps build through the Builder, however wm was started Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
24 lines
1.7 KiB
Text
24 lines
1.7 KiB
Text
// CI smoke test for apps/calendar. Run by tools/ci, which finds every `ci.splash`
|
|
// in the checkout. The script decides every input; the vision model only
|
|
// judges the grab against the acceptance text below. Basic on purpose: does
|
|
// it check everywhere, build and come up here, and look like what it is.
|
|
|
|
use mod.std.*
|
|
use mod.ci;
|
|
|
|
ci.step("check other platforms", fn(){
|
|
ci.check_targets({packages: ["makepad-calendar"] targets: ci.host.targets})
|
|
})
|
|
|
|
let app = ci.launch({package: "makepad-calendar" binary: "calendar" cwd: "."})
|
|
|
|
ci.step("comes up", fn(){
|
|
ci.sleep(3.0)
|
|
app.no_errors()
|
|
let shot = app.grab("start")
|
|
ci.accept(shot, "This is a screenshot of one application window taken from a Mac. A thin bright red frame runs around the very edge of the picture; it is the test harness's marker and is not part of the application. Ignore it. The application is a calendar. It came up when these are true: 1. The picture is not blank: it is not one flat colour from edge to edge, and it is not entirely black or entirely white. 2. Some user interface is visible: at least two different things among text labels, buttons, icons, panels, lists, input fields, a toolbar, a drawing or a picture. 3. No error panel covers the window: there is no large block of text with words such as panic, error, failed, backtrace or unwrap. 4. A calendar is visible: a grid of days with day numbers, or a week view with hours down the side. Write one short bullet line for each numbered point saying what you see. YES means points 1, 2, 3 and 4 are all satisfied. Then write the verdict as the last line, in exactly this form: VERDICT: YES or VERDICT: NO")
|
|
})
|
|
|
|
app.no_errors()
|
|
app.quit()
|
|
nil
|