@gouessej said: Abstracting windowing stuffs is easy if and only if you don't allow the end users to modify the resolution, if you allow only the use of the default virtual monitor. @Momoko_Fan seems to talk above several renderers for the desktop whereas you talk about a single renderer :s I understand that you want the jME users to be "clients" of the jME API by wrapping NEWT or anything else.
Momoko is talking about different platforms renderers, i.e. desktop, iOS, Android, PS3 etc. Imo something like NEWT is backwards for us because the window frame is in almost all cases handled by the OS in the end and the programming environment already allows managing it. On desktop systems its convenient theres NEWT but for Android and iOS its kind of annoying to have an opaque library handle the native windows. On iOS for example the user can place and use the window any way he likes using XCode, on Android he can do that in the Android code of the application using the Android API.