Slashdot Mirror

← Back to Stories (view on slashdot.org)

Jazilla Milestone 1 Released

Posted by timothy on from the practically-speaking dept.

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."

5 of 353 comments (clear)

  1. Re:Why? by Copid · · Score: 0, Troll
    Why? Because Mozilla wasn't enough of a pig slow CPU and memory hog as it was, of course!

    Great browser, but damn! I've wasted hours waiting for Mozilla menus to draw after clicking on them.

    --
    An interesting anagram of "BANACH TARSKI" is "BANACH TARSKI BANACH TARSKI"
  2. riiiiigggghhhht..... by Miguel+de+Icaza · · Score: 0, Troll

    i have downloaded your browser. loaded it in blackdown 1.4.1. typed in "http://slashdot.org/" at the address bar.. what should i see:

    black screen, with OSDN in top left corner

    Oh well, interesting project (i guess) - try harder

    --
    Before adopting WHATWG, read the moonlight.NET EULA [http://www.microsoft.com/interop/msnovellcollab/moonlight.mspx]
  3. java by k-zed · · Score: 0, Troll

    There's only one thing i wanna know: Why... Oh why, for god's sake.

    --
    we discovered a new way to think.
  4. This page is converted ... to XHTML 1.0 STRICT by azzy · · Score: 0, Troll

    Their homepage claims xhtml 1.0 strict complicance.. yet consulting validator.w3.org ...
    This page is not Valid XHTML 1.0 Strict!
    see for yourself

    Any pedant points going around?

  5. Who pay for it? by axxackall · · Score: 0, Troll
    The only explanation I can find about what's the motivation of such projects as Mozilla in Java is that the development was paid by PC manufacturersas moving big (especially with GUI) applications is the only way to push regular consumers to upgrade their PC.

    Seriosuly. Today most of people (at least what I can see in North America) have already got home office desktop PCs power enough to run most of applications they need. Typically it's 500Mhz - 1GHz CPU with 256-512 MB RAM (Geeks! your super PCs are not in count here as you are a minority of the PC user base!). But for PC vendors it's obsolete - they want to sell more and more power PCs in order to sqeez more and more money from users. So, how to force customers to upgrade?

    There several answers: CPU-expensive UI candies of win2k and XP, XML with SOAP (read .Net) where it's not needed, and of course Java.

    First Java has been expanded on the server market, where M$ is weak. It's very well known: most of Java based server installations do what was easy to program and cheap to run using Apache/CGI/PHP/Perl/Python. Now they try again desktop applications. They have failed with SWING plugins: Macromedia Flash is way lighter. And they didn't have any chances unless users realized that Windows is not the only liable platform. So, here are coming again: Java based GUI-monsters.

    --

    Less is more !