At 02:04 PM 11/17/2002 +0100, Holger Hoffstätte wrote:
>Craig Miskell wrote:
> > I'd like to see an eclipse modeller plugin, with class generation tied
> > directly into an eclipse project. But that's just me, and I don't have
>
>nope :-)
>One of my first thoughts after I saw the MVCification of the Modeler.
>
> > the resources to do it just yet. (Cant' justify it during work time, and
> > my machine at home struggles along just running eclipse, let alone running
> > an embedded eclipse for debugging a plugin :-( )
This whole IDE issue made me totally upset just a few weeks ago. On the one
hand we needed to evolve it and make it more powerful, on the other hand
continued development in Swing felt like a dead end. Finally I figured we
have no choice but continue with Swing. So I started the MVC effort for the
new screens and dialogs. In short, it is a bit messy now.
As for switching to Eclipse, history shows that there must be a person
dedicated exclusively to the plugin development for this to happen. This is
how it happened in WOProject/WOLips (thanks to Ulrich), same thing is true
with Tapestry. Eclipse GUI development looks like a big piece to bite when
also working on the core Cayenne code :-(.
I think we can't abandon Swing Modeler until someone expresses the desire
to lead an Eclipse project and moves at least to a point when you can do
complete model editing. As for Holger's concerns about quickly changing
versions of Cayenne and Eclipse, I suspect this is always going to happen
in one form or another.
Andrus
This archive was generated by hypermail 2.0.0 : Sun Nov 17 2002 - 18:25:32 EST