Over at the Bezilla blog, Niels Reedijk posted a new development version of FireFox 1.0 for people to download and test. There is a net_server version for BeOS R5 users and a BONE version for those who use BONE or Zeta.
The following are links to downloads and a list of patches mentioned in the blog:
In other news, Firefox 1.0.0-d4 is released which includes a new piece of candy.
Check out www.de-smederij.nl/firefox/MozillaFirefox-1.0.0-d4.zip for net_server, and http://beosland.free.fr/archives/mozilla/MozillaFirefox-10-d4-upd-bone.pkg for BONE. The latter one uses the SoftwareValet for installing. It’s nice. The latter one is done by jeannot31.
First of all, this release includes all the code that is present in the 1.0 release of Firefox. So it’s updated to the latest AVIARY-cvs. Additionally, from the previous release, the following patches are applied:
- 239813 - tangobravo’s transparancy patch
- 242315 - Japanese input (please test this in BONE, there was a regresstion there)
- The native app patch as distributed by tqh.
But the new and the updated are far more interesting.
- 267219 - the directorypicker code is updated and is now waiting for a review.
- 266327 - The add bookmarks window will now close, and the pref window won’t whine about failed saving of prefs either. This is all fixed by this patch. It is currently waiting a super review. This patch couldn’t be made without tangobravo’s help.
- The search bar is now fixed. (If it still doesn’t work, delete compreg.dat from your config/settings/Mozilla/Firefox/default.4a3/ dir)
If you’ve downloaded and tested one of these versions of FireFox, let the developers know of any problems and improvements that you notice when using the browser. Any feedback will help them make a better FireFox browser for the BeOS community.
Every great OS needs a great browser. BeOS had NetPositive, which pretty much has become a relic. You can see how it’s simple interface has influenced everything that has come out since, but it’s rendering engine just never kept up. Since then, the browser de jour has gone from Opera to Mozilla to Firefox. The interesting thing there is that the last two on the list, and the current browser of choice, are both developed by the BeZilla project.
Edward Dore, of the BeZilla project, sent me a request to post an article here talking about the new tinderbox and the continued need for funding. A tinderbox is a computer that constantly builds the code and checks for errors, etc. This allows immediate response to new code and a check to see if anything has broken. It also allows for simple nightly builds. Seems like a great cause.. contribute if you can. There is a paypal button in this letter, so you should be able to contribute directly to the project. It has nothing to do with us, and goes directly to Edward and the BeZilla project. We have included it for your convenience. Please “Read More” for the entierety of the letter.
Since the first days of the Mozilla browser on BeOS printing has been an issue. Once again a cash offer has been raised to any developer who tackles the problem. According to a forum post over at BeZilla.org the total cash bounty is up to $250 U.S. The only stipulations are that the fix must be functional under PhOS, Dano and Zeta. I would hope the fix would also be able to function on R5. The issue involves multiple levels of bug fixes and is not by any means a light task. I’m sure any true BeOS coder could tackle the issue in no time at all!
The BeZilla development team is in need of a few donations from the community. The BeZilla tinder box is becoming more and more unreliable and has recently experienced some down time. The team is looking into possible upgrades for the server, including hardware donations from the community and paypal donations.
On the same note, the Bezilla folk are looking into jump starting the development of a PPC build for BeOS. The libraries needed to be ported first are listed in this news item. Anyone with PPC experience give it a go.
Paul sent in a request for your support. StripZilla has made some advances and patches in the graphics library that would be extremely useful to BeZilla itself. Paul has a survey up on the BeZilla site and would like your support helping convince StripZilla to merge their code into BeZilla in order to make BeZilla, the official port of Mozilla, that much better and faster. You can read all about it here. Go show your support for a full featured browser running in the best possible way.
Just heard that bezilla.org has come online. It is a rather ambitious site maintained by arougthopher, which according to rumor is another name for “Paul”, who is a prominent BeZilla community member. It looks like the place to go for BeZilla news, questions, and downloads. Good luck to arougthopher in his quest to keep bezilla alive and kicking. I think we all should support this effort, because a modern browser is the #1 thing BeOS will need to live on. And BeZilla can answer that need.
Just had it pointed out to me that Wade Majors has stopped working on the BeZilla project, saying:
Some may not like to hear this, but I will no longer be working on Mozilla/BeOS. I will be happy to donate and transfer the mozillaforbeos.org domain to any user or group who wishes to do something with it. My reasons do have something to do with Be and the future of BeOS, and I am not going to try and justify those reasons here. You’ve all heard the stuff before. I wish Ham, Matt and the other moz devs still around luck.
He used to provide daily builds of BeZilla. I have also heard that Yannick Koehler has stopped working on BeZilla, though I don’t have confirmation on that. That still leaves several people on the BeZilla team, all of which are skilled and have been making progress… But they need more. BeZilla is a crucial app for BeOS, as it stops almost every complaint about a lack of browser support. Once it is up to speed with the other platforms, maintaining it won’t be as difficult. In fact, it should be relatively simple. But getting there will take a lot of help from lots of peeps. So if you can spare some time, and have “1337 skillz” involving BeOS coding, head over there and get involved.
Well, BeZilla has made great progress recently, and just keeps going. Up until now it has been very hard to follow their work because the build process was difficult, and consumed lots of time and resources. Solving that problem is Wade Majors, who is posting daily builds of BeZilla on his site. So if you get bored and feel like seeing what point it is at, now its much easier. Mozilla is a huge project, and the progress being made is very encouraging. I urge you to support the BeZilla dev’s any way you can, because a modern browser is a pretty big need right now. Way to go BeZilla team and Wade!
[powered by WordPress.]
Sleek, fast, kickin'-ass
Easy to use, fun to code
Go, go BeOS
Since 1998 - Until the Last User Leaves...
— BeGroovy, established 1998
19 queries. 0.048 seconds
[powered by WordPress.]