> > data.getParameters().setProperties(user, transformations)
>
> -1 because this is setProperties specific.
I feel that it is setProperties specific. If it was done in
a transformation class then we would be duplicating all
the property code. Wouldn't we?
I think the setProperties(object, transformations) makes
it completely optional: if you to manually grab all the
goods yourself then getXXX() will return your data
unscathed. The transformations would specifically be
applied within the setProperties(object, transformations)
method.
What I'm thinking about primarily is automatic form
processing, maybe something that can be used in
intake. I will think about it more, but I don't
think implementing tranformXXX() in each of the
transformation classes would be very nice. I think
the type that it transforms, and the transform
method would be enough.
I used the getClass() because I thought we could use
that in setProperty as the class type is used to
retrieve the correct type, so I figured making the
transformation return the class type it operates
on would make it easy to integrate into setProperty().
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
