Benjamin is starting to work on the canvas tag patch I wrote, so we may see it become reality soon.
6:53 PM Canvas Tag Coming Soon
12:04 AM Comments on Rapid Application Development with Mozilla
I've been going through the newly published Mozilla development book Rapid Application Development with Mozilla by Nigel McFarlane. I thought I'd add my comments.
It's very detailed. It provides detailed descriptions of XUL, XBL, RDF, templates, and so forth. For someone looking for detailed information about how to use these technologies and a bit about how they work, the book provides lots of information.
To some degree, the extra detail is also problematic. In many places, the book goes into more detail than is really necessary. There's a lot of text there. And, I think, a disproportionately small number of examples. If you were to go through the book attempting to learn XUL, I'd imagine you would be overloaded with information. Although I'm probably a little biased, I think the XUL tutorial is a better way to learn XUL, while the book is quite good for a greater understanding of the details.
I had hoped instead to see a much greater amount of focus on XPCOM and the available components. The book does provide, in the XPCOM chapter, some detail about the RDF APIs as well information about file and network reading, and provides an introduction to a number of other things, such as sockets, security and preferences. But, considering the detail in earlier chapters, this is too little I think.
However, overall, I think Rapid Application Development with Mozilla is a good addition to the Mozilla/XUL developer's library.
11:50 AM Parsing and Serializing XML Documentation
I finished the first piece of documentation that I have been working on, Parsing and Serializing XML, which describes how to parse and write out XML in Mozilla.
There are a number of other documents and have half-finished each of them, including the rest of the RDF stuff.
12:10 AM Want some documentation?
I'm now in documentation writing mode. I've been working on a couple of new Mozilla documents. I thought I'd ask if anyone had anything specific they want documented so that I can focus on that instead of writing something that no one wants.
12:36 AM Best Topicalla Screenshot Ever
I've added a much nicer looking screenshot of Topicalla, now with images and anti-aliased fonts. It shows a UI of a single FOAF file. The UI elements to use are determined from the data in the FOAF file. Some additional data is loaded from musicbrainz.org, although the loading part isn't handled automatically yet. One can select the Detail drop-down to show more detail such as the song titles on the albums, and the descriptions from the weblog.
I recently also added support for templates using XPath and XML datasources as well as the existing ReoPath and RDF support. It is generic enough now that support may be added for other kinds of datasources as well. This allows one to create a UI that is bound to some XML data. For instance, the following:
<hbox rp:repeaton="//td"> <label rp:assign="text()"/> </hbox>
5:27 PM About Documentation Seekers
There are two groups of people looking for technical documentation. The first are those looking to learn the technology. These people need to have straightforward information presented in a manner that allows them learn and understand the technology step by step. They need to start with simple examples and build to more complex ones. The documentation needs to be explanatory and not rush into introducing too many things too quickly.
This is the way I designed the XUL tutorial. It starts with simple concepts and explains them in detail so that the reader can understand them. It gradually adds new concepts over the course of the tutorial. It doesn't cover everything, but instead it tries to cover most things with more detail, as well as presenting some basic information for things like XPCOM that really need a separate guide.
The other group of documentation seekers already understand the technology and are using it. They are stuck on some problem they are having and have turned to the documentation for help. The XUL tutorial isn't designed for these people. There are two problems with a tutorial approach for this group.
First, the user doesn't know what could be causing the problem, so they won't know where to look. For instance, recently someone had a problem with a tree not rendering properly. It turned out that the problem was that the tree columns didn't have ids on them, and it was suggested that a note about this should be added to the tutorial. Actually, it's mentioned twice in the tutorial and once in the reference that ids are needed on treecol elements. The issue is that this information isn't presented where the user wanted it, especially since the user didn't know that this was the problem. I could add more notes about tree columns, but, in the context of a tutorial, it would need to be repeated in too many places.
Secondly, people looking at the documentation are looking for a answer to the problem they are having. If the documentation doesn't provide a specific answer to the specific problem the user is having, they might consider the documentation inadequate. In many cases, it's because the question is too specific to be answered by documentation. The documentation can only provide a limited number of direct responses. For instance, a topic about how to change the spacing between the icon and label in a toolbar button may be a suitable question for a theming guide, but for the XUL tutorial, this is a little specific for a direct answer. (For XUL, the actual answer is: you don't)
Anyway, here is a review of the recently published book Rapid Application Development with Mozilla. I haven't read the book yet myself, but it may provide some additional help for XUL and Mozilla developers. Although, as I said above, the problem isn't the lack of documentation, finding help depends on whether the solution to the problem is available.
8:40 PM Buying a CD
I have never bought any audio CDs. Nor have I bought any audio tapes nor any records. Neither have I bought audio on any other medium. Nor, for that matter, any DVDs or videos. I don't own a CD player. And I don't have an MP3 player. I have also, if you would believe, never downloaded any music illegally.
Recently, I listened to some music that I found on the Internet. Yesterday, I decided that I liked what I heard enough that I decided to buy the CD for myself. Of course, I've never done that before.
Recording studios would have you believe that no-one would do that. They would rather tell you over and over that people download lots of illegally copied music instead. That may be true, but that isn't true for me. I'd imagine that the music industry wouldn't even believe me. Well, I have only one thing to say to that.
1:08 AM I've changed all URIs in the XUL tutorial
When I originally wrote most of the XUL tutorial, I really didn't understand RDF that well. Now I do. At the time, I used URIs in my example RDF that were of the form 'urn:something:thing', since that is the form that some of resources in Mozilla used. That was actually a bad idea. Specifically, you're not supposed to make up the parts of a 'urn', except for the last part. The word between the two colons ('something' in 'urn:something:thing') is supposed to be one of a specific set of values as defined in RFC 3406.
Secondly, 'urn:animals:root' for instance, is very generic. Much too generic for a resource URI, since it should be globally unique. Better would be to include the domain of the person or entity that created the resource, which is what is usually done. I myself might use 'http://www.xulplanet.com/rdf/' as the base of all URIs. So, I have searched through the tutorial and have changed all 'urn' references to 'http://www.xulplanet.com/rdf/' including those in the animals example.
I originally wasn't going to change them, as I figured they were just examples. But, of course, after four years of questions and confused people, I realize that very few people using XUL, RDF and templates, even seem to take time to understand RDF very well.
I've noticed that many people are using 'urn' resources such as 'urn:music:item1', which are not good resource URIs. So hopefully, by changing the tutorial, I can discourage that usage.