Is there a reason for Mozilla to use anything BUT the standard Windows buttons, dialogs, etc?
Two reasons.
1) If they did, there wouldn't be any ports apart from possibly Macintosh (not enough time)
2) To get the things required by CSS 2 and 3 (animated background images on buttons, anyone?) you need to reinvent your own widget set. IE does the same thing. Having done that, why not use it for a cross-platform UI?
It's turned on by default (in installer builds only) because we would like more people to test it. You have an option of turning it off in the installer.
Yes, we are trying to make the code more efficient as well - turbo is not a substitute for performance improvements.
Oh, and the mozillaquest.com article is full of it.
Yep, you can prevent sites from resizing windows as well. It's possible in roughly the same way as popups, with the same level of control. You'd need to ask in the newsgroups exactly how to do it.
Are you committing to coming to help us if we do what you say?:-)
Gerv
Re:The browser is great, but where is the spell ch
on
Mozilla 0.9.4 Released
·
· Score: 2
but that is no longer supported
Well, the 6.1 spellchecker is not supported with current builds. But if you wait for the next Netscape release, the spellchecker will work with those builds and all following builds (until we break it again;-)
Best way to find out is file a bug and see:-) If you don't like it, and it makes it into Netscape 6.whatever'snext, then if you haven't filed a bug you've only got yourself to blame.
Gerv
Re:The browser is great, but where is the spell ch
on
Mozilla 0.9.4 Released
·
· Score: 2
Netscape has a proprietary spell-checker which it ships. No-one has yet found time to write an open-source one. Obviously, no-one at Netscape would spend time doing it, and external contributors are busy on other things. The usual trick is to use a build close to a Netscape release and install their spellchecker.
It would make a good CS project for someone. Fuzzy logic matching isn't all that hard. The UI is open source, it's just the back end that's currently proprietary.
If you are interested, mail me and I'll point you in the right direction.
We'd be very interested to hear of pages Konqueror gets right, and Mozilla gets wrong. Please file bugs in Bugzilla here, and then quote the bug numbers. We'll get right on it.
Lynx is probably faster still. But it doesn't mean you necessarily want to use it. This is not an excuse (Mozilla should be faster than it is), it's just an observation.
The mozilla folks really ought to put up MD5s with the release.
Why? If they can tamper with the releases, they can tamper with the MD5s.
Anyway, the standard disclaimer we put on all releases applies: "If it doesn't melt your hard drive and send your tax evasion plans to the IRS, consider yourself lucky."
Gerv
Slashdot Mirror
Yeah, but you've anonymous :-)
So, what's wrong with the codebase? I'm sure that, to make a statement like that, you have at least a passing familiarity with it.
Gerv
There's a sourceball on ftp.mozilla.org and you don't need the website unless you want weird build options. The command you are looking for is:
:-)
gmake -f client.mk build
Hope that helps
Gerv
Is there a reason for Mozilla to use anything BUT the standard Windows buttons, dialogs, etc?
Two reasons.
1) If they did, there wouldn't be any ports apart from possibly Macintosh (not enough time)
2) To get the things required by CSS 2 and 3 (animated background images on buttons, anyone?) you need to reinvent your own widget set. IE does the same thing. Having done that, why not use it for a cross-platform UI?
Gerv
So what's Netscape 6.1 (released early August, to widespread acclaim) if not a product?
Gerv
It's turned on by default (in installer builds only) because we would like more people to test it. You have an option of turning it off in the installer.
Yes, we are trying to make the code more efficient as well - turbo is not a substitute for performance improvements.
Oh, and the mozillaquest.com article is full of it.
Gerv
I'm not certain (check the newsgroup post) but I think it disables them during timer events as well.
Gerv
Create the popup, then - just create it at coordinates 100000, 100000, and destroy it after 10 seconds.
Gerv
In which case we hack window.open() to return a value indicating success :-) It may even do so already.
They can't win, you know...
Gerv
Yep, you can prevent sites from resizing windows as well. It's possible in roughly the same way as popups, with the same level of control. You'd need to ask in the newsgroups exactly how to do it.
Gerv
OK, so maybe I screwed up the release notes.
Could you tell me what OS you are using, and what the results of searching your hard disk for a file called prefs.js are? Mail me if you like.
Gerv
(there goes my option of opening in a new window)
That's bug 55696.
Gerv
Have you read the release notes? It details how to do it in there.
Gerv
That won't be fixed. You'll have to wait until the next time Netscape releases a spellchecker.
Gerv
Then go back to the drawing board and start over.
:-)
Are you committing to coming to help us if we do what you say?
Gerv
but that is no longer supported
;-)
Well, the 6.1 spellchecker is not supported with current builds. But if you wait for the next Netscape release, the spellchecker will work with those builds and all following builds (until we break it again
Gerv
Are they planning on keeping this awful behavoir?
:-) If you don't like it, and it makes it into Netscape 6.whatever'snext, then if you haven't filed a bug you've only got yourself to blame.
Best way to find out is file a bug and see
Gerv
Netscape has a proprietary spell-checker which it ships. No-one has yet found time to write an open-source one. Obviously, no-one at Netscape would spend time doing it, and external contributors are busy on other things. The usual trick is to use a build close to a Netscape release and install their spellchecker.
It would make a good CS project for someone. Fuzzy logic matching isn't all that hard. The UI is open source, it's just the back end that's currently proprietary.
If you are interested, mail me and I'll point you in the right direction.
Gerv
We'd be very interested to hear of pages Konqueror gets right, and Mozilla gets wrong. Please file bugs in Bugzilla here, and then quote the bug numbers. We'll get right on it.
Gerv
Lynx is probably faster still. But it doesn't mean you necessarily want to use it. This is not an excuse (Mozilla should be faster than it is), it's just an observation.
Gerv
The mozilla folks really ought to put up MD5s with the release.
Why? If they can tamper with the releases, they can tamper with the MD5s.
Anyway, the standard disclaimer we put on all releases applies: "If it doesn't melt your hard drive and send your tax evasion plans to the IRS, consider yourself lucky."
Gerv
Also make Mozilla reply as "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)".
That's a bit silly, isn't it? You'll get served IE DOM content, and it won't render correctly.
Gerv
Wow, what a great release! I think that 0.9.3 really is a key step in the right direction for 1.0.
;-)
Has someone been cutting and pasting out of their "Slashdot comments" file?
Gerv
Actually, it goes 0.9.9, 0.9.10, 0.9.11,...
Gerv
Read the release notes. Arabic language support should work.
Gerv
If, like me, you can't give blood for whatever reason, you can donate to the American Red Cross of Greater New York here.
Gerv