Discussion Locked

Using XML to describe user interfaces

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about using XML to describe user interfaces. What approach do you use? How helpful did you find this article in providing additional approaches?

5 replies

by nyc_guru_sorta

I found this article to be a good real-world example of applied XML. It was complete with examples, it developed well and showed how XML can be combined with HTML in a simple manner without the sometimes confusing XSLT and DTD integration that often makes XML seem daunting to the beginner.

I read the article you pointed to and I'm not really sure what your point is. If this article violated the *suggested* coding practices of the other article then I'd probably consider that a difference in style. If there is an error in a line of code in the example here then I'd probably chalk it up to a busy writer that never actually tested a piece of code that wasn't meant to go into production anyway.

Probably no more important than your misuse of the word "there" instead of the appropriate "their". I still knew what you meant :-)

by leo

I just have to flame the article, don't take it personal:

1. from "BUILDER.COM" XML newsletter I expected more practical, working examples. ".. render it into html ..." -> haha, and how do you do this ? xsl ?

2. LINKS TO IMPLEMENTATIONS
The User Interface of the Browser I am using right now to write these lines is completely based on XML description and CSS Style. I can change these description files. They implemented a RDF/XML based Messaging System for Email, too.
product is ...... MOZILLA / NETSCAPE
And from an expert like you I expected more projects I could use.

by bmikovits

If you explained how you got from the XML to the html this would be a more complete thought IMO.

The end result html was a bit sloppy. If derived from xsl I don't see how you could have a extra tag without it blowing up in your face.

by erich pawlik

Binding sales to a predefined and signed sepcification made be comfortable for developers but is not a recipe for success in today's difficult and turbulent times. The advice looks like too much like a piece of advice from outdated heavyweight development methodologies.

Software development is about delivering customer value. It is up to the software suppliers to adapt to frequently changing value propositions - unless you are Microsoft or SAP.

In the corporate development game, sales reps are representatives of the customer. They drive the process, not development or product management. Of cause there has to be some negotiation about feature priority but this negotiation should be inside the sales team as a whole.

This discussion is closed to new replies.