I'd like to organize the package layout of CForm classes in order to cleanly separate API classes from implementations classes.
The changes you propose all sound pretty sensible. Anything that makes it easier to extend CForms gets my vote!
A nesting is currently required for convertors, since they are attached to a particular datatype. To remove this need, we may use a naming convention, prefixing the convertor and format name by the corresponding datatype component name, i.e. "long-formatting", "date-formatting", etc.
Not so sure about this. Wouldn't it be better to have a datatype attribute on the convertor? Something like
<convertor type="formatting" datatype="date"/>
for example?
Vil.
--
__
o| _. / \|o._ _ _ ._ _ ._ _ _|_
\/ ||\/(_|| (|/||| |(/_(_)| |(/_o| |(/_ |_
/ \__
http://website.lineone.net/~vilya
