>This question applies to the other kinds of controls as well: should
>the "classes" be just a particular instance of an object, or a truly
>abstract collection of property/value pairs? The former is how
>ToolBook does it and is more xTalk like, while the latter is more like
>real OO languages but would probably be harder to learn. There are
>also a lot of issues related to where and how that data is stored
>(attached to a stack? In a new kind of object? In a text file that's
>#included?)
If an object is MetaCard is more conceptual than you can conceivably has
subclasses something I think R�diger was referring to with groups. If
classes in MetaCard were actual objects I think you would just need a
property which would declare a button,field, or group a new object and
that object would remain locked(undeletable) while it's children exist.
It would be nice however to just say:
declare script of button 1 as newobject
local x
put 5 into x
newobject y
set the someproperty of y to x
delete newobject
regards,
Tuviah Snyder
Diskotek
Custom Application Development & SuperCard/HyperCard Conversion at a low
price
