At 15:22 +0200 2001_08_16, Chnexus wrote:
>The Author of the demo is Jhon Kanding. He posted the URL on May 2th 2001.
>A .dcr is used there as Lingo libray in place of an LDM, bur the concept seems
>similar to the one described by Jakob Hede Madsen for an LDM, that's
>instantiating in
>RAM the structure of an object and accessing their props and method
>by an handle
>passed back to the main program before the .dcr closes.
Just like to add, that an important part of my idea is to extract the
"scripts" from the LDM into the instantiated object, so to
facilitating further instantiation of new objects.
Of course, you can always instantiate a new object, from an existing
one, by accessing its "script" property, but it seems more to point,
to explicitly store the script-references.
Actually, this "container object" could just be instantiated by the
LDM itself, and placed in the stage-scope in a convenient location,
such as a global, or in a property of the behavior placed on the LDM
sprite.
Doesn't really matter, just a matter of convenience for the Author.
When you have the "container object", you simply request "classes"
from there, instead of asking for them in a castLib. So instead of
writing:
xmlObject = script("xmlScript").new()
You would go:
xmlObject = gXmlScriptContainer.mGetScript("xmlScript").new()
In its simplest form.
And the gXmlScriptContainer would simply look up the scriptReference
from a propertyList.
Jakob
[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!]
