updates for retina

  • I was reading around about the new Macbook Pro retina display today and there were quite a lot of comments about how apps may need updating to support it. Chrome was mentioned as an app which doesn't look good currently, I saw the pictures, it's not nice. I understand apps needing 2x artwork piece, that makes sense. However I'm unsure how a normal app (like Chrome) needs special treatment just drawing to the screen and I didn't find a document describing 'all the things you might have to do to make your application retina-compatible', is there one? I thought the idea was it would just work.

    My impression of retina was that the display was beyond the eye's resolution ability so it didn't matter what the resolution of the underlying screen is, the system maps it on, antialiases it and, because of the real underlying screen pixel resolution, you can't tell the difference. (inserts a bit of doubt there, antialiased is never as good)

    Total curio for me here, I don't have an app which needs it, but nor can I find a document which describes potential compatibility issues and work which might be required. Is there one?
  • On Jun 15, 2012, at 10:21 AM, Roland King wrote:

    > I was reading around about the new Macbook Pro retina display today and there were quite a lot of comments about how apps may need updating to support it. Chrome was mentioned as an app which doesn't look good currently, I saw the pictures, it's not nice. I understand apps needing 2x artwork piece, that makes sense. However I'm unsure how a normal app (like Chrome) needs special treatment just drawing to the screen and I didn't find a document describing 'all the things you might have to do to make your application retina-compatible', is there one? I thought the idea was it would just work.

    Two of my products that make heavy use of Core Animation need to be revised to work correctly in HiDPI mode. One of them has fuzzy animated text, and the other puts everything in the wrong place completely. My other six products work perfectly in HiDPI mode without change, but they do not use any explicit animations. The developer documentation does suggest that there may be some applications that need changes, and I think Core Animation may be a key piece of that. I haven't tackled the fixes yet, but I know I'm using one method that is identified in the documentation as problematic in HiDPI mode, and I think some of my arithmetic may have assumed pixels and points are equivalent.

    --

    Bill Cheeseman - <bill...>
  • hi-

    On Jun 15, 2012, at 10:21 AM, Roland King wrote:

    > I understand apps needing 2x artwork piece, that makes sense.

    Why does that make sense?

    If your tool icon needs to be 32x32 pixels then make a TIFF/PNG 64x64 (or 128x128 or 256x256) and let NSImage do the rest.

    for icns, add all representations (as is required anyways).

    ... maybe I'm somewhat ignorant - but not having a retina display to play with yet is a handicap.

    thanks!-

    -lance
  • Le 15 juin 2012 à 16:21, Roland King a écrit :

    > I was reading around about the new Macbook Pro retina display today and there were quite a lot of comments about how apps may need updating to support it. Chrome was mentioned as an app which doesn't look good currently, I saw the pictures, it's not nice. I understand apps needing 2x artwork piece, that makes sense. However I'm unsure how a normal app (like Chrome) needs special treatment

    Because Chrome is not a "Normal" app, and it does not just use standard API for rendering. Usually everything just works. You can already test that on your standard screen by enabling HiDPI using the Quartz Debug utility that used to be part of Xcode but is now distributed in an extra package (the Graphic Tools package IIRC).

    It may not reveal subtle rendering bug, but will let you know if something goes really wrong in your drawing code, and coordinate computation.

    > just drawing to the screen and I didn't find a document describing 'all the things you might have to do to make your application retina-compatible', is there one? I thought the idea was it would just work.
    >
    > My impression of retina was that the display was beyond the eye's resolution ability so it didn't matter what the resolution of the underlying screen is, the system maps it on, antialiases it and, because of the real underlying screen pixel resolution, you can't tell the difference. (inserts a bit of doubt there, antialiased is never as good)
    >
    > Total curio for me here, I don't have an app which needs it, but nor can I find a document which describes potential compatibility issues and work which might be required. Is there one?

    -- Jean-Daniel
  • On Jun 15, 2012, at 8:02 AM, Jean-Daniel Dupas wrote:

    > Because Chrome is not a "Normal" app, and it does not just use standard API for rendering.

    To be precise: Chrome draws web page contents into offscreen pixmaps and then copies those to the screen. (This is for security: the drawing is done by WebKit in sandboxed renderer processes, using shared-memory buffers.) The problem is that it bases the pixmap dimensions on the logical size (in view coordinates) of the window, not the actual size in device pixels.

    BTW, this seems to have been fixed in the latest developer-channel builds of Chrome, since I just got my RetinaBook today and Chrome doesn't look jaggy to me. Presumably the fix will be ported into the stable releases too.

    (I'm sure Safari at one point had the same issue since it also uses sandboxed renderers, but of course they fixed that in time before the product release, just like the other retina-savvy Apple apps.)

    —Jens
  • On Jun 15, 2012, at 9:21 AM, Roland King wrote:

    > I didn't find a document describing 'all the things you might have to do to make your application retina-compatible', is there one?

    High Resolution Guidelines for OS X
    <https://developer.apple.com/library/mac/#documentation/GraphicsAnimation/Co
    nceptual/HighResolutionOSX/Introduction/Introduction.html
    >

    Lion AppKit release notes, "Changes for Resolution Independence".
    <https://developer.apple.com/library/mac/releasenotes/Cocoa/AppKit.html#10_7
    HighResolution
    >

    Regards,
    Ken
  • On Jun 15, 2012, at 11:05 PM, Ken Thomases wrote:


    Is there an equivalent iOS document?
previous month june 2012 next month
MTWTFSS
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30  
Go to today