[EMAIL PROTECTED] wrote:
>
> Based on the fact that the Turbine project contains a PythonAssembler I
> guess that people see how valuable Python can be in terms of rapid
> development. Given this what do people think about extending Velocity to
> deal with Python objects being placed into the context directly?
Eh... :)
> I have added support to ASTIdentifier by adding a PythonExecutor that will
> try to resolve reference from anything that subclasses PyObject. This is a
> pretty clean fit I think and doesn't require much code. I was about to
> extend ASTMethod to handle the method case, but here is the thing. I don't
> want to create a solid dependency on Jython in the Velocity codebase. What
> I would like from people are ideas about how to extend the AbstractExecutor
> notion to be more like plugable directive and then extend this notion to
> the AST{Identifier, Method, Reference?}
If you can do it in the AST, why not just make a conventionally
introspectable wrapper class for the python stuff...? Then you can drop
that right into the context, and no one is the wiser....
> Then these could walk a runtime defined list of Executors and preform the
> right handling without needing to link velocity with the handlers codebase.
> What do people think? Is this just a custom body of work or should we look
> at adding something like this to the main codebase?
>
> Thanks
> Ben
If you can get away with it at app level, I think you should leave it
there.... My gut is that we don't want to start doing things like this,
especially if you can get away with a simple wrapper.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
You have a genius for suggesting things I've come a cropper with!
