I have to say this basically has made DOOGLE obsolete however
here is some things I have learnt from it:
- Separate out OpenGL implementation abstractions. E.g. Webgl vs
desktop gl.
This may not be required because the aim is towards non web based
output but I think something like GWT[0] would bring an
interesting dimension to such a library.
Also include the opengl util stuff including textures ext. in
this with having it abstracted.
- If you think your going 3d do it first, its harder (yes) but
going 2d from that is pretty much load image into texture, load
mapping coords and display.
- If you can explore some kind of factory mechanism, I never did
but versioning implementations between sub packages was
absolutely messy. Perhaps a registrations system. That works
quite well for my web service framework with routes, models,
update functions ext.
- From experience on Windows, the client window area is a little
buggy. You may have to make up for that in making sure its exact
size requested. For an idea of what I did check out[1][2]
Some ideas I had for DOOGLE but really didn't even get close to
doing:
- Able to (out of process) query and manipulate the gui with a
permission mechanism.
- Output html/css/js with a routing mechanism to work as a web
server routes.
From what I have considered the context would need to change on
request, which would hold e.g. the actual request.
[0] http://www.gwtproject.org/
[1]
https://github.com/rikkimax/DOOGLE/blob/master/resources/shaders/button_popup.frag
[2]
https://github.com/rikkimax/DOOGLE/blob/master/source/StandardPlatformWindow/doogle/window/opengl/window_win.d#L28
