Just to add to the OOP discussion from a more pragmatic point of view
In the projects I participate in there are often more than one programmer involved.
Imagine different programmers getting and setting properties in behaviors and parent
scripts they haven�t even written themselves...
We are very strict about this issue in these projects. No one gets access to props in
the scripts. Instead we tend to have a standard way of writing methods that does
common things (like changing position, changing member, changing text or whatever) so
we dont have to ask around all the time. If a sprite is supposed to be moveable thru
Lingo there is ALWAYS a handler called placeMe in that behavior. If the positioning is
done by loc, rect or whatever is only known by the guy responsible for that particular
script and may be changed at will by him/her as long as the functionality and handler
name stays the same. We also use the "getPropertyDescriptionList" dialog a lot. This
gets rid of many beginSprite and/or prepareFrame actions, and adds versatility to our
behaviors. I beleive this is one of the best features of Directors behaviors.
So in my opinion there is not only "OOP-puritanism" that speaks for this. It also
gives consistency and security to collaborative programming projects.
Bjarne
_______________________________________________________
If it's true that we are here to help others, then what exactly are the OTHERS here
for?
Bjarne Nyquist
Researcher, Lingo Programmer
The Interactive Institute, phone: +46-(0)8 783 24 74
www.interactiveinstitute.se
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
