You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code itself would be cleaner, but current tools often introduce a toolchain which Contibutors need to be (partly) familiar with, as well I (@jdittrich) would need to learn more about them.
More toolchain means often higher barriers for contributors.
Minor, but: Currently data and view are one thing. Sounds horrible, has the advantage that we don't need to convert anything. With a "proper" separation, we need a mechanism to read-from-HTML and write-to-HTML. Not rocket science, but I want to keep a) files and b) the sharing- and browser-friendly file format and not make people save and pass a JSON file or so.
The text was updated successfully, but these errors were encountered:
I wish I could, but I haven't worked that much with it, in that way
I've only used it in already created environments, where I would only have to create a template and loops etc.
I want to rewrite quickMockup to use Vue.js. I hope to achieve the following advantages:
Also I hope to resolve the following bugs more easily. They could be solved now, but they would introduce a huge amount of spaghetti-code:
Possible Problems:
More toolchain means often higher barriers for contributors.
The text was updated successfully, but these errors were encountered: