Leon Messerschmidt wrote:
> The JPython support should not interfere with any existing stuff in
> ScreenLoader.
+1
> Only after failure to find a java screen in the normal way
> does the code start looking for a JPython class.
Good, but maybe we could have a chain of loaders, with configurable
order?
> There is also an option in
> the TR.properties to disable the JPython stuff (will probably be disabled by
> default).
Again, maybe we could have JavaLoader, JPythonLoader, RhinoLoader that would
were responsible for loading and launching assemblers, and they could
be installed/removed at administarators discretion?
> We think JPython support could add some nice benefits to Turbine:
> 1. You don't need to recompile classes - just edit them and save (TDK
> newbies can actually create some screens without rebuilding)
> 2. Python is easy. Even designers might be able to write simple sceen
> code. <GASP> :-)
> 3. JPython can be used for rapid prototyping and then later on compiled to
> real .class files with jpythonc.
> 4. If you do development/debugging on a remote server (like we've done in
> the past) you can easily edit files without the need to remote recompile or
> upload .jar files.
All of these are really nice features, that would add yet more power to
Turbine...
Rafal
PS. A random thought:
What is Turbine? That's what makes your project spin! ;-)
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
