well I can help you with the documentation but if I do it I want to do it properly.
1. presentation of the framework, layering, base concepts, most comonly used combinations of the provided functionality and so on... There is no mention of that What is the objective of the library. There is only one mention that it replaces glut but there is no statement what exactly it is suppose to do. Me as new developer I have to look for references regarding glut to understand what free glut is suppose to do...
2. differences between operating systems. maybe some features are not available or work in the same way on all systems.
3. how to build depending on the platform/IDE
4. clear explanations of the examples and how they are done (I don't know even if they have some readme at the moment)
5. use cases means how to use the functionality present in the library. This is usually done using small code snipets that are extremly focused on a specific feature. Use
cases are also used to show the chain of calls inside the library so that developers can see the dependencies.
They can present some more complex combination of functionalities depending on what is the final target.
I mean in the end a software is used by others to make other software. GLUT has some target public. How does this public reaches most common targets for which glut was developped?...
I mean you can be a closed comunity where everyone is in this project since the start of it and find themselfes inside the code but for new comers like me is like a labirinth...
6. it would probably need some appnotes with current known issues, features to implement based on a roadmap so people can hook in if they want to help.
What you sent me some time ago had 3 html files as documentation. Maybe there are some other docs but I didn't look enough to find them.
In the same archive there were some examples is true (4 if I'm not wrong) but deffinetly weren't
more than that.
can you give me a link to those examples that you mentioned?
It would be cool if we can provide a man for linux users and a chm for windows users and html files in a zip for the rest of the crowd.
I have a small tool that takes hand made html files and doxygen output and puts them directly in a chm...
Ok maybe I'm asking too much.
I'm working in support and I'm used to do this. (ask a lot in terms of sdk quality)
What I can say is that the state of glut homepage and the docs it really sets me off from programming.
I kind of had hopes to make a game engine on top but the interaction was so brutal. Maybe it was not meant for this purpose. But it wasn't written anywhere.
In any case, do i really need to reverse engineer the implementation to understand what I can/can't do? at this point pretty much yes.
hope that I didn't piss off the founders cause I made their "child" look ugly but at this moment this what I
Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.