On 29/03/2016 8:36pm, Michael Gentry wrote: > The concern I'd have with the MySQL Workbench approach is there'd be a lot > more scrolling involved. The model I have is already fairly large and I > don't like scrolling around it looking for things. If I had to expand > attributes (and relationships) and select the property to edit, I think the > amount of scrolling would become quite hectic. On my 27" iMac with CM 3.1 > taking up the full vertical height of the screen, the tree view is about > 1/2 shown. At least one ObjEntity has enough attributes to more than fill > the vertical height, too. If all of those properties start getting > expanded in the tree view, it would become quite chaotic, I think.
Let's talk about this point specifically. In MySQL Workbench there is exactly the same problem... very very long lists. One of my db servers has 60 databases and each database has about 120 tables. Each table might average 15 columns. But of course you never have the whole thing expanded at once. Typically you'd use it just like you would the three panel approach with a similar number of clicks. The tree only becomes unhelpful if you expand lots of things at once and maybe an accordion approach (where expanding one thing collapses everything else) could work. The only reason I really like this approach though is how much more room is available for the editor, rather than cramming it into the bottom 20% of the frame. Everything else apart from the editor is just navigation. Ari -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
