search

visicraft / visicraft-web

0 stars 0 forks source link

Future: Split UI Components #12

Open novacbn opened 4 years ago

novacbn commented 4 years ago

Description

As some cleanup and for organizational purposes, all the custom UI components should be split off into a separate package called visicraft/visicraft-ui. That way it can be separate developed and iterated on without affecting visicraft-web. And for slimming down the scope of visicraft/visicraft-web.

novacbn commented 4 years ago

As a quick follow-up, not only should the general UI components be split into visicraft/visicraft-ui. But also, after MVP and when appropriate, create custom Svelte bindings of Luda CSS under visicraft/svelte-luda. With a full re-implementation of any JS logic needed, to run it without Luda's provided CSS files.

This should wait til after the feature/next branch of the framework is done, presumably when it's released as v0.3 (or whatever it ends up being).