Hi,
Previously we (Frank and myself) mentioned that we were working on adding
support to create screen code with JPython. We are ready to add the first
working version to the cvs tree. Because it involves changes to
ScreenLoader (which in my eyes are a core part of Turbine) we decided to ask
for a vote on this.
The JPython support should not interfere with any existing stuff in
ScreenLoader. Only after failure to find a java screen in the normal way
does the code start looking for a JPython class. There is also an option in
the TR.properties to disable the JPython stuff (will probably be disabled by
default).
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.
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
