Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

XMLUI

blog.jonudell.net

Post reply on HN
Print view View original

21–30 of 345 posts

Re: XMLUI

#21

Post by sheepscreek »

danielvaughn wrote: post #15

Crazy, I just spent the past month designing an XML syntax for defining components. Weird coincidence. One issue I see in their choices is the HStack approach. What’s great about flexbox in CSS is that the flex direction can change dynamically. Admittedly I haven’t read the full docs for XMLUI, but binding the direction to the markup likely means you can’t do that.

While flexbox is more powerful, those semantics would require prior knowledge of other CSS attributes and to develop an intuitive understanding of them.

Re: XMLUI

#22

Post by 38 »

WillAdams wrote: post #9

Impressive that they note: https://docs.xmlui.com/ >This site is an XMLUI™ app. but like pretty much every such system, it is assumed that one knows react and so forth, and how to manage a deployment --- if they really want to be compared to VisualBasic, what is the equivalent to: - buy VB - install VB - launch VB - develop app - test/compile - distribute .exe Probably I'm not the target audience, but if they had a "…

[dead]

Re: XMLUI

#23

Post by thisislife2 »

Seems like we keep reinventing the wheel - the previous version of of HTML, XHTML (eXtensible HyperText Markup Language) is a direct subset of XML. Also, related - Mozilla Firefox used to have something called XUL (XML User Interface Language - https://en.wikipedia.org/wiki/XUL - using which you could build complete desktop web applications with the Firefox / Gecko web engine (something that is now popular with the Chromium Embedded Framework). (After Mozilla abandoned the XUL codebase, it has been forked and is now maintained as the Unified XUL Platform (UXP) implementation - https://forum.palemoon.org/viewtopic.php?f=46&t=30840 ).

Re: XMLUI

#24

Post by danielvaughn »

cheschire wrote: post #3

No mention of XSLT? Feels like it would be highly relevant since many folks have not considered transforming or styling XML since those days, and would be interested in understanding the huge leap from that to this. And given Jon Udell has written about XSLT before[0], I'm sure this was an intentional decision. Not sure I understand it though. 0: https://www.xml.com/pub/a/2003/08/13/udell.html

It’s probably irrelevant to an introduction. I think in this post the goal is to explain to a modern audience why something like this is beneficial. XSLT is part of the history here, but including it wouldn’t help sell the idea.

Re: XMLUI

#25

Post by sheepscreek »

cheschire wrote: post #3

No mention of XSLT? Feels like it would be highly relevant since many folks have not considered transforming or styling XML since those days, and would be interested in understanding the huge leap from that to this. And given Jon Udell has written about XSLT before[0], I'm sure this was an intentional decision. Not sure I understand it though. 0: https://www.xml.com/pub/a/2003/08/13/udell.html

The performance of available XSLT translation engines would be a big consideration for me, especially in a hot-reload context to support fast iterations.

Re: XMLUI

#26

Post by airstrike »

criddell wrote: post #16
yoz-y wrote: post #8

As a programmer I found that all no-or-less-code approaches break up sooner than one would expect. Eventually I chosen to always use the programming language itself for data fetching, looping and leave the templating (lit html in my case) to just passing in the data structures.

I've also seen examples that are pushed way further than I thought possible. I'm thinking about some of the things people do in Excel.

Spreadsheet is a form of programming, so you can build anything there.

Re: XMLUI

#27

Post by righthand »

Cool looking but it uses JSON? Weird choice to slap another data scheme on-top of your data scheme. I will stick with XSLT for the time being as it is pure XML.

> return { name: stop.commonName, zone: getProp('Zone'), wifi: getProp('WiFi'), toilets: getProp('Toilets'), // A comma-separated list of line names that serve this stop lines: stop.lines ? stop.lines.map(line => line.name).join(', ') : '' }; }); }

Re: XMLUI

#28

Post by silverlight »

Recently used a lot of HaxeUI for a game and it felt similar to this. A lot of components included out of the box that “just work” with some basic styling. And you can use CSS styling on top to further customize as needed. Works across a lot of different platforms as well.

Re: XMLUI

#29

Post by zigzag312 »

> XMLUI wraps React and CSS and provides a suite of components that you compose with XML markup.

So this goes from XML → React → XML (HTML)?

Are there any studies actually showing XML is easier to write that a scripting language? In my experience, XML is equally hard to write while being more limited.

Re: XMLUI

#30

Post by junon »

thisislife2 wrote: post #23

Seems like we keep reinventing the wheel - the previous version of of HTML, XHTML ( eXtensible HyperText Markup Language ) is a direct subset of XML. Also, related - Mozilla Firefox used to have something called XUL ( XML User Interface Language - https://en.wikipedia.org/wiki/XUL - using which you could build complete desktop web applications with the Firefox / Gecko web engine (something that is now popular with th…

XUL felt magical when it came out. Was kind of sad when it got sunset or whatever happened to it. Felt like it could have been something great.
Post reply on HN