Timelines are often used in novel writing. For example, the timeline workflow in Manuskcript. The concept can serve a similar purpose in writing historical articles but would probably hinder writing math proofs or technical manuals. For an editor, the feature should be accessible but hidden by default.
CSS is arguably the best means of UI customization.
Consider an example of graphic-editing of UI elements:
https://initialaudio.com/how-to-skin-sektor/
Using CSS, all elements in that project could potentially be done without graphics.
Prospractically all designers now know CSSit's vastly capable Conscan't really decouple CSS from HTML whereas HTML is the biggest performance bottleneck (we'll solve this using different means) The Problem Unfortunately, CSS can get incredibly bulky. So what if we could design using CSS in a way that could feasibly be compiled to a local app?
In general, everything would be styled using CSS, in the same bulky way it exists in browsers. But when compiled, it's no longer bulky.
Benefitswe have the full flexibility of CSS for all appswe have the full speed of native apps if needed
Consider an example of graphic-editing of UI elements:
https://initialaudio.com/how-to-skin-sektor/
Using CSS, all elements in that project could potentially be done without graphics.
Prospractically all designers now know CSSit's vastly capable Conscan't really decouple CSS from HTML whereas HTML is the biggest performance bottleneck (we'll solve this using different means) The Problem Unfortunately, CSS can get incredibly bulky. So what if we could design using CSS in a way that could feasibly be compiled to a local app?
In general, everything would be styled using CSS, in the same bulky way it exists in browsers. But when compiled, it's no longer bulky.
Benefitswe have the full flexibility of CSS for all appswe have the full speed of native apps if needed
Comments
Post a Comment