Hi Michael,
that’s a valuable suggestion and in fact there is already an open bugzilla for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=352332). It has not yet been pushed or supported by additional requests so it dropped out of the initial planning round.
But I see the value in this, especially because copying of code is always a bad idea (as also Rhett wrote). What I could imagine is providing some more service functionality for creating diagrams, but would rather vote for not offering the complete wizard since this is intended only for the creation of test diagrams and is probably not what a user would expect from a real tool wizard. If there are specific parts of the wizard coding that are of general interest they could of course be extracted and also offered as services.
Do you have more concrete wishes or requirements for the functionality to offer here? Best would be to comment directly in the bug.
Thanks,
Michael
From: graphiti-dev-bounces@xxxxxxxxxxx [mailto:graphiti-dev-bounces@xxxxxxxxxxx] On Behalf Of Keppler Michael (ETAS/EPS2)
Sent: Montag, 8. August 2011 12:27
To: Discuss development topics on Graphiti
Subject: Re: [graphiti-dev] Graphiti planning for Juno
Hi Michael,
I’d like to suggest one item for the “ease of use” topic: There should be some facility for easily creating diagrams (i.e. diagram files), which is not part of the commons.example plugin. If you start using Graphiti, you currently have two choices:
· Include the commons.example plugin, then you can easily create diagrams using the given wizard, but you get other dependencies and stuff that you don’t want.
· Don’t include commons.example and copy-paste a huge amount of code from the commons.example wizard, maybe not even understanding what exactly you are doing there.
And if you decide to make that wizard available in the runtime, then it should not create a hard coded subdirectory “src/diagrams”. J
Ciao, Michael
Von: graphiti-dev-bounces@xxxxxxxxxxx [mailto:graphiti-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wenz, Michael
Gesendet: Montag, 25. Juli 2011 16:41
An: Discuss development topics on Graphiti
Betreff: [graphiti-dev] Graphiti planning for Juno
Hi all,
I’ve created a very first (draft) version of the Graphiti project plan for the Eclipse Juno release, it can be found here: http://www.eclipse.org/projects/project-plan.php?projectid=modeling.gmp.graphiti
The links in the ‘Release Milestones’ section mostly direct to empty Bugzilla collections since the topics are not yet assigned to specific milestones. So currently, all planned topics can be found under the link behind the final release (0.9.0 for now). Only the link to M1 is filled with the stuff we already did since the release of Indigo.
Here are the direct links:
- What we already did for Juno M1:
https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;field0-0-0=flagtypes.name;status_whiteboard=M1;type0-0-0=equals;value0-0-0=juno%2B;component=Graphiti;classification=Modeling;product=GMP
- What is planned for Juno
https://bugs.eclipse.org/bugs/buglist.cgi?negate1=1;type1-0-0=anywords;field0-0-0=flagtypes.name;classification=Modeling;query_format=advanced;value1-0-0=M1%20M2%20M3%20M4%20M5%20M6%20M7%20RC1%20RC2%20RC3%20RC4;type0-0-0=equals;value0-0-0=juno%2B;component=Graphiti;field1-0-0=status_whiteboard;product=GMP
Let me know if you have comments on this, want to see additional things or have other questions.
Michael
+----------------------------------------------------------------------+
| ETAS Mail Security - http://intranet.etasgroup.com/encryption |
+----------------------------------------------------------------------+
| - The message was not encrypted and not digitally signed |
+----------------------------------------------------------------------+
