Skip to content

Prototype Web UI Framework #3

@mreschke

Description

@mreschke

Need to experiment with many different front end technologies.

No Build, No SPA

  • Alpine JS is pretty cool, less boilerplate than vue.js but similar API. No build, CDN style
  • Could use vue.js, no build CDN style, but more boilerplate than alpine but ONE framework to learn, will work later for SPA.
  • Bootstrap no build, but like tailwind. Is tailwind efficient without a build?
  • Pros of no build
    • No build, quicker dev and instant preview
    • Simple, quick and easy code
  • Cons of no build
    • Bulky assets especially tailwind
    • Must use non build JS, no imports, no modules. JS can be in jinja template or separate file, just not with imports. Or can browsers support import now?
    • UI is now tightly coupled with backend. Can't convert code to electron... more rigid and less portable and re-usable.

Build, SPA or not

  • Webpack with or without laravel elixer (mix)
  • Optimized tailwind
  • Less inline vue.js, now in own folder, with actual import modules, could still be NO SPA
  • Can do full SPA now. If full SPA, could just use NO uvicore for UI, separate projects completely, vue CLI style. Or could add to uvicore repo if wanted combined.
  • Pros of build
    • Full ECMA JS, imports, modules, separate folder structure...
    • Optimized assets, especially tailwind
    • If SPA, code is uncoupled from uvicore, can be separate repo. Could port to electon. More portable. Single concern.
  • Cons of build
    • Another watch process, slow to preview
    • If SPA, must use REST API, complex auth. APIs more complex than backend ORM queries pushed to templates.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestuiWeb UI

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions