Good morning, yesterday during the footbal match I listened to a very nice talk: "How to Design a Good API and Why it Matters"[1]. I recommend the first half, while the last part is Java specific and about problems a PHP programmer does not have.
During the talk I realized, that the thing I'm currently writing[2] becomes way to complicate and that I should search for parts that could be extracted out of it. I found, that PersistentObject could do some part and that it would help, if I could read, manipulate and write ezcPersistentObjectDefinition structures easily. By now we only have a definition writer in DbSchema, but it only takes schemes as input, does not write relations and can not be customized (yet). eZ Component: PersistentObject, Requirements ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Introduction ============ This document describes requirements for manipulating and writing PersistentObject Definition structures (po-structs). Description ----------- - All properties of a po-structs that can be set, must also be available for manipulation. - A po-struct can be validated. - A valid instance of an ezcPersistentObjectDefinition class can be written to disc. (Note: This could be implemented with the visitor pattern.) [1] http://www.youtube.com/watch?v=aAb7hSCtvGw [2] http://www.koch.ro/blog/index.php?/archives/75-Changing-Database-Schemas.html -- Thomas Koch, Software Developer http://www.koch.ro Young Media Concepts GmbH Sonnenstr. 4 CH-8280 Kreuzlingen Switzerland Tel +41 (0)71 / 508 24 86 Fax +41 (0)71 / 560 53 89 Mobile +49 (0)170 / 753 89 16 Web www.ymc.ch -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
