On Sun, Jun 19, 2011 at 2:38 PM, mrrick <[email protected]> wrote: > Hi Aaron, I just finished watching the presentation you did a few > years back and found it to be a very informative round-up of what > mootools is, how it works, and it's philosophy of classy writing. For > others who might like to see it (newbies like me) here is the link > > http://tv.adobe.com/watch/ajax-experience-2008/mootools-an-overview-by-aaron-newton/ > . > > Anyway, at the end you were going through your own extensions on > clientside (correct me if I'm wrong) and so decided to go back to the > clientside download to figure out if these items had been downloaded > when I downloaded core and more. They weren't right? Those are extra > right. Now you seem to be able to get everything straight from there > right? I had not seen it look that way before. Then I found > dev.clientside which I had not seen yet, is this new? and looks like a > great place to learn mootools. Thanks to you and whoever helped you > for this really great work making this all available for us to use and > understand. It really looks very well done and a lot of work went > into it. >
You can read about dev.clientcide.com here: http://www.clientcide.com/code-releases/clientcide-3-0-behavior-1-0-mootools-development-and-so-much-more/ The download page on Clientcide always allowed you to build the Clientcide libs with MooTools Core and More (though they start off disabled). Generally speaking, I recommend that you just download the packaged Core build from MooTools.net, but if you get it from Clientcide it's the same code. > When I click source in the second box below the html, the "clientside > source" it really gives us what all the dependencies are and what code > is actually required for that function right? This is meant for > helping us slim down our overall js by selecting only the features and > the dependencies for those features using the builder? I am really !!! > blown away!!! by the genius behind all this, not to mention the work > that must have been needed, it really is something. You could have > just kept this all to yourself or thrown it up on a site and let > others figure it out. > I'm not sure what you mean by the "second box below the html" - but if you go to the download page on Clientcide.com and choose what things you want you'll get all the dependencies you need for that code to work. If you leave MooTools Core and MooTools More disabled, you'll need to get those things separately. The work involved to make this system work isn't mine really; the dependency system used by MooTools (which itself is a fairly common practice of declaring in metadata what things are required for a component to work) is something used in nearly all MooTools projects. The builder itself isn't trivial, but not that hard either. A few day's worth of work. You can download and use it yourself. As for "keeping it to myself" well, that's what open source is all about, right? Here are more of my thoughts on the topic: http://www.clientcide.com/tools/why-you-should-consider-releasing-code/ > I'm sure there must be others to thank but you are the most visible. > http://mootools.net/developers > Please let us know if there is anything else you think we should know/ > understand about the new site dev.clientside, it is new right? to go > with your new release? > Again, see the blog post I linked to. You can find additional information about it in the readme on github.
