Sorry for all the "rights?", that's awful. I had a question about the "clientside source" box on the source page of dev.clientside. I see quite a few items in the code, one to several characters long, that are bordered by a red outline. Is there some significant meaning to these outlines?
Thanks, Rick On Jun 19, 5: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 > linkhttp://tv.adobe.com/watch/ajax-experience-2008/mootools-an-overview-b... > . > > 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. > > 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 sure there must be others to thank but you are the most visible. > 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? > > So much to learn....Thanks again. > Rick > > On Jun 16, 11:23 am, Aaron Newton <[email protected]> wrote: > > > > > > > > >http://dev.clientcide.com/docs/behavior/Docs/Behavior.md#Behavior:cle... > > > Whenever you retire an element from the DOM you call > > myBehaviorInstance.cleanup(target). > > > When you define a filter, you can define a method that is invoked when an > > element is retired: > > > Behavior.addGlobalFilter('Foo', function(element, api){ > > var foo = new Foo(element); > > api.onCleanup(function(){ > > foo.destroy(); > > }); > > > }); > > On Thu, Jun 16, 2011 at 2:23 AM, Robert <[email protected]> wrote: > > > Btw., Aaron, does behaviors solve problems like this: > > > >http://groups.google.com/group/mootools-users/browse_frm/thread/6c63c... > > > I mean is there automatic object disposal when You destroy its > > > element? > > > You seam to said so here but I am not sure: > > > "If you change the DOM, you might break the JS that sets it up and you > > > always have to keep it in sync. You almost can’t do that here because > > > the DOM and it’s configuration is closely bound and in the same > > > place." > > > > Thanks, > > > > On Jun 15, 9:51 am, Aaron Newton <[email protected]> wrote: > > > > For those who may not have seen this: > > > > >http://www.clientcide.com/code-releases/clientcide-3-0-behavior-1-0-m...
