Hollywood forums

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sun, 13 Sep 2009 23:36:26 +0200

Hi!

I am just thinking loudly along an idea that recently came to my mind.

What about the possibility to include an applet to the script which could be launched on a separate interpreter environment. This embedded applet could be run as it would started with Execute(), however it would share the same executable.

For example it could make easily to merge handmade scripts with Designers creations or let them join several independent scripts to a large bundle without the need to touch the scripts.

What do you think?

Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 15 Sep 2009 00:34:23 +0200

Hi!

I am just thinking loudly along an idea that recently came to my mind.

What about the possibility to include an applet to the script which could be launched on a separate interpreter environment. This embedded applet could be run as it would started with Execute(), however it would share the same executable.

For example it could make easily to merge handmade scripts with Designers creations or let them join several independent scripts to a large bundle without the need to touch the scripts.

What do you think?

This would be a very cool feature and this has been on my mind for several years now. However, it would be huge task with lots of work to do. So I currently don't give this any priority because I want to increase functionality first before implementing any luxury features

Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 15 Sep 2009 10:09:13 +0100

This would be a very cool feature and this has been on my mind for several years now. However, it would be huge task with lots of work to do. So I currently don't give this any priority because I want to increase functionality first before implementing any luxury features

Of course network support is more important