GLORP & Magritte both uses a lot of similar techniques. It's not descriptors only. Accessors and Conditions are other examples. So, why not clean up everything metamodel-related from GLORP, and utilise Magritte functionality instead? I thing it gives boost to both projects: Magritte will be forced to evolve and include techniques like collection tracking. GLORP, first of all, will lost part of it's complexity. And, secondly, it will be possible to use, say, Chain or Pluggable accessors. And there are several sinergy effects expected. First of all, we avoid double-working when you try to use Magritte and GLORP in one project. Yes, there are some package fir this, but it built "on top" of both systems, and provide only very simple and straitforward possibilities. Next, it becomes easier to implement "list all objects links to this very object", which is definetly in a lot of relation-databases-based applications. Finaly, as far as Magritte is often used (for generating forms, for example), it will be funny "just add few code and force my code to work with Postgresql". Really, I think, lot of people described different pieces of proposed system in their own projects. I personally did. _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/listinfo/esug-list