flutter3d_app 0.6.0 
flutter3d_app: ^0.6.0 copied to clipboard
Published 5 days ago • 
pleion.dev
pleion.devThe layer an application is assembled from, as one import: which device to open, the frame surface and run lifecycle, the screens that are not the game, and the input devices Flutter itself does not cover.
0.6.0 #
- Floors, and no code. Storage, settings, the frame clock and the screens
are byte for byte 0.5.0's.
flutter3d_backend,flutter3d_sessionandflutter3d_screensmove to^0.6.0;pad_inputandpointer_lockstay at^0.4.0, which their 0.4.1 covers. - What arrives through the barrel is one line wider without this package
changing.
flutter3d_backend0.6.0 can try WebGPU on a web build given--dart-define=FLUTTER3D_WEBGPU=true; an application assembled from here gets that by raising the floor and nothing else, becauseopenDevicewas always the whole of the question this layer asks.
0.5.0 #
- No API change. Its floors move to the 0.5.0 packages it assembles.
0.4.0 #
- No changes of its own; the version moves with the workspace, whose sibling constraints name a single release. The README's closing section now says what the engine around this package is.
0.3.0 #
- A barrel over
flutter3d_backend,flutter3d_session,flutter3d_screens,pad_inputandpointer_lock— the five packages an application assembles itself from, none of which know about each other. No code of its own.
Metadata
0
likes
140
points
252
downloads
Documentation
Publisher
Weekly Downloads
Metadata
The layer an application is assembled from, as one import: which device to open, the frame surface and run lifecycle, the screens that are not the game, and the input devices Flutter itself does not cover.
Homepage
Repository (GitHub)
View/report issues
Contributing
Topics
#game-development #game-engine #application
License
MIT (license)
Dependencies
flutter, flutter3d_backend, flutter3d_screens, flutter3d_session, pad_input, pointer_lock