Hi Dirk,
I did not make those Tcl procs to fix a broken data model. The design is to make it easier to use the CR. I wanted to have a design wherein the UI package is separate from the data operations. As I have experienced most CMS has the same functions and operations, but their UI varies a lot. Of course the theory must be more tested. And based from my initial first stint, it seems to be ok. But I need to change it, most are naming convention, merge or split some procs.
CR seems to work for me ok. Since the name (cr_items.name, normally used for url) and (cr_revisions.description) description are already there. And you can look it up by package_id in cr_folders.package_id. The CR maybe a heavy weight, especially if you do not need versioning. Although I have used CR even if I did not need versioning. The UI does not expose versioning and I only have one version in the CR.
Hope this is still related with the thread.
