cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gmail <tgiacc...@gmail.com>
Subject Re: CM Thoughts
Date Thu, 07 Jan 2016 15:02:26 GMT
One problem with moving to an eclipse platform/plugin is that it adds another barrier to adoption
by devs who don't use Eclipse. We have a lot of IntelliJ IDEA users here.

Tony Giaccone

> On Jan 5, 2016, at 7:58 AM, Michael Gentry <mgentry@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

Mime
View raw message