cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re: [jira] Commented: (CAY-762) ERDiagram for Object Entities in Cayenne Modeler
Date Thu, 03 Dec 2009 14:03:13 GMT
I agree with the premise, but I had bad experience with other ORM  
tools years ago that would save the layout together with the project,  
and then a single unintended mouse move results in making the project  
"dirty" and creates an underlying SCM change. IMO that was a  
distraction and created constant commit noise.

So essentially managing a pretty layout is a parallel task to the main  
task of creating a model, and I don't want it to become a distraction.  
So maybe we can make it a project property (persist-layout: true|false  
(default))? If true, it will store the XML together with the project,  
if false, it will store it in local preferences?


On Dec 3, 2009, at 3:47 PM, Andrey Razumovsky wrote:
> 2009/12/3 Andrus Adamchik <>
>> On Dec 3, 2009, at 3:31 PM, Andrus Adamchik wrote:
>> * saving graphs info as <domain_name>.graph.xml (and restoring).  
>> Note that
>>>> this file will not be used in classic Cayenne runtime
>> I think this can be tied to preferences and saved in ~/.cayenne/.  
>> Saving it
>> in the project tree has SCM implications.
> I thought of that..
> Lets take your example. You've got an enormous project, so no layout  
> can
> place entities without intersections. You spend half a day to  
> organize it
> well.. Then what? How can other members of the team see your  
> changes? It is
> even better when graph is in SCM - it is not a big file, and allows  
> everyone
> to see it. Graph file is XML, so SVN should merge it correctly. The  
> only
> thing you need is exclude it from packaged version of your project  
> (if you
> want).
> At last resort you can add graph files to something like svn:ignore

View raw message