|
Administrator
|
That's a good piece of news. Does it impact only applets?
Julien Gouesse | Personal blog | Website
|
|
Administrator
|
On 02/13/2012 05:21 PM, gouessej [via jogamp] wrote:
> > > That's a good piece of news. Does it impact only applets? It's generic for JAWT usage, ie OSX/Java7 implies offscreen layer only (as it is today). Only a dedicated NEWT window allows onscreen rendering on this target, hence NewtCanvasAWT is also forced to use the offscreen layering. ~Sven |
|
In reply to this post by Sven Gothel
Hello,
I am trying to back port use of CALayer rather than NSView into JSR-231. I plan to move over to JOGAMP as soon as possible but that can't be done right now. Can you share how you did this for JOGAMP? That might help me adapt JSR-231. Thanks for any help. -pax |
|
Administrator
|
On 08/02/2012 09:50 PM, pax [via jogamp] wrote:
> Hello, > > I am trying to back port use of CALayer rather than NSView into JSR-231. I > plan to move over to JOGAMP as soon as possible but that can't be done right now. > > Can you share how you did this for JOGAMP? That might help me adapt JSR-231. Sorry no time to support JOGL1. However, the source is available and following the git commit messages, you may see the change of architecture. Warning-1: I had to do quite a massive change of the underlying infrastructure to make it more generic and flexible allowing the CALayer hook. Warning-2: After SIGGRAPH I have to extend this to use the new FBO offscreen technique as this seems to be the only solution on certain OSX versions, see Bug 569 and Bug 599! ~Sven > > Thanks for any help. > > -pax > |
|
Administrator
|
In reply to this post by pax
Pax, you will waste a lot of time by trying to backport some features. I understand your position but you will get a lot of troubles with JOGL 1 and you will be alone to fix them. Sven is right.
Julien Gouesse | Personal blog | Website
|
|
Thank you Sven and gouessej for your input. I will spend some time to evaluate how much work it would take to move to JOGAMP before I back port. I need this to work on Java 7 on LINUX, OSX and Windows. I have had trouble building JOGAMP on OSX with Java 7, that was one of the reasons I went back to JOGL1.
Anyways, thanks again. |
|
Administrator
|
On 08/03/2012 08:27 PM, pax [via jogamp] wrote:
> Thank you Sven and gouessej for your input. I will spend some time to evaluate > how much work it would take to move to JOGAMP before I back port. Sure .. have I mentioned jackpot for auto-conversion ? (search forum) > I need this > to work on Java 7 on LINUX, OSX and Windows. JOGAMP simply works on Java7 on Linux, Windows .. We are aware of some open bugs regarding _latest_ OSX version, which will be fixed in 2-3 weeks (with help of members here), see Bug 569 and Bug 599! > I have had trouble building > JOGAMP on OSX with Java 7, that was one of the reasons I went back to JOGL1. Well, we build JOGAMP using Java6 - but a long time ago we managed to properly specify the build process to be able to use Java7 for compilation while still producing Java6 compatible code (which is a requirement). As Wade pointed out .. following the build steps closely should help. Fair enough .. I haven't tried to compile it w/ Java7 since I have no use case for this at this moment .. but will try in around 2 weeks .. just to make sure it works. > > Anyways, thanks again. You are very welcome. ~Sven PS: sorry for redundancy of information, just replying 'on the fly' .. |
Please re-test using the current rc11 release: http://forum.jogamp.org/Release-v2-0-rc11-td4026703.html Bug 569 https://jogamp.org/bugzilla/show_bug.cgi?id=569 and Bug 599 https://jogamp.org/bugzilla/show_bug.cgi?id=599 are both fixed in JogAmp JOGL 2.0-rc11! Please file a new bug in the bugzilla if you run into any issues compiling JogAmp using Java 7. |
| Free forum by Nabble | Edit this page |
