Single EC_Script absolutely, much more efficient speed and memory wise. Our script engines are not particularly cheap.
Another option is to use the app name and app class in EC_Script, this way you can have the component in all of the doors but they share the same script engine. With this tech "me" in the script refers to the entity that has the actual scriptRef set. But every instance will get a conatructor call that passes the real "me" entity. This might sound complicated but it's really not, check out scenes/Avatar script files. At least simpleavatar.js uses this tech. Best Regards, Jonne Nauha Adminotech developer On 29.3.2012, at 19.41, Vik <vyetr...@gmail.com> wrote: > Hi, > If I have in scene hundred of similar objects (for example door. > 001,...door.099), i can attach to each object javascript for actions > (say "OpenDoor"). Or I can attach one script to scene and in this > script distinguish door by name at run time. > Which solution is better. I mean 'better" from architectural point > of view of Tundra in terms of performance and memory consumption. > Thanks > Vik. > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org -- http://groups.google.com/group/realxtend http://www.realxtend.org
