Michael Tanenblatt | 1 Jun 2011 14:25

Re: Cas Editor split for easy RCP app integration

I think t his would be an excellent thing to do

On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:

> Hi all,
> 
> I am proposing that we split the Cas Editor into two parts,
> one core part and one part which deals with eclipse ide integration.
> 
> The core part will be designed to be reusable by RCP applications which
> need to perform CAS viewing/editing. An example for such an application
> is an annotation tool which is connected to document repository.
> 
> The ide part will ensure that the Cas Editor is integrated into the eclipse
> ide as it is now.
> 
> As part of the split I would like to work with the community to define an API which
> can be used to integrate and extend the Cas Editor in various ways.
> 
> Any opinions?
> 
> Jörn

Richard Eckart de Castilho | 1 Jun 2011 15:48
Picon
Favicon

Re: Cas Editor split for easy RCP app integration

Sounds good to me. That way the Eclipse integration could also take care of resolving imports via the Java
Classpath if a XMI resides within a Java project.

Cheers,

Richard

Am 01.06.2011 um 14:25 schrieb Michael Tanenblatt:

> I think t his would be an excellent thing to do
> 
> On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:
> 
>> Hi all,
>> 
>> I am proposing that we split the Cas Editor into two parts,
>> one core part and one part which deals with eclipse ide integration.
>> 
>> The core part will be designed to be reusable by RCP applications which
>> need to perform CAS viewing/editing. An example for such an application
>> is an annotation tool which is connected to document repository.
>> 
>> The ide part will ensure that the Cas Editor is integrated into the eclipse
>> ide as it is now.
>> 
>> As part of the split I would like to work with the community to define an API which
>> can be used to integrate and extend the Cas Editor in various ways.
>> 
>> Any opinions?
>> 
(Continue reading)

Tommaso Teofili | 1 Jun 2011 17:59
Picon
Gravatar

Re: Cas Editor split for easy RCP app integration

+1, really a nice idea Jörn , that may help other existing platforms (like
IntelliJ) developing a specialized CAS Editor (or create new UI tool for
UIMA).
Tommaso

2011/6/1 Michael Tanenblatt <slothrop@...>

> I think t his would be an excellent thing to do
>
> On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:
>
> > Hi all,
> >
> > I am proposing that we split the Cas Editor into two parts,
> > one core part and one part which deals with eclipse ide integration.
> >
> > The core part will be designed to be reusable by RCP applications which
> > need to perform CAS viewing/editing. An example for such an application
> > is an annotation tool which is connected to document repository.
> >
> > The ide part will ensure that the Cas Editor is integrated into the
> eclipse
> > ide as it is now.
> >
> > As part of the split I would like to work with the community to define an
> API which
> > can be used to integrate and extend the Cas Editor in various ways.
> >
> > Any opinions?
> >
(Continue reading)

Jörn Kottmann | 2 Jun 2011 08:37
Picon

Re: Cas Editor split for easy RCP app integration

On 6/1/11 5:59 PM, Tommaso Teofili wrote:
> +1, really a nice idea Jörn , that may help other existing platforms (like
> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
> UIMA).
  I cannot see how that helps the development of Cas Editors for other
non-eclipse platforms?

The core part will still depend on eclipse and contains the Annotation
Editor together with the views.

Jörn

Tommaso Teofili | 2 Jun 2011 09:49
Picon
Gravatar

Re: Cas Editor split for easy RCP app integration

2011/6/2 Jörn Kottmann <kottmann@...>

> On 6/1/11 5:59 PM, Tommaso Teofili wrote:
>
>> +1, really a nice idea Jörn , that may help other existing platforms (like
>> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
>> UIMA).
>>
>  I cannot see how that helps the development of Cas Editors for other
> non-eclipse platforms?
>
> The core part will still depend on eclipse and contains the Annotation
> Editor together with the views.
>

from what you said in the first email I understood the core wouldn't have
contained Eclipse dependencies, however I still think this refactoring is a
good thing.
Tommaso
Jörn Kottmann | 2 Jun 2011 11:27
Picon

Re: Cas Editor split for easy RCP app integration

On 6/2/11 9:49 AM, Tommaso Teofili wrote:
> 2011/6/2 Jörn Kottmann<kottmann@...>
>
>> On 6/1/11 5:59 PM, Tommaso Teofili wrote:
>>
>>> +1, really a nice idea Jörn , that may help other existing platforms (like
>>> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
>>> UIMA).
>>>
>>   I cannot see how that helps the development of Cas Editors for other
>> non-eclipse platforms?
>>
>> The core part will still depend on eclipse and contains the Annotation
>> Editor together with the views.
>>
> from what you said in the first email I understood the core wouldn't have
> contained Eclipse dependencies, however I still think this refactoring is a
> good thing.

No, that is a misunderstanding, almost any code inside the Cas Editor 
depends
on eclipse APIs.

Jörn


Gmane