Home » Archived » MST » OCL text editor
|
| Re: OCL text editor [message #1354 is a reply to message #1346] |
Mon, 20 October 2008 12:28   |
Eclipse User |
|
|
|
Originally posted by: Kenn.Hussey.embarcadero.com
Ed,
I agree that such functionality would indeed be useful for validating
constraints that are defined in a standard metamodel. We plan to use the
Papyrus environment as a basis for diagram editors in MST... have you
proposed this as an inclusion in Papyrus and/or compared/contrasted it with
plans that team has regarding OCL?
Kenn
"Ed Willink" <ed@willink.me.uk> wrote in message
news:gdcfop$rt4$1@build.eclipse.org...
> Hi
>
> An OCL text editor is available now from the M2M QVT Declarative CVS.
>
> This editor uses IMP to provide the usual syntax coloring, folding, and
> completion proposals. MDT-OCL and LPG provide the CST and AST parsing. The
> (now QVT Declarative) Model Registry binds the external models to support
> semantic validation.
>
> At present it supports a complete OCL text file (a sequence of scoped
> constraints). It could be no doubt adapted to support individual
> constraints as a pop-up from a UML graphical editor.
>
> For MST, the utility would be support for validated bulk entry of the
> large number of OCL statements that occur in the better specifications and
> that should occur in all specifications.
>
> Regards
>
> Ed Willink
|
|
|
| Re: OCL text editor [message #1360 is a reply to message #1354] |
Wed, 22 October 2008 08:52 |
|
We are very interesting by this fucntionnality in Papyrus.
In the OCL project can we put ocl constraint on profile, and validate theses
rules when we apply profile on model?
It could be very interesting to connect directly your ocl editor in the
diagram in order to see colored syntax.
Best regards,
Patrick
"Kenn Hussey" <Kenn.Hussey@embarcadero.com> a
|
|
|
| Re: OCL text editor [message #1366 is a reply to message #1360] |
Mon, 27 October 2008 15:39 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Patrick,
The UML metamodel binding in the OCL component supports the definition
of constraints on Stereotypes in Profiles. As a convenience, the UML
environment allows evaluation of a constraint defined in the stereotype
context on an Element to which the stereotype is applied; it does this
by finding the associated stereotype instance and evaluating the
constraint on it, under the covers. The constraint must be well-formed
with respect to the stereotype properties, in particular using
navigation of metaclass extensions to access UML elements. There is no
syntactic short-cut for access to UML attributes in the stereotype context.
Does that answer your question?
Cheers,
Christian
Patrick Tessier wrote:
> We are very interesting by this fucntionnality in Papyrus.
>
> In the OCL project can we put ocl constraint on profile, and validate theses
> rules when we apply profile on model?
>
> It could be very interesting to connect directly your ocl editor in the
> diagram in order to see colored syntax.
>
> Best regards,
> Patrick
>
> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de news:
> gdhthh$cii$1@build.eclipse.org...
>> Ed,
>>
>> I agree that such functionality would indeed be useful for validating
>> constraints that are defined in a standard metamodel. We plan to use the
>> Papyrus environment as a basis for diagram editors in MST... have you
>> proposed this as an inclusion in Papyrus and/or compared/contrasted it
>> with plans that team has regarding OCL?
>>
>> Kenn
>>
>> "Ed Willink" <ed@willink.me.uk> wrote in message
>> news:gdcfop$rt4$1@build.eclipse.org...
>>> Hi
>>>
>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>
>>> This editor uses IMP to provide the usual syntax coloring, folding, and
>>> completion proposals. MDT-OCL and LPG provide the CST and AST parsing.
>>> The (now QVT Declarative) Model Registry binds the external models to
>>> support semantic validation.
>>>
>>> At present it supports a complete OCL text file (a sequence of scoped
>>> constraints). It could be no doubt adapted to support individual
>>> constraints as a pop-up from a UML graphical editor.
>>>
>>> For MST, the utility would be support for validated bulk entry of the
>>> large number of OCL statements that occur in the better specifications
>>> and that should occur in all specifications.
>>>
>>> Regards
>>>
>>> Ed Willink
>>
>
>
|
|
| |
| Re: OCL text editor [message #1378 is a reply to message #1372] |
Tue, 28 October 2008 13:37 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Patrick,
By "contact you," you do mean "contact the OCL newsgroup," right?
:-D
In the mean-time, you can see how OCL works with stereotypes in the
org.eclipse.ocl.uml.tests.ProfilesTest class.
cW
Patrick Tessier wrote:
> Yes,
>
> As soon as I have time, I will contact you in order to connect your editor
> into the property view in a first time and then directly on the diagram.
>
> Patrick,
>
>
> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de news:
> ge4nba$lv7$1@build.eclipse.org...
>> Hi, Patrick,
>>
>> The UML metamodel binding in the OCL component supports the definition of
>> constraints on Stereotypes in Profiles. As a convenience, the UML
>> environment allows evaluation of a constraint defined in the stereotype
>> context on an Element to which the stereotype is applied; it does this by
>> finding the associated stereotype instance and evaluating the constraint
>> on it, under the covers. The constraint must be well-formed with respect
>> to the stereotype properties, in particular using navigation of metaclass
>> extensions to access UML elements. There is no syntactic short-cut for
>> access to UML attributes in the stereotype context.
>>
>> Does that answer your question?
>>
>> Cheers,
>>
>> Christian
>>
>> Patrick Tessier wrote:
>>> We are very interesting by this fucntionnality in Papyrus.
>>>
>>> In the OCL project can we put ocl constraint on profile, and validate
>>> theses rules when we apply profile on model?
>>>
>>> It could be very interesting to connect directly your ocl editor in the
>>> diagram in order to see colored syntax.
>>>
>>> Best regards,
>>> Patrick
>>>
>>> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de
>>> news: gdhthh$cii$1@build.eclipse.org...
>>>> Ed,
>>>>
>>>> I agree that such functionality would indeed be useful for validating
>>>> constraints that are defined in a standard metamodel. We plan to use the
>>>> Papyrus environment as a basis for diagram editors in MST... have you
>>>> proposed this as an inclusion in Papyrus and/or compared/contrasted it
>>>> with plans that team has regarding OCL?
>>>>
>>>> Kenn
>>>>
>>>> "Ed Willink" <ed@willink.me.uk> wrote in message
>>>> news:gdcfop$rt4$1@build.eclipse.org...
>>>>> Hi
>>>>>
>>>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>>>
>>>>> This editor uses IMP to provide the usual syntax coloring, folding, and
>>>>> completion proposals. MDT-OCL and LPG provide the CST and AST parsing.
>>>>> The (now QVT Declarative) Model Registry binds the external models to
>>>>> support semantic validation.
>>>>>
>>>>> At present it supports a complete OCL text file (a sequence of scoped
>>>>> constraints). It could be no doubt adapted to support individual
>>>>> constraints as a pop-up from a UML graphical editor.
>>>>>
>>>>> For MST, the utility would be support for validated bulk entry of the
>>>>> large number of OCL statements that occur in the better specifications
>>>>> and that should occur in all specifications.
>>>>>
>>>>> Regards
>>>>>
>>>>> Ed Willink
>
|
|
| |
| Re: OCL text editor [message #1391 is a reply to message #1384] |
Wed, 29 October 2008 14:59 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Sébastien,
Naturally, I am interested in helping with that. The question is how
thinly I can spread myself ... :-)
Several features that are planned for OCL in this release should help
the integration, such as providing .edit and .editor plugins for the
metamodels and other work that Ed Willink is contributing. I think hes
has also expressed interest in contributing to MST, which probably
reaches into Papyrus as well.
Speaking for myself, working on the Papyrus side of any integration,
although I would undoubtedly enjoy it, is likely to be beyond my means.
We shall have to see in what little ways I can pitch in.
Cheers,
Christian
Sébastien Gérard wrote:
> Hi Christian,
>
> do you if some guys, may be you, of the OCL group could work on the
> integration of the OCL support (including the OCL editor) within Papyurs? Of
> course, Patrick can help doing that.
>
> --Séb
>
> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de news:
> ge74in$dfi$1@build.eclipse.org...
>> Hi, Patrick,
>>
>> By "contact you," you do mean "contact the OCL newsgroup," right?
>>
>> :-D
>>
>> In the mean-time, you can see how OCL works with stereotypes in the
>> org.eclipse.ocl.uml.tests.ProfilesTest class.
>>
>> cW
>>
>> Patrick Tessier wrote:
>>> Yes,
>>>
>>> As soon as I have time, I will contact you in order to connect your
>>> editor into the property view in a first time and then directly on the
>>> diagram.
>>>
>>> Patrick,
>>>
>>>
>>> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de
>>> news: ge4nba$lv7$1@build.eclipse.org...
>>>> Hi, Patrick,
>>>>
>>>> The UML metamodel binding in the OCL component supports the definition
>>>> of constraints on Stereotypes in Profiles. As a convenience, the UML
>>>> environment allows evaluation of a constraint defined in the stereotype
>>>> context on an Element to which the stereotype is applied; it does this
>>>> by finding the associated stereotype instance and evaluating the
>>>> constraint on it, under the covers. The constraint must be well-formed
>>>> with respect to the stereotype properties, in particular using
>>>> navigation of metaclass extensions to access UML elements. There is no
>>>> syntactic short-cut for access to UML attributes in the stereotype
>>>> context.
>>>>
>>>> Does that answer your question?
>>>>
>>>> Cheers,
>>>>
>>>> Christian
>>>>
>>>> Patrick Tessier wrote:
>>>>> We are very interesting by this fucntionnality in Papyrus.
>>>>>
>>>>> In the OCL project can we put ocl constraint on profile, and validate
>>>>> theses rules when we apply profile on model?
>>>>>
>>>>> It could be very interesting to connect directly your ocl editor in the
>>>>> diagram in order to see colored syntax.
>>>>>
>>>>> Best regards,
>>>>> Patrick
>>>>>
>>>>> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de
>>>>> news: gdhthh$cii$1@build.eclipse.org...
>>>>>> Ed,
>>>>>>
>>>>>> I agree that such functionality would indeed be useful for validating
>>>>>> constraints that are defined in a standard metamodel. We plan to use
>>>>>> the Papyrus environment as a basis for diagram editors in MST... have
>>>>>> you proposed this as an inclusion in Papyrus and/or
>>>>>> compared/contrasted it with plans that team has regarding OCL?
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>> "Ed Willink" <ed@willink.me.uk> wrote in message
>>>>>> news:gdcfop$rt4$1@build.eclipse.org...
>>>>>>> Hi
>>>>>>>
>>>>>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>>>>>
>>>>>>> This editor uses IMP to provide the usual syntax coloring, folding,
>>>>>>> and completion proposals. MDT-OCL and LPG provide the CST and AST
>>>>>>> parsing. The (now QVT Declarative) Model Registry binds the external
>>>>>>> models to support semantic validation.
>>>>>>>
>>>>>>> At present it supports a complete OCL text file (a sequence of scoped
>>>>>>> constraints). It could be no doubt adapted to support individual
>>>>>>> constraints as a pop-up from a UML graphical editor.
>>>>>>>
>>>>>>> For MST, the utility would be support for validated bulk entry of the
>>>>>>> large number of OCL statements that occur in the better
>>>>>>> specifications and that should occur in all specifications.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Ed Willink
>
>
|
|
| |
| Re: OCL text editor [message #1402 is a reply to message #1396] |
Thu, 30 October 2008 13:10 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Ed,
Don't worry; budgeting time is a fact of Eclipse committer life. I
wasn't trying to speak for you. :-)
I do have a plan item for this release to deliver the generated .edit
and .editor plug-ins, in a separately downloadable feature. An OCL text
editor is not in the plan.
cW
Ed Willink wrote:
> Christian W. Damus wrote:
>> Several features that are planned for OCL in this release should help
>> the integration, such as providing .edit and .editor plugins for the
>> metamodels and other work that Ed Willink is contributing. I think
>> hes has also expressed interest in contributing to MST, which probably
>> reaches into Papyrus as well.
>>
>> Speaking for myself, working on the Papyrus side of any integration,
>> although I would undoubtedly enjoy it, is likely to be beyond my
>> means. We shall have to see in what little ways I can pitch in.
>
> Hi.
>
> Sorry, I don't read newsgroups very often.
>
> I was firstly highlighting the availability of OCL editing support in
> case you wanted it. It seems you do. I can assist in making the editor
> invokable in an alternate fashion, but have limited time available to do
> more than that.
>
> Regards
>
> Ed Willink
|
|
| |
| Re: OCL text editor [message #563199 is a reply to message #1354] |
Wed, 22 October 2008 08:52 |
|
We are very interesting by this fucntionnality in Papyrus.
In the OCL project can we put ocl constraint on profile, and validate theses
rules when we apply profile on model?
It could be very interesting to connect directly your ocl editor in the
diagram in order to see colored syntax.
Best regards,
Patrick
"Kenn Hussey" <Kenn.Hussey@embarcadero.com> a
|
|
|
| Re: OCL text editor [message #563224 is a reply to message #1360] |
Mon, 27 October 2008 15:39 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Patrick,
The UML metamodel binding in the OCL component supports the definition
of constraints on Stereotypes in Profiles. As a convenience, the UML
environment allows evaluation of a constraint defined in the stereotype
context on an Element to which the stereotype is applied; it does this
by finding the associated stereotype instance and evaluating the
constraint on it, under the covers. The constraint must be well-formed
with respect to the stereotype properties, in particular using
navigation of metaclass extensions to access UML elements. There is no
syntactic short-cut for access to UML attributes in the stereotype context.
Does that answer your question?
Cheers,
Christian
Patrick Tessier wrote:
> We are very interesting by this fucntionnality in Papyrus.
>
> In the OCL project can we put ocl constraint on profile, and validate theses
> rules when we apply profile on model?
>
> It could be very interesting to connect directly your ocl editor in the
> diagram in order to see colored syntax.
>
> Best regards,
> Patrick
>
> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de news:
> gdhthh$cii$1@build.eclipse.org...
>> Ed,
>>
>> I agree that such functionality would indeed be useful for validating
>> constraints that are defined in a standard metamodel. We plan to use the
>> Papyrus environment as a basis for diagram editors in MST... have you
>> proposed this as an inclusion in Papyrus and/or compared/contrasted it
>> with plans that team has regarding OCL?
>>
>> Kenn
>>
>> "Ed Willink" <ed@willink.me.uk> wrote in message
>> news:gdcfop$rt4$1@build.eclipse.org...
>>> Hi
>>>
>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>
>>> This editor uses IMP to provide the usual syntax coloring, folding, and
>>> completion proposals. MDT-OCL and LPG provide the CST and AST parsing.
>>> The (now QVT Declarative) Model Registry binds the external models to
>>> support semantic validation.
>>>
>>> At present it supports a complete OCL text file (a sequence of scoped
>>> constraints). It could be no doubt adapted to support individual
>>> constraints as a pop-up from a UML graphical editor.
>>>
>>> For MST, the utility would be support for validated bulk entry of the
>>> large number of OCL statements that occur in the better specifications
>>> and that should occur in all specifications.
>>>
>>> Regards
>>>
>>> Ed Willink
>>
>
>
|
|
| |
| Re: OCL text editor [message #563275 is a reply to message #1372] |
Tue, 28 October 2008 13:37 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Patrick,
By "contact you," you do mean "contact the OCL newsgroup," right?
:-D
In the mean-time, you can see how OCL works with stereotypes in the
org.eclipse.ocl.uml.tests.ProfilesTest class.
cW
Patrick Tessier wrote:
> Yes,
>
> As soon as I have time, I will contact you in order to connect your editor
> into the property view in a first time and then directly on the diagram.
>
> Patrick,
>
>
> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de news:
> ge4nba$lv7$1@build.eclipse.org...
>> Hi, Patrick,
>>
>> The UML metamodel binding in the OCL component supports the definition of
>> constraints on Stereotypes in Profiles. As a convenience, the UML
>> environment allows evaluation of a constraint defined in the stereotype
>> context on an Element to which the stereotype is applied; it does this by
>> finding the associated stereotype instance and evaluating the constraint
>> on it, under the covers. The constraint must be well-formed with respect
>> to the stereotype properties, in particular using navigation of metaclass
>> extensions to access UML elements. There is no syntactic short-cut for
>> access to UML attributes in the stereotype context.
>>
>> Does that answer your question?
>>
>> Cheers,
>>
>> Christian
>>
>> Patrick Tessier wrote:
>>> We are very interesting by this fucntionnality in Papyrus.
>>>
>>> In the OCL project can we put ocl constraint on profile, and validate
>>> theses rules when we apply profile on model?
>>>
>>> It could be very interesting to connect directly your ocl editor in the
>>> diagram in order to see colored syntax.
>>>
>>> Best regards,
>>> Patrick
>>>
>>> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de
>>> news: gdhthh$cii$1@build.eclipse.org...
>>>> Ed,
>>>>
>>>> I agree that such functionality would indeed be useful for validating
>>>> constraints that are defined in a standard metamodel. We plan to use the
>>>> Papyrus environment as a basis for diagram editors in MST... have you
>>>> proposed this as an inclusion in Papyrus and/or compared/contrasted it
>>>> with plans that team has regarding OCL?
>>>>
>>>> Kenn
>>>>
>>>> "Ed Willink" <ed@willink.me.uk> wrote in message
>>>> news:gdcfop$rt4$1@build.eclipse.org...
>>>>> Hi
>>>>>
>>>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>>>
>>>>> This editor uses IMP to provide the usual syntax coloring, folding, and
>>>>> completion proposals. MDT-OCL and LPG provide the CST and AST parsing.
>>>>> The (now QVT Declarative) Model Registry binds the external models to
>>>>> support semantic validation.
>>>>>
>>>>> At present it supports a complete OCL text file (a sequence of scoped
>>>>> constraints). It could be no doubt adapted to support individual
>>>>> constraints as a pop-up from a UML graphical editor.
>>>>>
>>>>> For MST, the utility would be support for validated bulk entry of the
>>>>> large number of OCL statements that occur in the better specifications
>>>>> and that should occur in all specifications.
>>>>>
>>>>> Regards
>>>>>
>>>>> Ed Willink
>
|
|
| |
| Re: OCL text editor [message #563326 is a reply to message #1384] |
Wed, 29 October 2008 14:59 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Sébastien,
Naturally, I am interested in helping with that. The question is how
thinly I can spread myself ... :-)
Several features that are planned for OCL in this release should help
the integration, such as providing .edit and .editor plugins for the
metamodels and other work that Ed Willink is contributing. I think hes
has also expressed interest in contributing to MST, which probably
reaches into Papyrus as well.
Speaking for myself, working on the Papyrus side of any integration,
although I would undoubtedly enjoy it, is likely to be beyond my means.
We shall have to see in what little ways I can pitch in.
Cheers,
Christian
Sébastien Gérard wrote:
> Hi Christian,
>
> do you if some guys, may be you, of the OCL group could work on the
> integration of the OCL support (including the OCL editor) within Papyurs? Of
> course, Patrick can help doing that.
>
> --Séb
>
> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de news:
> ge74in$dfi$1@build.eclipse.org...
>> Hi, Patrick,
>>
>> By "contact you," you do mean "contact the OCL newsgroup," right?
>>
>> :-D
>>
>> In the mean-time, you can see how OCL works with stereotypes in the
>> org.eclipse.ocl.uml.tests.ProfilesTest class.
>>
>> cW
>>
>> Patrick Tessier wrote:
>>> Yes,
>>>
>>> As soon as I have time, I will contact you in order to connect your
>>> editor into the property view in a first time and then directly on the
>>> diagram.
>>>
>>> Patrick,
>>>
>>>
>>> "Christian W. Damus" <cdamus@zeligsoft.com> a écrit dans le message de
>>> news: ge4nba$lv7$1@build.eclipse.org...
>>>> Hi, Patrick,
>>>>
>>>> The UML metamodel binding in the OCL component supports the definition
>>>> of constraints on Stereotypes in Profiles. As a convenience, the UML
>>>> environment allows evaluation of a constraint defined in the stereotype
>>>> context on an Element to which the stereotype is applied; it does this
>>>> by finding the associated stereotype instance and evaluating the
>>>> constraint on it, under the covers. The constraint must be well-formed
>>>> with respect to the stereotype properties, in particular using
>>>> navigation of metaclass extensions to access UML elements. There is no
>>>> syntactic short-cut for access to UML attributes in the stereotype
>>>> context.
>>>>
>>>> Does that answer your question?
>>>>
>>>> Cheers,
>>>>
>>>> Christian
>>>>
>>>> Patrick Tessier wrote:
>>>>> We are very interesting by this fucntionnality in Papyrus.
>>>>>
>>>>> In the OCL project can we put ocl constraint on profile, and validate
>>>>> theses rules when we apply profile on model?
>>>>>
>>>>> It could be very interesting to connect directly your ocl editor in the
>>>>> diagram in order to see colored syntax.
>>>>>
>>>>> Best regards,
>>>>> Patrick
>>>>>
>>>>> "Kenn Hussey" <Kenn.Hussey@embarcadero.com> a écrit dans le message de
>>>>> news: gdhthh$cii$1@build.eclipse.org...
>>>>>> Ed,
>>>>>>
>>>>>> I agree that such functionality would indeed be useful for validating
>>>>>> constraints that are defined in a standard metamodel. We plan to use
>>>>>> the Papyrus environment as a basis for diagram editors in MST... have
>>>>>> you proposed this as an inclusion in Papyrus and/or
>>>>>> compared/contrasted it with plans that team has regarding OCL?
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>> "Ed Willink" <ed@willink.me.uk> wrote in message
>>>>>> news:gdcfop$rt4$1@build.eclipse.org...
>>>>>>> Hi
>>>>>>>
>>>>>>> An OCL text editor is available now from the M2M QVT Declarative CVS.
>>>>>>>
>>>>>>> This editor uses IMP to provide the usual syntax coloring, folding,
>>>>>>> and completion proposals. MDT-OCL and LPG provide the CST and AST
>>>>>>> parsing. The (now QVT Declarative) Model Registry binds the external
>>>>>>> models to support semantic validation.
>>>>>>>
>>>>>>> At present it supports a complete OCL text file (a sequence of scoped
>>>>>>> constraints). It could be no doubt adapted to support individual
>>>>>>> constraints as a pop-up from a UML graphical editor.
>>>>>>>
>>>>>>> For MST, the utility would be support for validated bulk entry of the
>>>>>>> large number of OCL statements that occur in the better
>>>>>>> specifications and that should occur in all specifications.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Ed Willink
>
>
|
|
| |
| Re: OCL text editor [message #563371 is a reply to message #1396] |
Thu, 30 October 2008 13:10 |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Ed,
Don't worry; budgeting time is a fact of Eclipse committer life. I
wasn't trying to speak for you. :-)
I do have a plan item for this release to deliver the generated .edit
and .editor plug-ins, in a separately downloadable feature. An OCL text
editor is not in the plan.
cW
Ed Willink wrote:
> Christian W. Damus wrote:
>> Several features that are planned for OCL in this release should help
>> the integration, such as providing .edit and .editor plugins for the
>> metamodels and other work that Ed Willink is contributing. I think
>> hes has also expressed interest in contributing to MST, which probably
>> reaches into Papyrus as well.
>>
>> Speaking for myself, working on the Papyrus side of any integration,
>> although I would undoubtedly enjoy it, is likely to be beyond my
>> means. We shall have to see in what little ways I can pitch in.
>
> Hi.
>
> Sorry, I don't read newsgroups very often.
>
> I was firstly highlighting the availability of OCL editing support in
> case you wanted it. It seems you do. I can assist in making the editor
> invokable in an alternate fashion, but have limited time available to do
> more than that.
>
> Regards
>
> Ed Willink
|
|
|
Goto Forum:
Current Time: Sat Nov 09 00:41:50 GMT 2024
Powered by FUDForum. Page generated in 0.04428 seconds |
] 
Search
Help
Register
Login
Home
