Hi, all,
I’ve raised bug 495325 for the top-level preference page and posted Gerrit 74441 with my proposed solution. Have at it. Perhaps discussion about this page, itself, can move into the bugzilla now.
When this work is eventually merged, I can raise a new enhancement request for integration of the Xtext editor preferences into it. I have an idea how the Clear button for dialog settings can be consolidated into one (using the API provided by Xtext), but it needs some more thought.
On 2 June, 2016 at 12:05:14, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Right. The top-level menu item invokes the code
generator for textual UML-RT.
We should probably get rid of that and unify the textual and
graphical code-gen menus as well.
I'm not sure yet how to go about it, as the textual plugins
don't depend on Papyrus at all.
Understood regarding the two menu items. And there's
also this top menu which could be replaced by the generate
button:
Maybe we could use the Papyrus-RT icon for
the button; though, it's not square:
Here's an example pic of the Papyrus
icon in action:
CMake
--------
Now with support for Mac build & debug, I'm going to
update the setup & usage guides (soon.) These guides
will give us a good idea of what's required in the generated
project. Maybe it's preferable to dispense with options and instead
create the generated project with the required properties
preconfigured.
Verified build/debug thus far:
WIndows: Visual Studio 2013 & 2015.
Eclipse IDE via Cygwin, MSYS
Mac: Yosetime
Linux: Ubuntu 12.04
I’m not sure that this would be the best approach for those
menu items. I think I would prefer an approach similar to the build
tools, i.e., a button that would do the incremental code generation
by default and a sub-button that would do a regenerate - an
approach similar to make / make clean, but for codegen,
Assuming CMake makes its way into the trunk, there are a
couple of parameters that could be handled via the preferences
page.
And perhaps the model context menu could be reduced to a
single item where regeneration (overwrite?) is handled as a
preference.
<Mail Attachment.jpeg>
>>> Christian Damus <give.a.damus@xxxxxxxxx> 6/2/2016 9:33 AM
>>>
Yes, that’s quite annoying, actually, because those preferences and
their pages are all implemented in the Xtext run-time. I’m not sure
how feasible it would be to unify that. It could be reason enough
to leave the Xtext editor as a top-level preference node
(ugh).
Hi,
I guess it must be
considered that the current "Umlrt" section already have the same
kind of "Clear" button that is proposed:
<Mail
Attachment>
So to avoid confusion,
some alignment will definitively be needed.
/Peter Cigéhn
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|