voludu2 wrote:Is it possible for the script writers to agree on some resources they use in common, and set some flag or property to indicate successful loading of these bits? Every script can then check whether these bits have been loaded already, and only load them if it is necessary.
Unfortunately, not really. Because just because it hasn't loaded YET doesn't mean it isn't already queued to load.
The only way to really resolve this is to merge the projects -- if Twister wants to do that, I'd be game.
JS actually really sucks for this whole system... And the fact that we are all hacking an undocumented API, it all becomes that much more challenging.
That said, my offer for Twister to have access to the TB code for both reading and contribution stands, regardless of merging the projects or not.