Tried out that AOL Communicator beta to see if I could find out more about how its implemented. It uses an embedded version of Gecko to display HTML mail. It may even use it to edit mail. It is not implemented in XUL. Instead, it uses the wxWindows GUI toolkit. It doesn't use the Mozilla Mail back-end code either. It appears to have a seperate application for mail, the address book and instant messaging. It does look similar to Mozilla Mail though.
Hmmm. Aaron is working on some secret new application involving RDF. At least he won't have to worry about having to change its name later like the Phoenix folks.
Got to come up with a name like that for my stuff.
7:10 PM Is it just Mozilla Mail in disguise?
Pictures of the new AOL Communicator strongly suggest that it is not only based on Gecko and XUL, but on Mozilla Mail as well. The UI is almost identical, the menubar has the same labels, Modern theme buttons appear on the toolbars, and they have the same features (junk mail filter, collected address book, mail headers in a grey box.)
The only interesting difference from a XUL person is the slightly different tree widget. It has buttons to scroll through the columns in place of the hide/show drop-down.
Well, according to this, that new AOL Communicator mail client is written using XUL and the Gecko engine. So regardless of whether this is good or bad for Netscape, this is good for Mozilla either way.
10:46 PM 101 things translated
Hey. A Japanese translation of 101 things that the Mozilla browser can do that IE cannot is now available, courtesy of KOZUKA Atsushi.
4:36 PM RDFPath / RPath
There were some folks looking into building RDFPath, an XPath-like syntax for referring to RDF data, although it hasn't had any updates for over a year. The syntax is fairly general purpose though.
For the RPath language I'm using in the SWC, I probably have different goals, since the expressions are intended to be used in UI elements, like XPath expressions are used in XForms. As such, they don't connect to a giant database of info.
For example, I might use:
director[birthdate/year < 1950]
which in RPath would return all nodes of directors born before 1950, but that wouldn't make sense to use on a client, as a client wouldn't have a database of directors to scan through unless it sent the query off to some remote server.
But, given two RDF files sent to the client each describing a different movie, one could pick out cast members that starred in both using:
children(<movie1id>/cast) & children(<movie2id>/cast)
Thus, there needs to be a balance between making the expressions powerful, yet ensuring that they make sense and performance doesn't suffer as a result.
2:00 PM Real work
Hmmm. I seem to have gotten myself into a situation where I have to do some real paid-for work for a few weeks. So I might not get as much time to work on the SWC.
The only thing I've done lately is change the history panel to use labels instead of URIs, and started creating a dialog box for adding custom datasources.
I wonder how I am doing all this.