At 8:27 PM +0100 12/15/00, Clars wrote:
>Thanks again for input, all.
>
>Karina - any sources for naming conventons? I use p for property and g
>or m for global variables(project global or movie global), but that's
>about it.
>
>Jakob- I sent my post before I read yours. I suppose that specifically
>writing seemingly redundant access handlers gives a good
>clue-at-a-glance which properties are being accessed from outside.
>
>See you all soon, with more basic questions - after two years of
>behaviors, I'm going to try to figure out the how and why of
>parent/child.
>
Wow, an entire discussion on OOP, and I'm out of the office for one
morning. I think Karina summed up what I would have said very well.
But just to summarize, I'm a strong believer in accessor methods
(both "getter" and "setter" methods). You should never access a
property by name outside of an object - objects "own" their property
variables. Naming conventions are a pain to learn but very useful in
the long run.
One quick comment. In your original message you mentioned that there
were five different properties that you wanted to get and/or set from
a behavior. What do you do with the property values you get back
from the behavior? Could you possibly do whatever you are doing
inside the behavior rather than asking the behavior for the value of
a property and operating on it outside the behavior?
If you get the underlying concept of behaviors, then parent scripts
are not too much more difficult. They provide a way of grouping
related code and data into a single place.
Good luck,
Irv
--
Lingo / Director / Shockwave development for all occasions.
(Over two millions lines of Lingo code served!)
[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!]
