Jazilla Milestone 1 Released

mcbridematt writes "Many of the long time Slashdot readers will remember the Jazilla project to rewrite the Mozilla browser in Java. It went into hibernation in 2000 and I took it over last August. I have completely rewrote the browser which now follows a more Mozilla-like architecture. The Result: Jazilla Milestone 1 has been released. Download it from here. No prizes for guessing that it's Alpha software." Read on below for a list of what Jazilla can do, so far.

"Significant (implemented) features include:

• chrome:// support
• JavaScript implemented for the GUI thanks to the Mozilla.org Rhino engine. HTML Scripting coming.
• GUI in part, uses XUL and W3C DOM
• Written in 100% Java
• Open Source
• Uses the NetBrowser renderer, which is actually based on Jazilla-classic work."

Comments

Running this puppy

[mcgroarty]

I'm sure a million people will want to see this, but not everybody knows how to start it.

Once you expand and extract this puppy, just cd into the folder it made and, assuming Java is properly installed on your machine, you need only run:

java org/jxul/xulrunner/Main

Good luck, and enjoy! The browser's still lacking in many obvious areas, but it does work on a lot of sites. Too cool -- props for all the hard wo\ rk. :-)

Re:Running this puppy

[jeffg]

You may need to specify a classpath manually using one of the following (again, both from the directory containing README, COPYING.TXT, etc.):

java -cp . org/jxul/xulrunner/Main
java -classpath . org/jxul/xulrunner/Main

Windows users: The "jazilla.bat" file may or may not work for you. You may wish to edit this file to specify the classpath as above. You could also change your CLASSPATH environment variable, if you felt the need.

Re:Running this puppy

[mcbridematt]

I might as well add two other things I didn't put in my original submission:

1) Look in org/netbeans/netbrowser/tags for any .java files not compiled. Compile them. The renderer uses Reflection to start up tags, so they don't get compiled at compile time. In the future, if Jazilla finds a compiler and tag which isn't compiled, it will compile that tag
2) Did I mention that getting URL's is multithreaded? If you try and hack it abit, e.g use a JIT for Crimson, you might get a better result.

Also, anyone wishing to make a product based on Jazilla, note that the jXUL part is unlicensed. I am yet to talk to Kevin T. Smith (co-founder of the jXUL project) about what license to put it under. The renderer is under the SPL. When that's done, expect anything under org.jxul to move to org.jazilla

Re:Running this puppy

[hatrisc]

actually there's a script. jazilla.sh

Re:So, using Javascript and Java...

[Exiler]

Java programs != Applets, I think you're getting the two mixed up.

Why...

[valis]

Since half the comments so far seem to be "What is the point" I'll offer one justification.

There is still a serious lack of a good modern HTML browser for embeding in java applications. Swing provides an EditorKit which handles HTML3 reasonable well, but most of the other quality offerings are non free.

Major Java IDEs (Eclipse, NetBeans) have projects to implement something like this. Many other Java applications could potentially benefit. It's a good idea.

What "Write Once, Run Anywhere" Really Means

[Anonymous Coward]

From the beginning, Sun intended the Java language to be platform-neutral. That is, Java programs are written to run on a Java Virtual Machine instead of on a physical computer--it's the Virtual Machine that runs on a real computer. Thus a programmer can develop a program that will work on the sort of computer he likes and expect it to run on the sort of computers that his customers like, because it runs inside of the Java Virtual Machines on those computers.

This means that when you go to the store to buy an application, you don't buy the "Mac version" or the "Microsoft Windows version." You buy the "Java technology version." And as long as you have the Java Virtual Machine--which is free, and available from a large number of vendors--you can buy the program without having to worry whether it's going to run on your particular computer.

Re:Why?

[FatherOfONe]

Ok it was kinda a joke but I will address it more seriously this time.

1. Java is slow. This was true in 1.0 release of Java, but with todays JIT's the speed difference is small. I can point you to numerous sites, but at the end of the day it comes down to good coders. Your experience must be with some bad coders.

2. SWING is slow. This again use to be true with 1.18 + SWING and 1.2x JVM's the 1.3 and 1.4 have increased SWINGS speed considerably.

3. JAVA takes up too much memory. Yes it is true that the base JVM can take around 5-16MB of RAM per JVM instance. But with todays systems, on a lot of applications that isn't too bad. Now the core issue is that it takes up that amount for EVERY JVM that is used. So to your point: If I launch a Java calculator program, and then launch a Java notepad, I will have lost around 10-32MB of RAM in just JVM's. This is currently true, however it is being addressed and should be solved with the 1.5 release. Once this is done, then it would be possible to have ONE JVM running on the system for all Java applications. The JVM could launch at startup and then even the inital load times would be greatly reduced. I believe that this is the way Apple is handling Java (Can't confirm it though).

So, when this issue is resolved, running Java on a machine could mean only giving up a maximum amount of 16MB of RAM for the JVM and the rest for the application. To be honest that is what most Java programs are doing today. Most run as an application server and run Servlets and JSP's all day long.

Another poster mentioned that you use the correct tool for the job. I agree, but I will add that the issues for not using Java for speed has and is going away. The reasons for not using it for memory are going away on most computers.

We do agree on one point. Most people do have computer processors far greater than they need.

Lastly, if you are having so many issues running Java apps on your system you should look at newer JVM's. They make a huge difference.

Re:So, using Javascript and Java...

[recursiv]

Hold on there skippy. Java applets ARE Java.

I think what our friend Exiler here is trying to say is that Javascript has nothing in common with Java except the name. And if I'm to believe the person who told me, Javascript had a different name while it was being developed but Sun exerted sufficient pressure on the neccesary parties to change the name to sound like Java.

Quick recap:
Java Applications - Java
Java Applets - Java
Javascript - Not Java

I hope this helped.