I'd rather we have a different navigation solution than an infinitely
expanding tree. Cayenne model is different from EOModel in that it
separates DB and Obj views. So there are more connections and more
navigation path's: (ObjEntity -> DbEntity, ObjAtribute -> DbAttribute,
etc.) I think think requires a different solution. Probably some
clickable elements on the right-hand side editor forms.
Andrus
On Mar 16, 2008, at 3:11 PM, Michael Gentry wrote:
How about being able to drill through relationships in the view on the
left, just like EOModeler?
On Sun, Mar 16, 2008 at 5:53 AM, Andrus Adamchik <[EMAIL PROTECTED]
> wrote:
I created a page with the list of tasks for the SoC project called
"cayenne-modeler-improvements":
http://cwiki.apache.org/CAY/summer-of-code-2008.html
Note that I did not include anything that would require student to
make architectural decisions or change classes in the "map"
package. I
hope this way I can mentor it effectively and we can actually place
the code on Cayenne trunk at the end of the program.
Andrus
On Mar 10, 2008, at 12:23 PM, Andrus Adamchik wrote:
http://wiki.apache.org/general/SummerOfCode2008
Summer of Code is here. I think I may sign up as a mentor for some
specific tasks within the scope of Cayenne project. If somebody has
project idea and/or also wants to be a mentor, please speak up.
Thanks,
Andrus
