The Future of the Web is not the Past of Windows: XML UI languages are commonly used to accelerate and simplify development and distribution of desktop-like applications. Languages like XUL and XWT encapsulate the set of Windows UI elements, and the ability to rapidly assemble a Windows-like Web application using XML is valuable and has many advantages over building a similar application in Visual Basic, let alone MFC or Swing. Unfortunately, using XML as a way to assemble interactive components that are defined using classic GUI toolkits leads to homogeneity and artificial simplicity, and does not reflect the diversity of today’s Web. Freedom of expression is essential for a UI markup language.

Read the complete paper in html or PDF.

I presented this position paper yesterday at the W3C workshop on Web Applications and Compound Documents.

Many thanks to my editor, David Temkin, who also came up with the title.

3 thoughts on “enabling freedom of expression

  1. No question about it, bad design is bad design, especially from an interaction standpoint. The tricky case is well-designed visuals combined with poorly designed interaction.

    I’ve encounted many a visually stunning (ie. in one sense, well-designed) Flash-based www site whose use I could not comprehend after several minutes of fiddling and clicking.

    I’ve got a question: do the recent versions of Flash player allow for popup windows? I know that you can overlay content outside the Flash rectangle, because I’ve seen ads ‘surf’ over the www page I’m looking at. But I can’t recall seeing a popup Window. Macromedia Central apps seem to be very rectangular and boxed in.

  2. Sarah,

    I think one of the biggest challenge you will face with Laszlo is the fact that it is opaque to deep linking. You are essentially creating a walled garden of navigation within the prevailing context of a dense thicket of HTTP/HTML. This is of course the inherent problem with Flash and why it will never gain much traction.

    A fundamental implications of HTTP is that it works best when everyone buys into the shared (yes, mediocre) UI mechanism of linking. This is the “good enough” principle at work again.

    For example I visited Marc Canter’s blog at http://blogs.it/0100198/ and noticed the soundblox and photoblox Laszlo widgets. Schematically they represent two “island” traversal hierarchies that don’t allow me to link to an individual photo or individual track. So I can’t send a link to my buddy to check it out.

    Do you have plans in the future to address this?

    Cheers,
    Douglass Turner

  3. Douglass has a point when it comes to websites that primarily offer information. This type of site is best kept as HTML for searching and navigation reasons. But there are a whole host of applications where deep linking does not make sense. Take any online shopping application as an example. There is no point linking directly to the checkout page. To checkout, you have to have first put something in your shopping basket. It is this type of application can be made to work more smoothly and intuitively using rich client technologies.

What do you think?