> > Are we using torque to generate the peer/map classes for
> > Turbine itself?
>
> Nope.
Ok, roughly what would it take to move there?
We are extending Turbine's map builder with our own, and
I'm trying to figure out the best way to do it and reuse
most of the code.
> There is only one map building for the internal turbine
> tables.
Ok. This is TurbineMapBuilder, right? It looks like it would
be enough to replace the code in doBuild() with calls to
doBuild() for each of the generated map builders, right?
> We should probably move toward using torque to generate
> the all the internal turbine goodies as well. I'm playing
> with some templates for flux that generate the user class
> for a webapp so that the flux can deal with user types
> that implement the User interface.
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
