I dunno how it is now, but last time I looked for documentation (I think somewhere around 3/4 of a year ago), "sparse" would be the most flattering word that I could apply to them.
Whereas the only thing that would make MochiKit docs better would be more examples. On 3/1/07, dsmath <[EMAIL PROTECTED]> wrote: > > > Hu? No documentation for dojo? Did you happen to notice the "Get > Help" tab on their front page? > Or the link to API docs: > http://dojotoolkit.org/api/ > > Or manuals linked from the wiki (also linked to from the home page): > http://manual.dojotoolkit.org/WikiHome > > I guess this pales in comparison to prototype's extensive external > documentation (2 mini-articles): > http://www.prototypejs.org/learn > > > On Feb 28, 12:39 pm, "Matthew Kwiecien" <[EMAIL PROTECTED]> wrote: > > >If Dojo was at its current state two years ago I would've used it > rather > > > > than writing my own library. > > > > Boy am I glad you chose to write your own. :) > > > > Don't get me wrong, Dojo is nice, but they seem to have the philosophy > that > > "REAL programmers don't document! If it was hard to write it should be > hard > > to understand!" > > > > > Maybe then it's reason to keep a designated "maintainer" for each > module > > > > Seconded, sounds like a good idea to me. > > > > -matt > > > > > -- | Matthew Kwiecien Webhosting | Design | delihosting.com | neoteria.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" 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/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
