Geoff Canyon wrote:
The fact that there is an underlying permanent unique id for everything,
completely abstracted from the user. So you can change the name of a
column, or table, or layout, one time, in the database definition, and all
references to that object in scripts, other layouts, etc. will
automatically update -- or really, peeking behind the curtain, I'm guessing
they don't have to update at all because they all reference the permanent
unique id, and only render it into the name you know it by when they render
themselves for you to edit them.
So in LiveCode terms, imagine if you could rename a card, and any script
that referenced that card, or controls on it, wouldn't break, but just
automatically reflect the new name. Or rename a control, or a stack.
Ah, thanks. I wonder how the name lookup for every element in the
system affects performance.
It sounds like in this regard LC is no worse off than MySQL, SQLite, and
other systems where names are used directly.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
