On Dec 3, 2009, at 4:22 PM, Mike Kienenberger wrote:
It doesn't make any sense to have a project-specific piece of
information
stored in preferences.
And still we do that a lot already. There's a bunch of per-screen
Modeler preferences stored per project (and not in user visible XML
files). If you move to another machine, you lose it.
I think the difference here is in a mental view of the graph layout
task. To you and Andrey it is a part of the ORM modeling work. To me
it is not. It is a *local* user preference. Something a single
developer would tweak to his or her liking, kind of like arranging
icons on a desktop.
Let me give you a few examples of why sharing a layout might be bad:
* 2 developers on the project want to have different layouts, because
they work with different parts of the model. So they group entities
differently.
* A single developer rearranges the layout multiple times during the
day as he goes from one task to another.
* 1 developer uses a 13" notebook, another - 31" screen. Developer 1
has no choice, but to optimize the layout for his screen.
Andrus
