David, I agree with you in terms of resources and bandwidth Simile has! Thanks for coming forward to start making a plan for documentation.
I will start converting documentation from http://simile.mit.edu/wiki/Timeline http://simile.mit.edu/wiki/Exhibit/For_Authors http://simile.mit.edu/wiki/Timeplot to new wiki http://code.google.com/p/simile-widgets/w/list Will it be just copy paste with linking to proper pages? To give my background: I am Portal developer and work with leading technology company. I have around 4 years experience and I did my Masters in Computer Science from Carnegie Mellon University. This background was required as you will know which tasks you can give me. I can start reading code for exhibit then timeline if that sounds ok? Let me know what you think. -Brian On Oct 3, 1:37 am, David Huynh <[EMAIL PROTECTED]> wrote: > Hi Brian, > > Thank you for raising this issue and for offering to help. You're > definitely right that more documentation is needed, especially at the > code level. It's really not a question of whether or not that's > desirable; it's a question of how, given the limited resources that we > have. More specifically, no one here, including me, is paid to help out; > we are all volunteers. I'm actually very encouraged to see more and more > people are starting to chip in on answering other people's questions. > > Your offering to help 2 hours a day is very much appreciated! That is > very generous. Right now, I think it's more pressing to have the > documentation moved from our old wiki > http://simile.mit.edu/wiki/Timeline > http://simile.mit.edu/wiki/Exhibit/For_Authors > http://simile.mit.edu/wiki/Timeplot > to our new wiki > http://code.google.com/p/simile-widgets/w/list > Once that's done we can start thinking more about documenting the code > itself. Thoughts? > > David > > Brian wrote: > > David, > > > You always come out with great suggestions and by reading your posts I > > learn a lot! > > > I think it will be a great help for the community if there is some doc > > of how things work at code level, if now anybody wants to do anything > > which is little out of track from common examples, hundreds of > > questions and doubts are raised. Reading the code line by line and > > debugging in firebug of what is doing is one of things to know what's > > going on inside but I guess if there is something like utility wiki > > created describing different uses of different scripts and functions, > > it would be of immense use and rather than people concentraing on > > solving small issues, we will see actually people contributing faster > > as they understand the code now and not "hacks". They are very > > brilliant people on this community and if the core developers of > > simile come forward and help us creating something like a simple API > > that would be great, I can help in anyway you want me to in this task, > > I can devote 2 hours per day for this task as needed. > > > One of the great things of Java is it's API is very well documented > > and even the dumber knows how to hack around it, something on the > > similiar lines is needed for simile, same thing is there with Yahoo > > User Interface toolkit where every javascript function is explained in > > detail and that's what made them so powerful as thousands of people > > started writing the code and enhancing YUI to a level which we haven't > > seen. > > > Please discuss on what you guys think. > > > Thanks, > > Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
