Slashdot Mirror
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."
Some uses I can think of is embedding sub-parts of it in embedded environments.You also can modify it (Open-source) it for use in hundreds of ways to create useful apps.This most probably is not going to replace any browser on the average desktop, but can possibly be used as a web-test tool, automation framework etc.
What about running a browser/modification on a Netware box (it supports java) and no cross compiler necessary.
Also note that W3C demoes a browser on their website ( Amaya IIRC) written in Java.
.ACMD setaloiv siht gnidaeR
A year and a half ago I was involved on the development of a Digital TV Set Top Box.
As User Interface Developer one of my duties was the analysis and selection of an embedded web browser. My bet was a Gecko based one, but implement it for the Nucleus RTOS was out of the question, so we should point to a propietary browser license.
If this project was so evolved in that moment it would have been a serious alternative.
Maybe I want to write an application in Java that has a more dynamic user interface. Swing makes things like this hard. What if you could make a great GUI in seconds in Java using dynamically generated XUL with call outs to Java instead of broken impared JS.
o neEditor", XUL.TEXT);
:) I'm impressed with the speed. Maybe it will send some of those idiot trolls about Java being slow back to the drawing board so they can complain about something else for a while when it gets done.
I'm all for duct taping a rendering engine on the front of real Java just because I don't like to deal with any of the popular layout managers for swing. Ideally, I would have my own Java widgets (because swing gets extendible widgets right like no other GUI API anywhere) that were rendered in a sane fasion (plus the native XUL widgets for when you don't need to extend them).
Swing layout is one of the reasons Java GUIs seam to be broken. If you resize a window, you get a lot of grey boxes. Sure, Mozilla could use some double buffering on their resizing, but it doesn't leave me with a gray screen instead of seeing how the components will look after resizing.
It would be even better if you could extend the XUL language in some manner with custom widgets.
For example:
XUL.registerComponent(MyPhoneEditor,"ph
These are all the more reasons why we need a good renderer in Java.
On a side note:
Anyone notice that with Java 1.4.2, jazilla starts faster than mozilla? A little over a second for me. It just won't render any web-site properly
Karma Clown