4 ms·
What you're describing is an extensible component model, which any sane application framework has, but HTML sadly doesn't. As a result, re-usability is a first
by seanalltogether 9y ago
What you're describing is an extensible component model, which any sane application framework has, but HTML sadly doesn't. As a result, re-usability is a first class feature and not something that has to be hacked in. XML based UI builders allow for view tree to be composed of vendor or user custom components.
<HorizontalLayout gravity="top">
<MyCustomSideBar id="menu" height="100%"/>
<VerticalLayout gravity="center">
<Text>Enter a starting date for search</Text>
<MyCustomCalendar id="calendar"/>
</VerticalLayout>
</HorizontalLayout>
- space_fountain 9y agoI thought I'd replied but it looks like not. What's missing for me in these systems seem like they don't usually map the program to manage the behavior of the widget with the layout of the widget. Am I wrong? I really like that I can build a custom widget that encapsulates the entire behavior of the widget not just how it looks.