Hey, [EMAIL PROTECTED] remember when you typed: > That is our biggest problem. We like to code. We add something, > announce it to the list. Some stuff big enough finds it's way to the > WiKi. But we are missing some _real_ documentation, with all features
In a large "foot in the mouth" venture, I now see the virtue of the wiki. :) I have never liked wikis, but darn it -- it sure is good in this situation. Here are my current thoughts: I have started reading some python books. Realize my mind often doesn't work like a programmer, but I want to be able to read some code and follow what's happening. I had no idea what *happened* when freevo ran. I've been looking in the code and trying to figure stuff out. (I've added a few minimal things to the wiki, and will continue to add more as I figure stuff out) To be honest, I don't *want* you guys to document stuff. Code, code, code, code!!! I am trying to learn enough to understand what is happening. I'm going to try to look at some more freevo code, and document the particularly thin parts. What needs documentation the most right now? I'm working on the XML stuff now -- it was a big thrill when I had figured out what to add to the fxd file to select a different audio track. (It turns out I think something is wrong with the .avi -- but when my trial matched Aubin's suggestion, there was great jubillation. :) Please lets stick with the wiki. My job often causes me to be busy in spurts. (ie, see last 3 months...) The wiki allows for collaboration, which is good. If I am unavailable, I sure don't want documentation to stop! Do you guys read the wiki diffs as they are made? (the changes get mailed to somewhere...) If I interpret code wrong, and dont' have the hardware to test on -- I want to make sure I'm being double checked. Incorrect documentation is worse than no documentation. :) Sorry for this long email, but I want to make sure that the programmers can continue to program. :) (Oh, and please keep commenting code when possible, especially if I'll be perusing it to try wikiing out some documentation) Thanks!!! -Shawn -- Shawn Powers Technology Director Inland Lakes Schools 231-238-6868 x174 http://techcorner.inland.k12.mi.us ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
