Gran Paradiso Alpha 1 Released
Friday December 8th, 2006
Gran Paradiso Alpha 1, an early developer milestone based on the Gecko 1.9 branch, has been released. Gran Paradiso, a mountain group located in Italy, is also the project codename for Firefox 3. There are no significant user interface changes. Core layout and rendering changes include use of Cairo as the default graphics library, use of Cocoa Widgets for MAC OSX builds and new SVG elements.
For more details, refer to Gran Paradiso Alpha 1 Release Notes.
Shouldn't the next major version be Firefox 2.5??
#7 Re: What abou Firefox 2.5?
by naylor83 <firstname.lastname@example.org>
Saturday December 9th, 2006 1:36 AM
#2 *scracthes head*
by john1987 <email@example.com>
Friday December 8th, 2006 7:23 PM
Isn't it a little early for alpha releases? Wasn't Firefox 3 scheduled for a year from now or am I, as per usual, highly confused?
John, Firefox 3 will hopefully be no later than a year from now. But the more important point is that work on Gecko 1.9 has been happening since August 2005. That's a years' worth of major changes that really need to be tested. We're hoping to finish landing the remaining big changes in the next month or two, and there will probably be another alpha release at that point, then betas.
In the meantime, we desperately need testing, especially of website compat, with these builds.
I'd be more than happy to test the new Gecko for website compat, but I'd also like to keep using my existing FF2.0. Would it be possible to provide an extension along the lines of the (very successful) "IE Tab" that uses the new page renderer in the existing FF window? Or am I fundamentally not getting it?
This is an alpha for Gecko 1.9. the rendering engine, not for Firefox per se (thus the "no significant user interface changes"). Given the nature of the changes that will be in Gecko for 1.9, getting early testing to help find bugs and regressions is imperative.
BTW, author of the article: It's Mac OS X; Mac is short for "Macintosh", not an abbreviation for Media Access Control, and there's a space between the abbreviation for "operating system" and the Roman numeral 10 ;)
Where did you hear that the X is supposed to represent a numeral rather than just be an "X"? Even Apple's own page (<http://www.apple.com/software/>) puts a version number after the X.
#15 Re: Re: Re: *scratches head*
Sunday December 10th, 2006 6:30 PM
"Mac OS X" is pronounced "Mac Oh Ess Ten": <http://en.wikipedia.org/wiki/Mac_OS_X>
But you don't have to accept a company's definitions for how its words should be pronounced (nor spelt, or we'd be writing PLAYSTATION in capitals all the time).
Personally I pronounce OS X as 'OS X' not 'OS 10', PNG as 'PNG' not 'ping', and am about 50/50 on whether it's 'SQL Server' or 'Sequel Server'. :)
I'd kind of like to try this release but it's a bit of a pain running multiple Firefoxes alongside each other so I'll probably wait for a beta or some such point where I know I can basically switch over to it, keeping the older one around only for testing.
(Oh, and Firefox? Pronounced 'Firefox', but abbreviated 'Ff' - a spluttering sound, or the musical symbol for 'very loud' - and certainly not 'Fx'.)
#24 Re: Re: Re: Re: *scratches head*
Monday December 11th, 2006 10:20 AM
Link to a real source (like apple.com), not wikipedia. Wikipedia is unreliable. Anyone and their grandmother can edit that page to say whatever they want.
#25 Re: Re: Re: Re: Re: *scratches head*
Monday December 11th, 2006 10:34 AM
Hardly a good argument. If your information is wrong, you can bet it'll be edited out rather quickly in many cases.
Just because anyone can edit Wikipedia does not mean that it doesn't have a lot of good information.
It's as stupid as: "Why use a computer? It could crash!".
#28 Re: Re: Re: Re: Re: Re: *scratches head*
Monday December 11th, 2006 8:18 PM
Ok, here's a better argument. Find a supporting source. If there's a reputable source to corroborate the Wikipedia article then I'll be more inclined to believe it. For example, is there a mention, or audio example, of the pronunciation on apple.com? All of the Apple users I have met have always called it "Oh Ess Ecks." That, combined with the fact that Apple lists version numbers as Mac OX X 10.3 (why would ten be listed twice in a row?) have lead me to believe that it's pronounced "Oh Ess Ecks." I have yet to find anything to change that opinion.
#29 Re: Re: Re: Re: Re: Re: Re: *scratches head*
Monday December 11th, 2006 10:53 PM
For what it's worth, Steve Jobs and just about everyone who has appeared on an Apple keynote presentation pronounces it as "OS ten".
#31 Re: Re: Re: Re: Re: Re: Re: *scratches head*
Tuesday December 12th, 2006 3:57 AM
Well, searching Google for "Mac OS X pronounced" finds a lot of people agree it's "ten": <http://www.google.co.uk/s…rch?q=mac+os+x+pronounced>
Easiest official source as someone already said would probably be to hear Steve Jobs or any of the people at Apple say it - should be easy enough to find video of something on the net. But this doc is from Apple, and says it's pronounced "ten": <http://docs.info.apple.co…article.html?artnum=25808>
#5 Compatibility with Fx 2.x profiles?
Friday December 8th, 2006 9:32 PM
Will running the new Alpha damage profiles created in Firefox 2 the way Firefox 2 would with profiles created in Firefox 1.5 if you switched back?
#6 Re: Compatibility with Fx 2.x profiles?
Friday December 8th, 2006 10:51 PM
I tested it on my work system, and noticed no issues when I went back to FF 2.0.
#8 but incompat themes can damage profiles
Saturday December 9th, 2006 11:19 AM
Reset your theme to the default before starting. The old one was ruined by my not doing that. But extension compatibility is otherwise excellent.
Will Gran Paradiso work with Vista RC2?
But most importantly, will Firefox 3 work with Vista SP2 ?
What is the difference between this and minefield?
Minefield is "current trunk as of today". This is "trunk from a certain day when we know things worked fairly well". We hope this will get somewhat wider testing than Minefield does.
If you're already using Minefield, just keep doing that! ;)
#11 Is SeaMonkey 1.1 compatible with SeaMonkey 1.0.6 p
by pkb351 <firstname.lastname@example.org>
Saturday December 9th, 2006 5:49 PM
Good mnews about the Cocoa widgets for OS X...this is jsut about the only item holding back OS X users from switching to products based on Gecko. If FireFox/ThunderBird/SeaMonkey is to be widely adopted on OS X te apps have to look like an OS X app. Moving to Cocoa widgets will finally make all Gecko based apps look like the "belong" on the Mac. Yippeee!
#12 Re: Is SeaMonkey 1.1 compatible with SeaMonkey 1.0
Sunday December 10th, 2006 6:28 AM
As opposed to, say, itunes? ;-)
#13 Re: Is SeaMonkey 1.1 compatible with SeaMonkey 1.0
Sunday December 10th, 2006 10:46 AM
"Moving to Cocoa widgets will finally make all Gecko based apps look like the "belong" on the Mac. Yippeee!"
No, Cocoa widgets has absolutely nothing to do with how the apps look. It simply means that the code in the mozilla/widget directory is written mostly in Cocoa instead of in Carbon.
#16 Oh, I misunderstood.
by pkb351 <email@example.com>
Sunday December 10th, 2006 6:36 PM
I misunderstood. Hopefully moving to Cocoa will make the app run faster.
Can someone explain the benifit of moving the code in the mozilla/widget directory from carbon to cocoa?
"Can someone explain the benifit of moving the code in the mozilla/widget directory from carbon to cocoa?"
Well, a native look for form widgets will come with the move, but as has been said that's not the reason, since the appropriate look _could_ be done in Carbon. (See, e.g., iTunes, which has got pulsing action blue buttons although it's a Carbon app.)
The move seems to be to save Mozilla from having to maintain _two_ sets of OS X widgets, since they need Cocoa widgets for Camino as it is. Besides, Cocoa widgets have some important advantages, and Cocoa is Apple's preferred environment for developers, so if you want to drop one set of widgets dropping Carbon ones makes more sense.
Have a look at what Josh Aas says:
On websites, like <http://www.morpheussoftware.net/> the dropdown menus at the top of each page have the text sorta fuzzy looking with red/blue tints around the edges of some of the letters when using Gran Paradiso Alpha 1. Also the right pixel or two of each line is cut off. Probably both related to Cario rendering now. Neither problem shows up in Firefox 2.0.
#41 Re: ClearType + Opacity rendering
Wednesday December 13th, 2006 11:55 AM
I'm not seeing that problem? Could you file that as a bug in bugzilla? <https://bugzilla.mozilla.org/enter_bug.cgi> File it under Core->GFX->Thebes
#42 Re: Re: ClearType + Opacity rendering
Thursday December 14th, 2006 10:13 AM
#30 ff3 and ff2 on the same machine without painhead?
Monday December 11th, 2006 11:29 PM
There is a way to have ff3 and ff2 installed and with one doesn't know about the other ?
#35 Re: ff3 and ff2 on the same machine without painhe
Tuesday December 12th, 2006 7:27 AM
Make use of profiles, they're not as obvious as in SeaMonkey (that adds a link to the profile manager in Windows start menu and even has it as a menu option in the app last time I looked). Here's a guide: <http://browserden.co.uk/b…efox-on-the-same-machine/>
Basically, use profile manager to create a profile for each firefox instance and then alter their shortcut icons to always load the correct profile.
#32 Still no support for European languages
Tuesday December 12th, 2006 4:16 AM
As evident from bugzilla, <https://bugzilla.mozilla.org/show_bug.cgi?id=9101> there will be no support for soft hyphenation as needed for European languages. The bug is one of the most voted for in FireFox
#33 Re: Still no support for European languages
Tuesday December 12th, 2006 4:31 AM
How is it evident from bugzilla that it won't happen? The most recent comment from a developer in that bug says it won't be fixed until the underlying code is rewritten. That rewriting is happening now (I'd link to the bug, but it'll just mean it'll get 200 comments from people complaining that it hasn't happened 5 years ago...), which should then mean they can improve the hyphenation (and a bunch of other things).
#34 Re: Still no support for European languages
Tuesday December 12th, 2006 6:35 AM
Actually, that bug is fixed in roc's tree (part of his textframe rewrite).
#39 Re: Re: Still no support for European languages
Tuesday December 12th, 2006 8:31 PM
that's good. but dynamic fonts is what I really want.
#37 Bug right here?
Tuesday December 12th, 2006 2:52 PM
Check out the post above this, on Mac with the alpha it's missing the containing box's bottom line for me.
#38 Re: Bug right here?
Tuesday December 12th, 2006 2:53 PM
And now it's not. Odd.
#43 Why mozilla is not acid2 compliant?
Sunday December 17th, 2006 4:53 AM
I thought that it would be for firefox 2... now the first alpha of firefox 3 is out and it still can't render the acid2 test right <http://www.webstandards.org/action/acid2/>
#44 Re: Why mozilla is not acid2 compliant?
Saturday December 23rd, 2006 10:18 AM
Try the latest in CVS, that appears to pass the Acid 2 test(the patches just landed shortly after this release). That will probably become Alpha 2. Firefox 3 by the end will completely pass the acid 2 test, don't worry.
#45 version numbering and naming of mozilla products
Saturday December 23rd, 2006 10:53 PM
the next release roadmap, as of now, is as follows: firefox 220.127.116.11.1.1, followed by 18.104.22.168.1.2, based on gecko version 22.214.171.124.1.1.1a future version numbers will be decided by the mozilla foundation. seamonkey will be renamed as vermincutler due to trademark issues new features of gecko 126.96.36.199.0.0a will be under the project name the "itching igloo" and the corresponding alpha 0.0.0.1a of firefox will be called as "gnawing gnat".
I've switched almost entirely to SeaMonkey because it's faster than Firefox and it isn't a memory hog. Using Firefox with any other app slows my computer to a crawl and needless to say any brower that needs 100% of my resources to browse the Internet isn't worth it. I switched to Firefox because of its speed, then security, then its rendering of CSS. Now I use anything BUT Firefox.
I've also checked out Opera and after a little tinkering I find it more than acceptable. Plus it passes the Acid2 test with flying colors. The only reason I haven't switched to Opera is because it doesn't render some CSS correctly.
My point is simple; if Firefox 3 becomes a continuation of Firefox 2 in any way, shape or form, I won't be using it. I need many apps open at one time and FF2 simply makes that impossible.