RE: OOP and ancestor access

[Ken Prat]

> 1 - directly manipulate the data
>
> 2 - make the data public by making it a global variable
>
> 3 - make it accessible via an accessor method

Maybe the problem is a conceptual one. The 'idea' of an accessor method ties
you into the 'idea' that "here is my data -- do with it what you will".

Perhaps a better idea is that of using messages. Rather than exposing a
slider's position in a method, have it send a message to the video object,
"update your frame based on this data, here it is." This leaves it up to the
video object to decide what to do with the data and the message, and the
slider can generate the data any way it pleases.


[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!]