I wonder at what kind of resolution we will no longer need anti-aliasing. Did they provide any Retina screenshots with AA off? You'd think that with small enough of a pixel it would no longer be necessary.
There is no clear cut answer to that. Even at 10,000ppi you can still get visual artifacts without anti-aliasing. The problem is pixles are averaging a single point source over a 'full' pixel so with some patterns they can become vary sensitive to slight motions. Think chain link fence, all the pixels could be on the fence and it looks solid, or between them and it looks clear, and if your rotation it can swap between them.
Not there yet. I turned off AA in the Terminal and it looks smooth, but not completely. If I use a lower scaled resolution like 1440x900, then it looks even smoother, but again not completely smooth. So I guess an even higher dpi is needed. It would be interesting to see non-antialiased fonts on the iPhone which has a much higher dpi.
Applications need to be 'retina aware' to actually get the full resolution, otherwise they are told the resolution is 1440x900 (this doesn't include fonts, and other system-rendered features, which the OS can always render at full resolution). The program icons also need to be shipped in a higher resolution.
Apple does something called pixel doubling. If an application takes no action, it won't just be rendered smaller. Instead, Apple zooms the whole app, causing everything to get very fuzzy.
I'm confused about this. I've been running the sept 11 Nightly and it has retina support. Did they take it out, and this is just about re-adding it?
Prior to that I used the "retinizer" app and the about:config hack to disable acceleration, but performance was really bad. Since running nightly, it has been fully retina enabled and smooth.
Relative term, and totally subjective. I have an rMBP, and use Firefox (as well as InDesign) all the time, and it's not horrible. If your entire screen looked that way, you wouldn't even notice.
This is fabulous, now if I could get it for the iPad, tell it to lie about what kind of device I was so that I would not be stuck with the 'mobile' version of Gmail. That would be a usability win.
Why do you need "support" for a screen resolution? PC's have had different screen resolutions forever, why were there never news articles about "Firefox Gets Support For 1280x1024" or "Firefox Gets Support For 1920x1200"?
1920x1200 does not equal high dpi. Think 1920x1200 on a 10" display. If your app runs on a high DPI screen, and the OS and your app has no support for this, all fonts and UI elements become tiny, which is unacceptable.
Windows XP had abysmal support for high DPI which usually resulted in broken UI layout. Vista introduced "DPI virtualization" requiring you to declare and provide explicit support for variable dpi in your application. Otherwise it is run at 96 DPI and raster scaling is applied. This prevents any UI layout issues but results in a a blurry image. I guess Apple uses the same approach: if your app has no explicit support, it runs under raster scaling.
No, Firefox is at v15. v16 will be released on Oct 9th. Personally, I just run the Nightly (http://nightly.mozilla.org/) and get an update every day. It's simply "today's build."
The version number is meaningless. What is meaningful, however, is getting millions of people to help test beta browsers. If Chrome is your browser of choice then help test the Canary builds (https://tools.google.com/dlpage/chromesxs)
That joke never gets old, let's keep saying it every time a Chrome or Firefox version comes out! (Or like here, just because a Chrome or Firefox version number was mentioned in a random article.)
[+] [-] phoboslab|13 years ago|reply
I hope they didn't screw it up as bad as Apple did with Safari: http://www.phoboslab.org/log/2012/09/drawing-pixels-is-hard
Edit: judging from some comments in the source, the Canvas element still uses a low resolution, so the test case should work as expected in any case.
[+] [-] tathagata|13 years ago|reply
[+] [-] paulrouget|13 years ago|reply
[+] [-] akurilin|13 years ago|reply
[+] [-] Retric|13 years ago|reply
[+] [-] tathagata|13 years ago|reply
[+] [-] cpach|13 years ago|reply
[+] [-] listic|13 years ago|reply
[+] [-] keeperofdakeys|13 years ago|reply
[+] [-] cmelbye|13 years ago|reply
[+] [-] cheald|13 years ago|reply
[+] [-] asadotzler|13 years ago|reply
[+] [-] chmars|13 years ago|reply
[+] [-] chrisdroukas|13 years ago|reply
[+] [-] navs|13 years ago|reply
[+] [-] chmars|13 years ago|reply
[+] [-] lawnchair_larry|13 years ago|reply
Prior to that I used the "retinizer" app and the about:config hack to disable acceleration, but performance was really bad. Since running nightly, it has been fully retina enabled and smooth.
[+] [-] cheald|13 years ago|reply
[+] [-] teilo|13 years ago|reply
[+] [-] ChuckMcM|13 years ago|reply
[+] [-] eurleif|13 years ago|reply
[+] [-] Aardwolf|13 years ago|reply
[+] [-] ringm|13 years ago|reply
Windows XP had abysmal support for high DPI which usually resulted in broken UI layout. Vista introduced "DPI virtualization" requiring you to declare and provide explicit support for variable dpi in your application. Otherwise it is run at 96 DPI and raster scaling is applied. This prevents any UI layout issues but results in a a blurry image. I guess Apple uses the same approach: if your app has no explicit support, it runs under raster scaling.
[+] [-] mh-|13 years ago|reply
http://i.imgur.com/pbGvv.png
whole thing looks like this.
[+] [-] jonchang|13 years ago|reply
Today's nightly: http://hg.mozilla.org/mozilla-central/rev/c09a0c022b2e
Last retina changeset: https://hg.mozilla.org/mozilla-central/rev/1d3de8da2508
Shortlog: https://hg.mozilla.org/mozilla-central/shortlog
[+] [-] melling|13 years ago|reply
https://bugzilla.mozilla.org/show_bug.cgi?id=674373
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] yottabyte47|13 years ago|reply
[+] [-] melling|13 years ago|reply
The version number is meaningless. What is meaningful, however, is getting millions of people to help test beta browsers. If Chrome is your browser of choice then help test the Canary builds (https://tools.google.com/dlpage/chromesxs)
[+] [-] azakai|13 years ago|reply