Re: IntelliJ + WebObjects 5.4
Re: IntelliJ + WebObjects 5.4
- Subject: Re: IntelliJ + WebObjects 5.4
- From: Mike Schrag <email@hidden>
- Date: Tue, 18 Dec 2007 08:43:22 -0500
Ideally, if all the Eclipse specific code in WOLips could be
separated out of the "core" WOLips (if it isn't already) then it
would provide the base for an IDEA plugin to build on.
I think this would be really REALLY hard to do ... Entity Modeler is
separated out as its own application, but almost every bit of code
uses Eclipse API's ... EOModel loading is mostly independent of
Eclipse API's, but even many models use Eclipse model API's
(IDocument, etc). Component editing and binding validation is full of
references to IProjects, IJavaProjects, ITypes, IResources, etc.
Basically, other than Entity Modeler, the vast majority of WOLips code
is talking to the Java type system to manipulate your Java classes, or
to the Eclipse document system to manipulate documents. I think
trying to abstract this would be essentially defining a complete set
of peer interfaces to all of the Eclipse API's, which would basically
be total insanity. The alternative would be to try to actually
implement the Eclipse interfaces on top of IDEA, but you're talking a
HUGE task.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden