Hey,
While considering the moving of the components currently in the DataValues
git repository [0], it occurred to me the current components are not all
that nicely dividing the code. All of these components, with the exception
of DataTypes and ValueView, bundle whole inheritance hierarchies. A classic
package design mistake that leads to various problems. My current plan here
is to have a new component that holds the interfaces, exceptions and
trivial implementations for all of these components (again, except DTs and
VV). Many of the components currently dependent on one of the already
existing ones, would then just need this one, which is much more
abstract/stable, tackling most of the pains of the current component design.
Two questions:
* Any suggestions on what to call this new component to hold the interfaces?
* Any alternate approaches that improve upon the current situation?
There is some urgency to this, as the git repo split should happen soon, to
alleviate the pains currently caused by not having independently deployable
and released versions.
[0] DataValues, ValueParsers, ValueValidators, DataTypes, etc
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--