Doc Formats
SourceForge seems to have settled back down of late, which is good. All the stats appear to be correct now and the CVS server is seemingly quicker than normal.
netWindows as a whole has been languashing in a sea of travel and work, but spending some quality time with pyMail and the documentation re-orginization are on my plate for the comming weeks. Ted Shroyer has suggested a format for the API documents similar to that of the JDK documentation (JavaDoc), but I have misgivings about maintainability. The web application geek in me instinctively wants to throw a database on the back end of this and generate everything on the fly, but it seems like overkill for something that only gets changed by developers and is already in CVS. I really do like the idea of having a frameset that helps navigate, but I think that the indexes and links should be created dynamically, I just don't have any good ideas how to make that happen on the back end. Another potential problem is the fact that our comments aren't our documentation, rather the documentation was extracted early for the sake of download weight (mistake?). Perhaps a well laid-out document structure is the right answer to both problems.