3 ms·
I think where xml based layouts have always seemed lacking to me is re-usability. With React.js say I can make a special widget to handle calendar input. It cou
by space_fountain 9y ago
I think where xml based layouts have always seemed lacking to me is re-usability. With React.js say I can make a special widget to handle calendar input. It could be built from an assortment of html elements + code. I don't see a good solution to duplicate the amount of reuse this allows in a different pariadime.
Maybe I don't understand what you're saying, but it can feel almost like advocating for putting everything in one function. Following the execution through all the functions and methods is a nightmare you might say, but the point is not to follow it through all those layers in the vast majority of cases. The point is to enable a higher level of abstraction that means you don't need to look at those lower levels unless you actually have to change something there.
- seanalltogether 9y agoWhat 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.
- pjmlp 9y agoCreating reusable components in XML layouts has always been a feature, for example XAML and Facelets.