Re: [mdt-ocl.dev] OclInEcore editor behaviour

[ed@xxxxxxxxxxxxxxxxxx]

Hi Alex

Lower priority: absolutely. Not looked at how; do you know?

Xtext nature; I'm not 100% sure whether I like it; with some doubt caused
by major Xtext error diagnosis fixes in M7. With the nature, some bad
files can lock the machine up on rebuild. Without the nature, old errors
can get stuck until a clean.

Glad you like them. I'm surprised you haven't found more annoyances. I've
got quite a few fixes in store; now down to just one error, through lack
of template specialisation, in RoyalAndLoyal.

The OCLinEcore syntax is up for discussion; it's currently a pragmatic
migration from Emfatic to OMG-like.

    Ed

> Hi Ed,
>
> I am playing with the new xtext-based OCL editors. They are cool, great
> work!
>
> I found a small inconvenience that would probably annoy those who don't
> use
> OCL editors. When installing all features of OCL with all examples, etc.
> (e.g. M7a) - the default editor for .ecore files would be OclInEcore
> editor.
> Moreover, if a project containing an ecore doesn't have an XText nature, a
> dialog will be opened prompting the user to add the nature. I don't think
> it
> should be the default behaviour. IMO by default the priority of the
> OclInEcore editor should be less than the priority of the standard sample
> ecore model editor.
>
> Do you agree?
>
> Regards,
> - Alex.
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
>