I spent the weekend working on resurrecting Cello, the (in principle) portable GUI built atop Cells. The only changes planned now are backing off various forkings and letting especially FreeGlut alone. That much worked pretty easily, and after noticing that my intended new font engine is actually a C++ library, well, I could make it work since I have my own C DLL anyway to get to the OS fonts, but for now I think I'll keep things simple and just go with my own glue to the OS font functionality. Stuff I am reading says this may be optimal anyway, because it can segue into texture fonts, apparently the best for performance and scalability, and even anti-aliasing.
So Cello (such as it is) looks to be under control, and so I want to get back to Cells and do up some documentation. The first thing will be a write-up of a nice little use case to which Cells were applied. I keep promising to do that, and tomorrow I will really try to Just Do It.
Then what?
Something that looks like a reference? Or a series of tutorials? Other?
kenny
On Mon, 10 Nov 2003 00:29:25 -0500, Kenny Tilton ktilton@nyc.rr.com wrote:
Something that looks like a reference? Or a series of tutorials? Other?
I'd very much prefer a simple tutorial ("do this, then do that, then...") followed by a complete reference manual which explains every exported symbol (macro, function, ...) in detail.
I usually shy away from packages without good reference docs ("look at the source, buddy") because they look like the author hasn't settled on a consistent API yet. If everything is written down, you - as a user - have a chance to decide what is expected behaviour and what is a bug (and what is missing). And the author forces himself to stay more or less on track, or at least alert the users of significant changes.
I'm trying to do these with my own published stuff at least.
Cheers, Edi.