PHP stays the program: JumPHP\Tauri\App starts the Tauri runtime (tauri/, a Rust C library loaded with FFI) from its main thread; Tauri runs its native loop there and calls PHP back at every frame, like the browser engine. Pages talk to PHP with window.jumphp (invoke / send / on); PHP drives windows, dialogs, notifications and decides what closing does. Native only, Linux for now. - tauri/: libjumphp_tauri (jt_run / jt_poll / jt_send / jt_version), pages served from the app's folder at run time - engine: JumPHP\Tauri (App, Window, AppMain, TauriRuntime, FakeRuntime, NativeCommands), JumPHP\Native (Dialog, FilePicker, Notification, Shell; providers tauri / sdl / browser / none), Testing\AppTestCase (no window) - bin/jumphp app:new / app:run / app:test / app:shot / app:export, tauri:setup / tauri:build (tools/app-commands.sh); run / test / shot hand over to them for an app, pages skips apps - app:export: export:standalone with optional settings (extension list with FFI, boot class, native library, injected php.ini); unset, games build and find the same micro as before (same key) - skeleton-app/, games/hello-desktop (a notepad), docker/tauri, docs/tauri.md + docs/tauri.fr.md, AGENTS.md §16 Nothing changes for SDL games (desktop, browser, standalone, Android, Apple). Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01JkYTqpYNZKwTnRZHQRD5HP
1 line
81 B
Text
1 line
81 B
Text
bcmath,phar,zlib,mbstring,ctype,tokenizer,filter,sockets,openssl,pcntl,posix,ffi
|