Hi all
Just thought I'd let you in on our newest Turbine experiment - JPython
integration. Why would we want to do such a thing you may be wondering.
Well, if you've done as much actual web app development with Turbine as we
have, you may well see the benefits this brings to the dev process:
* RAD - add/change (Python) actions and screens without recompiling!!! No
lost sessions/logins/db connections because of reloads, no waiting forever
for the first page after a reload (especially with our XSL stuff that is not
cached initially), none of the problems that rapid edit/recompile cycles
present to multiple coders. Can you say: "edit, save, refresh"?!
* The JPython interpreter does the work at runtime. Of course, before
deployment, JPython can be used to compile the Python actions/screens into
Java class files, so that there's no performance penalty. In fact, JPython
can "compile" to Java source code if needed!
* Easier for non-hardcore-Java developers. Now a developer with relatively
basic Python skills can add actions and screens - just provide them with
properly designed data objects that encapsulate the business rules/logic,
and off they go! What's more, they can immediately see what they're doing
(right or wrong!).
We're still in the baby stages of development on this stuff, but it sure
would add a wonderful OPTION to Turbine for developers.
Please let us know what you think.
Frank (and Leon)
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
