* Make `tauri build` just work
* Move folder: frontend/wasm -> wasm
* Create SvelteKit project with 'npx create-svelte'
* Move wasm-communication into seperate npm package
* Use wasm-pack directly and pack package.json
* Got it to work
* Add primitive build script for wasm npm module
* Fix wasm build script (python)
* Clean up glue code
* Rewrite wasm build script in node.js
* Add serde-reflection to trace types
* Add traced types
* Generate typescript (.d.ts) from Rust types
* Update .d.ts
* Finalize TS types
* Add script to update .d.ts
* Add watch command to build wasm-bindgen
* Make wasm work again
* Add sass; fix build script for windows
* Describe requirement for wasm-pack
* Add license
* Copy and reorganize vue components
* translate LayoutCol.vue
* Split app.scss into pieces
* Translate LayoutRow.svelte
* Rename scss files
* Fix compile issues on Windows
* WIP port TitleBar
* Support classes for LayoutCol/Row
* Restructure based on Vue codebase
* Port all components in window folder
* Port FloatingMenu
* Port Document panel component
* Update readme after folder move
* Update typegen: print discriminant by default
* Update typegen: Merge from branch 'tailwind' 4f14fedb
Fixes bigint & bytes
* Made Vue/webpack/eslint to accept wasm package at new location
This is quite a hack.
Those two packages are both named the same. Yes, it's an npm package inside another npm package.
- frontend/src/wasm-communication/
- frontend-svelte/glue/
'wasm/pkg/index.js' imports the correct one registered when linking.
* Port LayerTree
* Port NodeGraph
* Port Properties
* Port components in /floating-menus
* Finish porting all Vue -> Svelte components
* Change import prefix
* Revert type generation
* Revert moved wasm folder
* Revert all of @locriacyber's work on this branch
- Remove Vite and restore Webpack
- Remove SvelteKit
- Remove everything except the components I ported to Svelte
- Restore all frontend files from Vue code, now altered for Svelte
* Convert Vue's 'reactive' and 'provide' to Svelte's stores and contexts
* Fix event emitting and bi-di data flow
* Undo removal of 'update:' events
* Fix 'update:' event dispatching
* Fix usage in parent of bi-di component props
* Fix component typing, more progress towards no errors
* The page builds and opens!
* Add loading spinner and remove postcss dependency
* Make the basics of document editing work
* Fix rebase history
Co-authored-by: Locria Cyber <74560659+locriacyber@users.noreply.github.com>
Keavon Chambers
TrueDoctor