+1.
Two notes:
- UI capabilities went off since Helios [1].
- I'll probably bet for providing access to both consoles:
1. If an xtext console is not available by default, perhaps
nobody will note that it exists.
2. If the old-one is not available, somebody could complain
before realizing that there is away to make it visible
Perhaps, a Menu-Sebmenu items approach could fit here.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=299344
Best Regards,
Adolfo.
El 03/03/2011 19:17, Ed Willink escribió:
Hi
Guys
It looks as if http://dev.eclipse.org/ipzilla/show_bug.cgi?id=4866
may come through in time.
But, the interpreter was outside the area that I identified as
available for me to modify without team review, so any patch will
need review. This incurs delays, and I'm not entirely sure that
the OCL Console should migrate in 3.1 when it is not really till
3.2 that we want to encourage transition to the Xtext parser and
associated pivot model. I therefore propose to create a new
o.e.o.examples.xtext.console plugin for the replacement
functionality ensuring that old and new have distinct namespaces
and so limit impact to download size.
We should ensure that we have UI capabilities control that enables
either or both of the old "OCL Console" and the new "OCL Xtext
Console" to be switched off. I suggest deferring a decision as to
which to enable by default until just before M7.
Regards
Ed
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
