Hello Everyone,
Sorry about this. If we knew about the retina issue we would have reconsidered the switch to Oracle’s Java 1.7. Supposedly it is already fixed in the Java 1.8 dev builds and it will be back-ported to java 7 once it it stable enough. Unfortunately we will have to wait until then. Glider 1.7 will still use Apple’s Java 6 so it should look crisp on retina displays. They should get it back-ported soon because 1.8 is due to be released in a few months.
Regards,
M.Y. Developers
So, just gotta wait a few months???
Unfortunately yes, java 7 update 40 is scheduled to be out in late August. Please send us a screenshot of the blurry-text and we will be sure to vote on the bug and put up more data for them to see. The only viable alternative is to backport everything in Glider to Java 1.6. Not only is this a considerable task and would require us to remove some features but Apple’s implementation of Java 6 is no longer supported so it is not a long term solution.
Thanks for understanding,
M.Y. Developers
Here is a pic of what it looks like on a retina MBP. The text in the list on the right side is the “Window” menu item, note how it’s text looks fine but the actual editor/IDE is blurry.
It looks like the issue has been fixed in netbeans(https://netbeans.org/bugzilla/show_bug.cgi?id=215141) and in Java7(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8000629). So does this mean we can see a solution sooner?
Hello Chevol,
The bug status in netbeans is “resolved, won’t fix.” Unfortunately they can’t do anything about the java bug. We are probably just going to backport everything back to java 6. End of August is just too long away and who knows, java 7 update 40 might even get delayed.
Regards,
M.Y. Developers
So, just gotta wait a few months???
Unfortunately yes, java 7 update 40 is scheduled to be out in late August. Please send us a screenshot of the blurry-text and we will be sure to vote on the bug and put up more data for them to see. The only viable alternative is to backport everything in Glider to Java 1.6. Not only is this a considerable task and would require us to remove some features but Apple’s implementation of Java 6 is no longer supported so it is not a long term solution.
Thanks for understanding,
M.Y. Developers
Here is a pic of what it looks like on a retina MBP. The text in the list on the right side is the “Window” menu item, note how it’s text looks fine but the actual editor/IDE is blurry.
It looks like the issue has been fixed in netbeans(https://netbeans.org/bugzilla/show_bug.cgi?id=215141) and in Java7(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8000629). So does this mean we can see a solution sooner?
Hello Chevol,
The bug status in netbeans is “resolved, won’t fix.” Unfortunately they can’t do anything about the java bug. We are probably just going to backport everything back to java 6. End of August is just too long away and who knows, java 7 update 40 might even get delayed.
Regards,
M.Y. Developers
That would be great, I hate not being able to use Glider 1.9 yet.
Please try this version:
http://www.mydevelopersgames.com/Lua%20Glider%20InstallerJ7u40Dev.dmg
And let us know if the fonts are retina sharp. That version of Glider uses a dev build of Java 7 with many mac specific bugs fixed.
Regards,
M.Y. Developers
Just tried it out.
Fonts are not blurry any more.
yup, its now working fine for me. No more blurry text!!!
Hello Everyone,
Sounds great! Looks like the java experience for Mac is improving. By the time they release it for good it can only get better. Please let us know if anything strange occurs. We tested it as much as we could on our Macs but things always work great on the dev machine.
Regards,
M.Y. Developers
awesome - works for me too!
Hello Everyone,
Just checking in to see if anyone is having issues with the java 7 dev version. Please let us know about anything
Regards,
M.Y. Developers
I haven’t had any issues with it so far. Sometimes when time machine does its backup Glider hangs and says its using like 200%+ but I’ve been shrugging it off.
Hello Chevol,
Thanks for the report. How often does this problem occur? Never tested it with time machine before, that is def. a combination worth testing.
Regards,
M.Y. Developers