Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
MIME-Version: 1.0
In-Reply-To: <9D6B1FFF-10A8-41B8-A4B5-7B798C8911C6@karlmenn.is>
References: 
 <CAA-upzqaFTBJd5jcPyj38nUkTAsZZwSfkQsQ+UE-+jzAdXkjcQ@mail.gmail.com>
 <1B4FDD19-EAC4-446A-8BA5-4558AFADA2EE@gmail.com>
 <CAA-upzpUJV8okaVCPtDhhtQ+qcWnbyFi3_zSE7vSdpPL++DVfA@mail.gmail.com>
 <9D6B1FFF-10A8-41B8-A4B5-7B798C8911C6@karlmenn.is>
From: Michael Gentry <mgentry@masslight.net>
Date: Mon, 11 Jan 2016 10:27:44 -0500
Message-ID: 
 <CAA-upzrHJcBCcCOXMaQTv26Myuv6=wOJnsrL=E-92-jQyfvq3g@mail.gmail.com>
Subject: Re: CM Thoughts
To: Cayenne Developers <dev@cayenne.apache.org>
Content-Type: multipart/alternative; boundary=001a1140d7443c155d05291095e6

--001a1140d7443c155d05291095e6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was wondering if SWT made it easy/easier to do that.

On Mon, Jan 11, 2016 at 10:23 AM, Hugi Thordarson <hugi@karlmenn.is> wrote:

> EOF=E2=80=99s Entity Modeler is also provided as a standalone application=
. That
> seems like a winning situation, where the modeler can be run either withi=
n
> the Eclipse environment or as an app.
>
> - hugi
>
>
>
> > On 11. jan. 2016, at 13:50, Michael Gentry <mgentry@masslight.net>
> wrote:
> >
> > Well, using SWT doesn't mean it has to be an Eclipse plugin -- it can b=
e
> > like Apache Directory Studio, which is a standalone application.
> >
> >
> > On Thu, Jan 7, 2016 at 10:02 AM, Gmail <tgiaccone@gmail.com> wrote:
> >
> >> 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/relationship=
s.
> >>>
> >>>
> >>> 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
> >>
>
>

--001a1140d7443c155d05291095e6--