I'll add another one I forgot about! :-) Possibly merge the ObjEntity and DbEntity in the left-hand navigation pane. I'm not exactly sure what it would look like, but I know EOModeler and WOLips have a combined navigation pane:
http://cdn-ak.f.st-hatena.com/images/fotolife/m/mig50/20060731/20060731010550.png On Tue, Jan 5, 2016 at 7:58 AM, Michael Gentry <mgen...@masslight.net> wrote: > Hi, > > I'd like to start a conversation about future improvements for CM. > > My current wish list: > > - Java Entities > - Class Level: > - Ability to add extra imports. > - Ability to add interfaces implemented. > - Ability to add JavaDoc. > - Ability to add annotations. > - Attribute Level: > - Ability to add JavaDoc. > - Ability to add annotations. > - Relationship Level: > - Ability to add JavaDoc. > - Ability to add annotations. > - Ability to drill-down through relationships.* > - DB Entities > - Table Level: > - Ability to add comments (for DBs that support comments). > - Column Level: > - Ability to add comments (for DBs that support comments). > - Relationship Level: > - Ability to add comments (for DBs that support comments). > - Ability to drill-down through relationships.* > > * Llike EOModeler, in the left-hand navigation pane. You could keep > expanding the relationship tree to expose other entities/relationships. > > > We've also previously chatted a bit about if we even want to keep > maintaining the current form of CM. If we did want to overhaul the > implementation, what route should we go? > > - JFX (Seems like Oracle's ugly stepchild and I question their commitment > to it.) > - SWT > - Eclipse Plugin (The WOLips route.) > - Electron (Used by Atom and Visual Studio Code, among others.) > > > Your thoughts greatly appreciated! > > > Thanks, > > mrg > >
