> > Cool, I got the carousel. Regarding issues, I know where to find them > (bookmarked) and when I get better I'll try and contribute. The first > one I would look at is the problem with the waiter when using > requestHtml. I will be needing that, so I may understand that problem > sooner rather then later. >
Waiter moved over to MooTools More and got renamed to Spinner: http://www.mootools.net/docs/more/Interface/Spinner > On the carousel, what would have to be done to it to be worthy of > being included in more or clientside. If you want to through me a > challenge regarding its functionality let me know. I am new to JS but > not all programing, I should be able to get reasonably good in not too > much time. > It's probably not going to go into More any time soon, not because the code is bad but because More doesn't have specific UI implementations in it, though one day it might. There are a few things in More that are UI-ish, but for the most part, More is an extension of Core, not a UI library. The only real task that it needs is to update it's syntax for MooTools 1.3. As for adding it back to Clientcide, I doubt I'll do it, because then I have to maintain it. Again, it's not that the code is bad, my interest is just low on keeping it up to date. You should split it off and put it in the Forge if you want. > I would think that SimpleCarousel would be super popular. Are they > cheesy to use or buggy? What's the problem? > No problem. Just not important to me. At least for now. > In particular I would be very interested in reading about how you > learned to use mootools/JavaScript. What was your AHA! moment? You > know, that little piece of information/concept/analogy/metaphor that > pulled it all together for you? How do you conceptualize mootools/ > JavaScript programing that you find helpful? > If there's one single thing I recommend to anyone who wants to learn JavaScript and MooTools in particular it's this: read the source. I started using MooTools by reading through the source code and writing the documentation for every method. There were no docs before that. This required me to read every method and understand it before I could document it. Go read the entirety of MooTools Core and keep studying it until you understand what every line is doing. This exercise taught me a LOT about JavaScript. More than any single thing I've ever done.
