Jazilla Milestone 2 Released
Monday August 4th, 2003
Adam Hauner wrote in to tell us that Jazilla Milestone 2 has been released. The Jazilla project aims to rewrite Mozilla in Java. Check out the Jazilla M2 Release Notes and Changelog for more details and download a Jazilla binary from SourceForge.net. The next milestone, Jazilla M3, will feature a major rewrite of the renderer code.
(Tip: To detect Jazilla, all you have to do is: if (navigator.product == "Javagator"). ) (do that BEFORE any "//" comments). See <http://home.iprimus.com.a…mcbridematt/navigator.png>.
Oh, if you downloaded a binary, and find some site which isn't working (i.e the XML parser in Jazilla closes the pipe due to syntax errors), add them to <http://jazilla.netfirms.c…eabb31187c;act=ST;f=1;t=1>
When Jazilla will have better useragent string then Java/<version>?
You probably want to have a look at the DevEdge DOM xref at <http://devedge.netscape.c…ry/xref/2002/client-data/> . You may not know this, but Mozilla implements ALL of the DOM functions. And By M3, Jazilla along with Mozilla will both trounce IE when it comes to implementing DOM. (The renderer rewrite, by the way, is needed, in part, to correctly implement the DOM, as it wasn't originally designed for 'dynamic' pages)
I don't get it? How is Jazilla related to Mozilla? It does not use Gecko or a Java port of Gecko? Does it share any sources or architectural designs?
 Restrictions, i.e the tag which the stlye applies to apply.  Netscape needed a JS engine for JavaGator. But in the end, executives "forgot" that it existed
To be honest... I didn't expect the release to make news on MozillaZine.
Thanks for trying to clear this up... I guess I'm not totally lost now, just lost.
So the goal is to create a new XML/CSS rendering engine in Java from scratch? Or maybe based on JTextPane? Are you going to implement a XML+CSS XUL rendering engine or are you just generating Swing components from the XUL files?
(I did read the FAQ but it didn't anwser much ;-))
The HTML engine is from scratch, however. It goes back to 2000 when Andy Trip and Matthew Schmidt created it. It was later forked and refactored by the NetBrowser project and now its back with us :). The only problem is that it lays out tables as if it were a Swing app.
And judging from info in the web archive, Jazilla appears to have been a moz.org module at one stage.
who think that Mozilla is just too fast!
Java might be fun for language purists and whatnot, but I've yet to have a *single* positive experience as the end user of a java application.
#8 Re: I guess this is for people
by webgremlin <email@example.com>
Tuesday August 5th, 2003 7:45 AM
> I've yet to have a *single* positive experience as the end user of a java application.
I would have said that until I used Eclipse (eclipse.org). SWT!
#10 Re: I guess this is for people
Tuesday August 5th, 2003 7:56 AM
Chances are you have used a Java app disguised as a real one. LimeWire is an example. MacOS X runs Java apps as if they were native ones (Java is listed as a GUI toolkit for that platform).
The only problem is a lack of a good native Java compiler. gcj is getting better, but it isn't complete yet.
As for the "who think that Mozilla is just too fast" comment.. well maybe. I ran M18 and Netscape 6 when I had a 233MHz Cyrix MII, and I don't think Gecko was slow back then.
So, I downloaded this new milestone, how do I get it to actually run?
#13 Re: How to get Jazilla to run?
Wednesday August 6th, 2003 1:21 AM
Same way as M1.
$ java org.jxul.xulrunner.Main
$ java -Ddebug=true org.jxul.xulrunner.Main
#14 Re: Re: How to get Jazilla to run?
Wednesday August 6th, 2003 3:17 AM
Does this need to typed into an MS-DOS prompt . . . ?
#18 Which gives me the following error . . .
Wednesday August 6th, 2003 10:04 PM
Exception in thread "main" java.lang.NoClassDefFoundError: org/jxul/xulrunner/Main
mcbridematt, is Jazilla based on an older version of the Mozilla code? Do you plan to eventually release a new Jazilla milestone corresponding to each new Mozilla/Firebird release (to port over the new features/fixes), or will Jazilla have its own separate development path?