SillyDog701

[Don_HH2K]

After exactly a year of work, Donzilla 1.0 Final has been released!

For those that don't know, Donzilla is an Internet all-in-one client developer exclusively here at SillyDog701 for HardwareHacks 2000. Actively developed by SillyDog701's community, it's become greater than it could've been developed by a closed group. Donzilla was created with the development progress open to all: we've had numerous people jump on the development bandwagon during the year. Now that we've hit 1.0, I'd like to say thanks to our contributors for a great year of work on this project.

Download Donzilla 1.0 Final:
Donzilla 1.0 Final for Windows (and standalone RAR archve)
Donzilla 1.0 Final for Linux GTK1+XFT
Donzilla 1.0 Final for Mac OS X 10.3.9 and higher

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[beanboy89]

Yes! Finally, Donzilla's gone gold! I remember the moment, 356 days ago, posting in the Customized Builds forum about the first pubulic release, Donzilla 0.3. That pre-alpha release was buggy, and the interface was broken at some places, but I could see the project was going somwhere. Since then, there's been 15-or so releases, with the change of codebase from Netscape to Mozilla to SeaMonkey, the addidion of two new supported platforms, and a whole lot of fixes and new features.

Congratulations Don!

Here's some of my feedback on the 1.0 release:
This is the first SeaMonkey-based Donzilla I've used. I'm happy, as I'm mainly a SeaMonkey user, to use a browser that uses the same base codebase and feature-set. A recent introduction in SeaMonkey was autoscroll. Auto scroll does work in Donzilla, but the icon that appears upon a middle click is blank, and takes the apperence of the MS Office-like menus that Donzilla uses.

Screenshot showing the difference between SeaMonkey's and Donzilla's autoscroll icon:


Just a guess, but it probably has somthing to do with the [tt]userChrome.css[/tt] hack to get the Office-like menus is interfearing with autoscroll because the autoscroll icons in [tt]chrome\modern\skin\modern\communicator\icons[/tt] are intact.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Fulvio]

One problem, noticed with 0.9. I wanted to uninstall a number of preloaded extention, and each one gave an error, in regard to the backup folder. I had to remove it manually. It seems to run with less memory usage, but will have to see.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[beanboy89]

I just noticed that ChatZilla identifies Donzilla as SeaMonkey. In ChatZilla, if you go to Help > About ChatZilla, the following appears:

[INFO] Chatzilla 0.9.69.1 [SeaMonkey 1.0b/0000000000]
[INFO] Please visit the ChatZilla homepage at <http://www.mozilla.org/projects/rt-messaging/chatzilla/> for more information.

And it looks like the Build ID should be in place where "0000000000"'s are, but that same thing happens in SeaMonkey as well.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Antony]

Excellent work!

This version does not exhabit some Mac-specific problems I reported earlier for previous versions.

The slash (/) and apostrophe (') are work fine. Mac-style convention keyboard shortcuts are all correctly assigned (e.g. + C, + V, + arrow keys).

UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051221 Donzilla/1.0 (WML/1.3)

[Don_HH2K]

Billy, I'll look into the autoscroll problem. I don't have an autoscrolling feature on this laptop, and the only other mice I have are old serial mice, so I had no idea that was happening . . . I think I know how I can fix this: I put the Windows-styled menubar features in global.css -- I bet I can correct it if I put it in menus.css (if such a file exists, and I believe it does) instead. The Chatzilla problem I believe is inherent, because Chatzilla is reading the version number from the application core itself (which still calls itself Seamonkey), not a localizable entry. The build date of all zeros is probably because I removed the build date entry in build.dtd during the 0.9 PR1 milestone; I suppose I can put the date 2006010100 in there since that corresponds to the date/time I released it.

Fulvio, I'm working with Pu7o on a method of easily uninstalling extensions. It turns out that instead of using the giant installed-chrome.txt, Seamonkey's launch process can also be controlled by individual manifest files. If I port installed-chrome.txt entries to their respective manifests, then not only could I easily write an application to remove components, but it would also make it much easier to create an installer with multi-component support.

Antony, glad to hear that 1.0 works on OS X. I put together this one using OS X instead of attempting to drop everything in on Windows, as I was doing before.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Pu7o]

...menus.css (if such a file exists, and I believe it does)

That'd be [tt]popup.css[/tt]

I suppose I can put the date 2006010100 in there since that corresponds to the date/time I released it.

How about putting in [tt]Donzilla 1.0[/tt], so that it'd be recognized like this:

[tt]ChatZilla 0.9.69.1 [SeaMonkey 1.0b/Donzilla 1.0][/tt]

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8) Gecko/20060101 Firefox/1.5 Firescape/0.1b3 wml/1.3

[Edward]

Congratulations on the release!

UserAgent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.9a1) Gecko/20060101 SeaMonkey/1.5a

[beanboy89]

I don't know if this is a known problem, but I can't view SVG documents in Donzilla. If I go to this page and click any of the examples I get an open/save dialog. By contrast, SeaMonkey 1.0b can view the SVG pages without any problems. I checked [tt]about:buildconfig[/tt] and I notice Donzila does not have [tt]--enable-svg --enable-canvas[/tt] while SeaMonkey does. So Donzilla was compiled without SVG and Canvas support?

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Don_HH2K]

It wasn't compiled with SVG support; I recall Pu7o was having problems compiling Seamonkey with SVG support for some reason.

The Adobe SVG reader plugin should still work, although since that isn't redistributable, I can't put it in.

Pu7o -- any chance the next build will have SVG enabled?

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Fulvio]

I had a big surprise after installing the SVGView program. It did not drop any file in plugin folders, so I found a folder in Program Files|Common files. I figured that the NPSVG3.dll was the correct file to place in the plugins folder. It, sure enough, works to open the Samples. The problem starts when I make any attempt to close the page, or a Tab which was one of three open. It, invariably, when I choose to close it, closes the browser. If I want to close all tabs, I get a warning, as selected, but not this thing.
May be it is not the correct file, but, it sure makes a mess.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Don_HH2K]

The problem with plugin installation is that most installers are taught to find two or three plugin directories. I'd like to think that installers are taught to append pluginreg.dat instead of looking for a /plugins directory, but I could be mistaken, and if that's the case, then there's a good chance that they're not going to be programmed to look for Donzilla for awhile. Either that, or Mozilla registers itself to the Windows registry for this sort of thing, and then installers would look for that, which I could easily recreate using Advanced Installer.

I'm not sure of why the Adobe SVG viewer does that. I'd tell you to try it in Seamonkey 1.0b, but since Seamonkey has SVG inbuilt, you can't do that. It does look like it happens in the 1.8-based Firefox, though, according to Bugzilla Bug 296944, so it's more likely a Seamonkey problem than a Donzilla problem. I'll try the SVG6 beta and see if that works any better.

EDIT -- Confirmed: SVG Viewer 6 PR1 works.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Pu7o]

It wasn't compiled with SVG support; I recall Pu7o was having problems compiling Seamonkey with SVG support for some reason.

The Adobe SVG reader plugin should still work, although since that isn't redistributable, I can't put it in.

Pu7o -- any chance the next build will have SVG enabled?

The build I compiled yesterday does have SVG and CANVAS enabled.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8) Gecko/20060101 Firefox/1.5 Firescape/0.1b3 wml/1.3

[beanboy89]

Here's somthing I just noticed. If I go to Edit > Preferences > Appearence > Themes or View > Apply theme, I notice there is a blank theme selection. If I choose this theme and restart Donzilla, Modern is used. I don't know if it is somthing I did or is like this for everyone, but creating a new profile doesn't seem to fix it.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)

[Don_HH2K]

I've just noticed this as well. I tried refreshing the local chrome, and found a rogue entry to a nonexistant adblock.jar in installed-chrome.txt, then deleting the three control JARfiles. That didn't help, so I tried creating a new profile after that, and got the same result. I'm going to go confirm it in the Linux build, just to see if it's a Windows-only problem.

--EDIT--
It doesn't appear in the Linux build, so there's a good chance it's only in the Windows build. I think I found it: chrome.rdf reveals three themes:

Code: Select all

  <RDF:Seq RDF:about="urn:mozilla:skin:root">
    <RDF:li RDF:resource="urn:mozilla:skin:modern/1.0"/>
    <RDF:li RDF:resource="urn:mozilla:skin:classic/1.0"/>
    <RDF:li RDF:resource="urn:mozilla:skin:classic"/>
  </RDF:Seq>

I'd take it that classic (not classic/1.0) is the rogue entry, I'll try taking out the reference to that, and see if it fixes this.

--Another EDIT--

Yet another Adblock problem: Adblock's skin calls itself classic, even though the correct name is "classic/1.0". By my guess it's a Seamonkey theme handling problem that didn't show up in earlier builds, but that's an easy fix by changing everything in Adblock's skin's chrome.rdf from "urn:mozilla:skin:classic" to "urn:mozilla:skin:classic/1.0".

Furthermore, I've found another bug, this time in Forumzilla, where certain feeds won't display because of the messages containing <iframe>s instead of plain text or more standardized HTML; apparently 1.8's Mailnews doesn't like to display <iframe> elements in e-mail messages (for good reasons, too). An edit to /components/feedItems.js fixes that.

Looks like a 1.0.1 bugfix release will be along soon.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)