I think the strength of livecode is that it can build very simple and also very complex things. I wish I was more familiar with behaviors and their use cases (out of all the stuff I build every day in livecode I have never implemented a behavior script I have written) but I imagine this is similar to method chaining in other languages?
Also, Does someone have that killer example stack or article/lesson on behaviors that sums it all up? Andrew On Fri, Jul 12, 2013 at 1:48 PM, John Dixon <dixo...@hotmail.co.uk> wrote: > > > > Date: Fri, 12 Jul 2013 10:58:29 -0700 > > From: ambassa...@fourthworld.com > > To: use-livecode@lists.runrev.com > > Subject: Re: Chained Behaviors > > > Nested behaviors simply extend the value of such a mechanism, at long > > last giving xTalk one of the most valuable aspects of OOP: subclasses. > > Richard... > > I hear what you say, but does an xTalk language need to go down this road > ?... or to perhaps put a direct way... Should an xTalk language be going > down this road ?... What I am worried about is that there are a lot of > people jumping on the 'open source' bandwagon... wanting to change things > for what they see as improvement whilst completely forgetting that it is > simplicity not complexity that has got xTalk where it is today... > > John Craig and I have debated this very point for hours... but all that > has come outof our discussions is that we agree to disagree... > > Dixie > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Andrew Kluthe and...@ctech.me _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
