Skip to content

Search

返回
· 閱讀時間 1 分鐘

The editor in the browser

The editor runs in a browser tab on the WebAssembly module the examples play on, keeps the project in IndexedDB, and exports a pack.

The editor runs in a browser tab, on the WebAssembly module the examples play on. The project lives in IndexedDB. Export writes a pack.

  • The examples play in the tab on WebGPU.
  • balaurengine.org/editor opens on an example or on a local folder, and returns the project as a zip.
  • The project is kept in IndexedDB, textures and sounds included, and survives a refresh.
  • Export writes a .bpak, or a web bundle zipped beside the running module. Native targets need a linker.
  • ui::set_lazy runs the shell pass only on input, a log line, a reload or an animation. An idle frame went from 7.2 ms to 4.8 ms.

Not in the tab

An account and a project kept on Gamend, native export, a linker and a signing toolchain, and the debugger. PLAN-web-editor.md has the order. Build size has the module's weight and how to make a smaller one.