Vladimir Sekissov wrote:
>
> To continue discussion about extension languages in Turbine.
>
> I wrote BRL service, layout, page, screen, navigation classes for the
> same reasons (announce was posted weak ago). Instead Python it use
> Scheme and Kawa as interpreter.
>
> Now I'm working on support for coding actions in Scheme to get hole
> system for RAD.
>
> My question. What about to develop conventions for coding action paths
> for extension languages and additional methods for ActionLoader?
>
> The goal is to have uniform extension interface similar to one
> we already have in Turbine template system.
+1, go for it Vladimir. It would be really nice to have the option to
extend Turbine using languages other than Java. I would very much
prefer that this is disabled by default, and I really think that Java is
an excellent language for long-term web development, but I see the value
in being able to experiment with other languages. However, I don't want
to have any of these other languages installed unless I am actually
playing with them.
Leon, ditto for your stuff.
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
