You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Jörn Kottmann <ko...@gmail.com> on 2011/03/30 11:29:20 UTC
Removal of Cas Editor Project support
Hello everyone,
the Cas Editor started with a special project type called
"Cas Editor Project" to mange annotation projects, this special
project is through recent work which went into the 2.3.1 release now
obsolete,
since 2.3.1 it is possible to open a CAS file from any project type.
The removal would remove a bunch of code from the Cas Editor.
The would be the following:
- Cas Editor Project model
- Corpus Explorer
- Analysis Engine and Cas Consumer run support (replaced for 2.3.2 by
the uimaj-ep-launcher plugin)
The removal will make the Cas Editor code base simpler and also remove
the dependency on
the eclipse ide plugin, which eases the integration of the Cas Editor
into RCP applications.
Any opinions?
Jörn
Re: Removal of Cas Editor Project support
Posted by Tommaso Teofili <to...@gmail.com>.
+1 from me.
Tommaso
2011/4/27 Jörn Kottmann <ko...@gmail.com>
> Any opinons? Otherwise I will go ahead and remove the
> Cas Editor project support and implemented the proposed
> backward compatibility.
>
> Jörn
>
>
> On 4/11/11 5:15 PM, Jörn Kottmann wrote:
>
>> On 3/31/11 10:35 PM, Marshall Schor wrote:
>>
>>> Could we do something to make its removal give the right guidance to let
>>> people
>>> who are "used to" the other method continue to use the CAS editor?
>>>
>>> I think we need some way to gracefully migrate people :-)
>>>
>>
>> Now looked a little deeper into this issue and suggest the following
>> migration.
>>
>> When the new Cas Editor 2.3.2 is started up the first time,
>> it does the following to migrate a project:
>>
>> 1. Reads the dotCorpus file and sets the type system location for the
>> project
>> 2. Copies the dotCorpus to the new default styling file location
>>
>> After these two steps a user will be able to open any .xcas or .xmi file
>> inside
>> the migrated project with the configured styling. The functionality to run
>> an
>> AE will be removed from the Cas Editor and we will instruct our users to
>> use
>> the new eclipse AE launch support instead.
>>
>> What that be a graceful migration?
>>
>> Jörn
>>
>>
>>
>>
>
Re: Removal of Cas Editor Project support
Posted by Marshall Schor <ms...@schor.com>.
On 4/28/2011 7:47 AM, Jörn Kottmann wrote:
> On 4/28/11 1:27 PM, Jörn Kottmann wrote:
>> When exactly would you show this dialog?
>
> The dialog is now shown once the first time the user opens
> the Annotation Editor.
>
This sounds right to me. The users is obviously thinking / focussed on the
Annotation Editor at that point, and is more likely to be able to read and
understand what you're showing, at that time.
-Marshall
> Jörn
>
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
On 4/28/11 1:27 PM, Jörn Kottmann wrote:
> When exactly would you show this dialog?
The dialog is now shown once the first time the user opens
the Annotation Editor.
Jörn
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
What do you think about an eclipse intro page instead?
As far as I know, it can be shown when the plugin was updated,
or when it is installed the first time, the removal could be described
there.
Jörn
On 4/28/11 1:27 PM, Jörn Kottmann wrote:
> When exactly would you show this dialog?
>
> The migration is currently done when the bundle is activated,
> which could also be during the start up of eclipse.
>
> Jörn
>
> On 4/28/11 1:17 PM, Jörn Kottmann wrote:
>> On 4/28/11 1:08 PM, Marshall Schor wrote:
>>> +1 if in addition, you popped up a message during the 1 - time
>>> migration saying
>>> what was happening, giving the user a just-in-time "education" about
>>> the change.
>>>
>>> It would probably be good to make this a modal message so the user
>>> would need to
>>> push an OK button. I suppose you could have a cancel option button,
>>> too, in
>>> case the user didn't want to do the migration, and wanted to
>>> uninstall the 2.3.2
>>> version and go back to the previous one (though, I doubt that path
>>> would be
>>> chosen - but then again, perhaps there are more issues we don't
>>> realize, yet).
>>>
>>
>> Sounds good, I will add such a dialog. I do not see the need for a
>> cancel button,
>> since the existing things are not changed, even after doing the
>> migration it
>> will be possible to just go back to the old version.
>>
>> All we change is setting a type system property on the project and
>> copy the dotCorpus file to
>> the new default location, the old dotCorpus file remains in place.
>>
>> Jörn
>
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
When exactly would you show this dialog?
The migration is currently done when the bundle is activated,
which could also be during the start up of eclipse.
Jörn
On 4/28/11 1:17 PM, Jörn Kottmann wrote:
> On 4/28/11 1:08 PM, Marshall Schor wrote:
>> +1 if in addition, you popped up a message during the 1 - time
>> migration saying
>> what was happening, giving the user a just-in-time "education" about
>> the change.
>>
>> It would probably be good to make this a modal message so the user
>> would need to
>> push an OK button. I suppose you could have a cancel option button,
>> too, in
>> case the user didn't want to do the migration, and wanted to
>> uninstall the 2.3.2
>> version and go back to the previous one (though, I doubt that path
>> would be
>> chosen - but then again, perhaps there are more issues we don't
>> realize, yet).
>>
>
> Sounds good, I will add such a dialog. I do not see the need for a
> cancel button,
> since the existing things are not changed, even after doing the
> migration it
> will be possible to just go back to the old version.
>
> All we change is setting a type system property on the project and
> copy the dotCorpus file to
> the new default location, the old dotCorpus file remains in place.
>
> Jörn
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
On 4/28/11 1:08 PM, Marshall Schor wrote:
> +1 if in addition, you popped up a message during the 1 - time migration saying
> what was happening, giving the user a just-in-time "education" about the change.
>
> It would probably be good to make this a modal message so the user would need to
> push an OK button. I suppose you could have a cancel option button, too, in
> case the user didn't want to do the migration, and wanted to uninstall the 2.3.2
> version and go back to the previous one (though, I doubt that path would be
> chosen - but then again, perhaps there are more issues we don't realize, yet).
>
Sounds good, I will add such a dialog. I do not see the need for a
cancel button,
since the existing things are not changed, even after doing the migration it
will be possible to just go back to the old version.
All we change is setting a type system property on the project and copy
the dotCorpus file to
the new default location, the old dotCorpus file remains in place.
Jörn
Re: Removal of Cas Editor Project support
Posted by Marshall Schor <ms...@schor.com>.
+1 if in addition, you popped up a message during the 1 - time migration saying
what was happening, giving the user a just-in-time "education" about the change.
It would probably be good to make this a modal message so the user would need to
push an OK button. I suppose you could have a cancel option button, too, in
case the user didn't want to do the migration, and wanted to uninstall the 2.3.2
version and go back to the previous one (though, I doubt that path would be
chosen - but then again, perhaps there are more issues we don't realize, yet).
-Marshall
On 4/27/2011 4:26 AM, Jörn Kottmann wrote:
> Any opinons? Otherwise I will go ahead and remove the
> Cas Editor project support and implemented the proposed
> backward compatibility.
>
> Jörn
>
> On 4/11/11 5:15 PM, Jörn Kottmann wrote:
>> On 3/31/11 10:35 PM, Marshall Schor wrote:
>>> Could we do something to make its removal give the right guidance to let people
>>> who are "used to" the other method continue to use the CAS editor?
>>>
>>> I think we need some way to gracefully migrate people :-)
>>
>> Now looked a little deeper into this issue and suggest the following migration.
>>
>> When the new Cas Editor 2.3.2 is started up the first time,
>> it does the following to migrate a project:
>>
>> 1. Reads the dotCorpus file and sets the type system location for the project
>> 2. Copies the dotCorpus to the new default styling file location
>>
>> After these two steps a user will be able to open any .xcas or .xmi file inside
>> the migrated project with the configured styling. The functionality to run an
>> AE will be removed from the Cas Editor and we will instruct our users to use
>> the new eclipse AE launch support instead.
>>
>> What that be a graceful migration?
>>
>> Jörn
>>
>>
>>
>
>
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
Any opinons? Otherwise I will go ahead and remove the
Cas Editor project support and implemented the proposed
backward compatibility.
Jörn
On 4/11/11 5:15 PM, Jörn Kottmann wrote:
> On 3/31/11 10:35 PM, Marshall Schor wrote:
>> Could we do something to make its removal give the right guidance to
>> let people
>> who are "used to" the other method continue to use the CAS editor?
>>
>> I think we need some way to gracefully migrate people :-)
>
> Now looked a little deeper into this issue and suggest the following
> migration.
>
> When the new Cas Editor 2.3.2 is started up the first time,
> it does the following to migrate a project:
>
> 1. Reads the dotCorpus file and sets the type system location for the
> project
> 2. Copies the dotCorpus to the new default styling file location
>
> After these two steps a user will be able to open any .xcas or .xmi
> file inside
> the migrated project with the configured styling. The functionality to
> run an
> AE will be removed from the Cas Editor and we will instruct our users
> to use
> the new eclipse AE launch support instead.
>
> What that be a graceful migration?
>
> Jörn
>
>
>
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
On 3/31/11 10:35 PM, Marshall Schor wrote:
> Could we do something to make its removal give the right guidance to let people
> who are "used to" the other method continue to use the CAS editor?
>
> I think we need some way to gracefully migrate people :-)
Now looked a little deeper into this issue and suggest the following
migration.
When the new Cas Editor 2.3.2 is started up the first time,
it does the following to migrate a project:
1. Reads the dotCorpus file and sets the type system location for the
project
2. Copies the dotCorpus to the new default styling file location
After these two steps a user will be able to open any .xcas or .xmi file
inside
the migrated project with the configured styling. The functionality to
run an
AE will be removed from the Cas Editor and we will instruct our users to use
the new eclipse AE launch support instead.
What that be a graceful migration?
Jörn
Re: Removal of Cas Editor Project support
Posted by Jörn Kottmann <ko...@gmail.com>.
On 3/31/11 10:35 PM, Marshall Schor wrote:
> Could we do something to make its removal give the right guidance to let people
> who are "used to" the other method continue to use the CAS editor?
>
> I think we need some way to gracefully migrate people :-)
After the Cas Editor project support is removed the Cas Editor will not
be able
to locate the type system for these projects anymore. To avoid that we
could add some
migration code which knows how to find the type system for Cas Editor
projects.
We could also do the migration step wise, first deprecate the Cas Editor
project
and then remove it later, that will give our users more time.
Jörn
Re: Removal of Cas Editor Project support
Posted by Tommaso Teofili <to...@gmail.com>.
2011/3/31 Marshall Schor <ms...@schor.com>
> Could we do something to make its removal give the right guidance to let
> people
> who are "used to" the other method continue to use the CAS editor?
>
> I think we need some way to gracefully migrate people :-)
>
>
I agree,
Tommaso
Re: Removal of Cas Editor Project support
Posted by Marshall Schor <ms...@schor.com>.
Could we do something to make its removal give the right guidance to let people
who are "used to" the other method continue to use the CAS editor?
I think we need some way to gracefully migrate people :-)
-M
On 3/30/2011 5:29 AM, Jörn Kottmann wrote:
> Hello everyone,
>
> the Cas Editor started with a special project type called
> "Cas Editor Project" to mange annotation projects, this special
> project is through recent work which went into the 2.3.1 release now obsolete,
> since 2.3.1 it is possible to open a CAS file from any project type.
>
> The removal would remove a bunch of code from the Cas Editor.
> The would be the following:
> - Cas Editor Project model
> - Corpus Explorer
> - Analysis Engine and Cas Consumer run support (replaced for 2.3.2 by the
> uimaj-ep-launcher plugin)
>
> The removal will make the Cas Editor code base simpler and also remove the
> dependency on
> the eclipse ide plugin, which eases the integration of the Cas Editor into RCP
> applications.
>
> Any opinions?
>
> Jörn
>
>