Hi Thomas! On 12/20/2007 11:15 AM Thomas Nunninger wrote:
> there is an issue (#010913) about complex datatypes for persistent > object. I don't know in deep about the disussion - but I just have an > idea: I'm right now working on this issue, btw. > Wouldn't it be good to have a dedicated Datatype component? This > component could cover things like validation, conversion (to an > internal representation and between different representations e.g. > degree Celsius and Farenheit), and provide datatype specific operators, > e.g. calculating a distance between two location-related datatypes. > This component could be used in several places: > > - input validation > > - business objects > > - persistent object > What do you think about such a component? I like the general idea of havinng conversions for UserInput, too. Therefore I'm not against such a component at all. I still see some problems of how such a component can be useful on it's own, except for TieIns for UserInput and PersistentObject. However, if we want to support conversions into complex objects for UserInput, too, it would make some sense to create a dedicated component for it to avoid code duplication. Regards, Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
