Talk:XML - Managing Data Exchange/XUL

Why is the text in this page in tags? It makes for a less than beautiful page. Will there be host if I remove them? (218.128.116.44 zeimusu on 'pedia)

Luxor XUL link
I removed the link to "luxor xul", as it is not related to Mozilla XUL, other than in concept. People from "Open XUL Alliance" have been trolling around for quite a long time already, posting links to their "xul" projects on various Mozilla-related sites. --195.146.72.90 11:19, 13 September 2005 (UTC)

Various comments

 * The ‘id’ attribute is important in that it is the way to identify the window so that scripts can refer to it.

Not really. Scripts can use  to refer to the window element. The id is used for binding icons to the window, and sometimes in the overlays.


 * All events and attributes must be written in lowercase.

Actually it's just that XUL is case-sensitive, as is XML. Attributes that have special meaning in XUL happen to be all-lowercase. This doesn't stop you from using mixed-case attributes for your own needs.


 * All strings must be double quoted.

Attributes must be in quotes, just as in XML. It doesn't mean that "all strings must be double quoted".


 * Save it anywhere but be sure to give the file the .xul extension. Now just double click on it and it should open in your Mozilla or Netscape browser.

.xul files are not associated with Mozilla by default

--195.146.72.90 11:37, 13 September 2005 (UTC)

revision suggestions
Karl Strength 16:42, 29 March 2006 (UTC)
 * Bold key words and start with clear definition after each.
 * Follow author guidelines to revise chapter.
 * Show more widgets and some user created widgets.
 * Change the first example -perhaps use an example that we have been using through out the class.(movie, professor)
 * Create an assignment and place it at the bottom of the page. Use XUL and widgets to create a page that displays information about UGA.
 * Edit the conclusion section. (Try to make is sound less like a Firefox employee wrote it.)
 * Place Learning objectives in a box to set them apart from the rest of the text (as done in previous chapters.)

Editorial Board
Moussa Mané
 * You can move the "written by" part as a reference at the bottom, so the chapter stays consistent with the rest of the book
 * If you notice there is too much text, like whole block. The reader can even find a specific information. Try to break everything down. You may need to change the structure a little with more sub-sections
 * Example: first a section on widget where you explain what they are, then how to use them and add them
 * One for Events...then sub section would be Event handlers and another Responding to Events.
 * Fell free to change the title of the sections (The basics, A first example, Adding Widgets...) I find them inconsistent. (let me know if you need clarification on this)
 * A shorter introduction. the rest of the info can be added as a new section
 * The example can be movie, professor or any other simple one
 * Give a summary.
 * Add Exercises and answers link

Professor
Rtw 19:38, 1 April 2006 (UTC)
 * Karl and Moussa's suggestions will help improve the chapter considerably
 * Try to use a tourism example to stick with the themes covered in other chapters. Maybe cities and attractions :)
 * Change sample code to fit with author guidelines
 * Change so that reference browser is Firefox rather than Mozilla or Netscape
 * Correct labeling of code (eg figure should not be within the code)
 * Check all the references are still valid

XUL's ≠ HTML's   tag!
The article states that the  tag of XUL is like the   tag of HTML — wich is not true. the  tag is more like the   tag (they're both the root tags) and XUL can for example also have the    and    root tags. More information at MDC XUL hub.