retina displays

3 views
Skip to first unread message

Patrick Klug

unread,
Apr 30, 2013, 8:07:52 PM4/30/13
to node-...@googlegroups.com
Has anyone got experience with node-webkit on Retina displays. Our game doesn't seem to run all too well and before I try to hire someone who could help us I wanted to see if there are known issues/prior experiences with this?

Patrick

Marc Torruella

unread,
May 1, 2013, 2:58:22 AM5/1/13
to node-...@googlegroups.com
The only thing i know about retina is that it takes advantage of image resolution but all your markup has to be the same as for the regular display... so positioning is on a 1024x768 basis... i guess you mean something else... but here you have what i know :-)


On Wed, May 1, 2013 at 2:07 AM, Patrick Klug <patric...@gmail.com> wrote:
Has anyone got experience with node-webkit on Retina displays. Our game doesn't seem to run all too well and before I try to hire someone who could help us I wanted to see if there are known issues/prior experiences with this?

Patrick

--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Michael Latta

unread,
May 1, 2013, 8:01:40 AM5/1/13
to node-...@googlegroups.com
Without the proper CSS any image is assumed to be non-retina.  There is a WWDC video on using retina resolution images.  But, that is about Safari of course, no telling about Chromium.

Michael

Patrick Klug

unread,
May 1, 2013, 8:31:26 AM5/1/13
to node-...@googlegroups.com
I think there might be an issue with node-webkit:


About the Retina bug: When opening the defaultBrowser.html file everything works fine. The bug lies in the packaging.
Message has been deleted

Maxime Istasse

unread,
May 2, 2013, 10:21:31 AM5/2/13
to node-...@googlegroups.com
So when you run your packaged app (the one that must each time decompress in temporary files), you got a bug?
I really think such a packaging SHOULD'NT be used by big projects... imagine how a SSD disk would suffer.
I would be pretty curious to test my packaging method(everything into a single HTML file), it should be as if we didn't package.

The fact is I haven't improved it this week as nobody seemed interested and it perfectly fits to my habits but not otherwise. So maybe a conversion (either of my converter, either of your program) would be necessary.

Wishing you the best,
Maxime

Patrick Klug

unread,
May 2, 2013, 5:54:43 PM5/2/13
to node-...@googlegroups.com
no sure I understand you. On Mac OS I just added a app.nw folder so there is no decompressing going on.

Patrick


Maxime Istasse

unread,
May 3, 2013, 2:00:05 PM5/3/13
to node-...@googlegroups.com
Not sure I'm understanding you well either (have no Mac), but if by app.nw you mean archive, then I can be right. And as you talked about a packaged app, I went on this way.

Yes there would be, because otherwise, the browser couldn't access the datas. It has no built way to access zipped files into an archive. "your app.nw" (zipped file renamed, I mean).
It thus has to decompress it into temporary files to access it.
Reply all
Reply to author
Forward
0 new messages