Good reply Rolf. I'd like to add that you could create a Github Issue in regards to the doc fix:
http://github.com/mootools/mootools-core/issues http://github.com/mootools/mootools-more/issues Either we, or better yet, you guys can send a PR with the fix ;D. On Mon, Feb 20, 2012 at 2:48 PM, Rolf Langenhuijzen <[email protected]>wrote: > :) sometimes it's a bit abstract yes. > > Yes, updating the docs with examples is on the to-do list. Or better > said, wish list. Unfortunately most (core/more) developers are already > swamped with stuff that simply put there's little time left. The > community should step in and could start expanding docs with extra > demos/samples (jsfiddle embedded demos are preferred).. so yes, > something for the future! > > If you have learned some more (feel free to post questions while your > trying) collect them all and later decide if something is worthwhile > adding. > > On Feb 20, 9:14 pm, ghazal <[email protected]> wrote: > > Thanks a lot to everyone's replies. > > At least, there is a discussion on that matter. > > > > But my goal was specifically to point out that, and without your > > contributions, > > someone in the process of learning Mootools just from the Docs would > > have had a hard time solving this issue. > > > > I really think that Docs should be a little bit more self-explanatory > > sometimes. > > Or less confusing, like the keyboard method constructor example : > > > > http://mootools.net/docs/more/Interface/Keyboard#Keyboard > > > > My guess :http://jsfiddle.net/ghazal/svtF6/ >
