The JOGL renderer is used with the Raspberry Pi too, it uses OpenGL-ES under GNU Linux on ARM. Do you consider it is an extended feature?
Does it mean that JMonkeyEngine will use its own windowing toolkit? This information is important for me, I’d like to know whether I’ll have to use the NEWT Input API when it’s ready and how JMonkeyEngine will become able to manage several windows at the same time.
jME will abstract the windowing stuffs over whatever backend is used. Some of this is a bit convoluted at the moment, we intend to change that with the new unified renderer, then we will just need some way to tell the renderer to open a window, pass a link to an AWT surface etc. So theres nothing in the way of using NEWT in the background but the whole NEWT API won’t be made accessible from the jME side. If you want to change the current renderer so that it uses the APIs you deem most appropriate for jME we can use that code to adapt the new renderer.
Edit: And for the RasPI support etc… I guess the “plugability” of JOGL would be an extended feature, yes. From what I get we’d simply take a premade RasPI JOGL version and plug in our OpenGL(ES) renderer. We could just as well use a native interface though, if configuring JOGL takes more time than adapting the render code to do something you can regard that as “extended”