Home » Modeling » GMF (Graphical Modeling Framework) » General Documentation Issue
| General Documentation Issue [message #145525] |
Tue, 07 August 2007 07:46  |
Eclipse User |
|
|
|
hello,
Intro:
I'm 'working' with GMF for over 4 month now (full time), but still
lacking an overview of the documentation. I think one problem is that
there's no GMF book, but I doubt it that one book could address all the
diversity of GMF.
Existing documentation:
The documentation of GMF is split into GMF-Tools (wiki) and the
GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
runtime-articles in the wiki. A lot of concepts / features are inplicit
explained in tutorials or are explained due to an implementation in an
open-source project which costs extra time to find the interesting place
in a complex set-up. Another good information source is of course the
EclipseCon and Jax presentations, publications in EclipseMag etc. each
addressing a bunch of topics. Last but not least GEF books address lots
of concepts of the GMF runtime.
Conclusion:
My impression is that _the documentation isn't as bad as it looks like_,
but it takes a lot of time finding the right place. The reason for this
is because there's no aggregation (or index in terms of where to look
for a specific problem) of it. For me this results in mind-numbing tasks
like printing out the docs e.g. presentations, writing the treated
topics on top of it and later on when I actually need it trying to
remember in which resource I've read it.
Suggestion(abstract):
In addition to invest time to write further documentation a better time/
benefit rate would be achieved with a link collection of the existing
documentation.
Suggestion(concrete):
I guess a structured wiki-page like the index and/or the content of a
book would be a very good idea.
This could look like:
(+link for every item)
EditPolicies:
Developer Guide to Diagram Runtime Framework P.10f
GMF Best Practices P.8-10
IBMs Redbook P.110ff
Decorators(Shape):
Extending your DSM by ... P22-26
Creating your own DSM using GMF P.28
Decorating Model:
GMF Best Practices P.19-24
Diagram Partitioning:
(Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
Draw2D:
IBMs Redbook ...
Online Tutorials ...
Of course this would need a better structure, but the idea should be clear.
Final words:
I assume the time creating this would be amortized soon in relation to
the time the gmf-professionals spend in answering the recurring
newsgroup questions.
What do you think? Wouldn't this be a cheap, easy and feasable improvement?
-stefan
|
|
|
| Re: General Documentation Issue [message #145540 is a reply to message #145525] |
Tue, 07 August 2007 08:22  |
| Eclipse User |
|
|
|
Good idea, thanks! I've created a skeleton wiki index page based on your
content below, and linked it from the main documentation wiki page.
http://wiki.eclipse.org/GMF_Documentation_Index
I'll add more content later, but would encourage you and others to
contribute to this wiki as well. For some reason, people seem reluctant to
create/edit our wiki pages (to Ward's dismay, no doubt).
Thanks again,
Rich
On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
<kuhn@oio.de> wrote:
> hello,
>
> Intro:
> I'm 'working' with GMF for over 4 month now (full time), but still
> lacking an overview of the documentation. I think one problem is that
> there's no GMF book, but I doubt it that one book could address all the
> diversity of GMF.
>
> Existing documentation:
> The documentation of GMF is split into GMF-Tools (wiki) and the
> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
> runtime-articles in the wiki. A lot of concepts / features are inplicit
> explained in tutorials or are explained due to an implementation in an
> open-source project which costs extra time to find the interesting place
> in a complex set-up. Another good information source is of course the
> EclipseCon and Jax presentations, publications in EclipseMag etc. each
> addressing a bunch of topics. Last but not least GEF books address lots
> of concepts of the GMF runtime.
>
> Conclusion:
> My impression is that _the documentation isn't as bad as it looks like_,
> but it takes a lot of time finding the right place. The reason for this
> is because there's no aggregation (or index in terms of where to look
> for a specific problem) of it. For me this results in mind-numbing tasks
> like printing out the docs e.g. presentations, writing the treated
> topics on top of it and later on when I actually need it trying to
> remember in which resource I've read it.
>
> Suggestion(abstract):
> In addition to invest time to write further documentation a better time/
> benefit rate would be achieved with a link collection of the existing
> documentation.
>
> Suggestion(concrete):
> I guess a structured wiki-page like the index and/or the content of a
> book would be a very good idea.
>
>
> This could look like:
> (+link for every item)
>
> EditPolicies:
> Developer Guide to Diagram Runtime Framework P.10f
> GMF Best Practices P.8-10
> IBMs Redbook P.110ff
>
> Decorators(Shape):
> Extending your DSM by ... P22-26
> Creating your own DSM using GMF P.28
>
> Decorating Model:
> GMF Best Practices P.19-24
>
> Diagram Partitioning:
> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>
> Draw2D:
> IBMs Redbook ...
> Online Tutorials ...
>
> Of course this would need a better structure, but the idea should be clear.
>
>
> Final words:
> I assume the time creating this would be amortized soon in relation to
> the time the gmf-professionals spend in answering the recurring
> newsgroup questions.
>
> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>
> -stefan
>
>
>
>
|
|
|
| Re: General Documentation Issue [message #145620 is a reply to message #145540] |
Tue, 07 August 2007 10:28 |
| Eclipse User |
|
|
|
thanks ;)
Well I tried to edit this page and made a suggestion how we could format
the links. But right now I get logged out of the wiki every 2 clicks
(firefox & IE) making it really hard to add something :(
-stefan
Richard Gronback schrieb:
> Good idea, thanks! I've created a skeleton wiki index page based on your
> content below, and linked it from the main documentation wiki page.
>
> http://wiki.eclipse.org/GMF_Documentation_Index
>
> I'll add more content later, but would encourage you and others to
> contribute to this wiki as well. For some reason, people seem reluctant to
> create/edit our wiki pages (to Ward's dismay, no doubt).
>
> Thanks again,
> Rich
>
>
> On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
> <kuhn@oio.de> wrote:
>
>> hello,
>>
>> Intro:
>> I'm 'working' with GMF for over 4 month now (full time), but still
>> lacking an overview of the documentation. I think one problem is that
>> there's no GMF book, but I doubt it that one book could address all the
>> diversity of GMF.
>>
>> Existing documentation:
>> The documentation of GMF is split into GMF-Tools (wiki) and the
>> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
>> runtime-articles in the wiki. A lot of concepts / features are inplicit
>> explained in tutorials or are explained due to an implementation in an
>> open-source project which costs extra time to find the interesting place
>> in a complex set-up. Another good information source is of course the
>> EclipseCon and Jax presentations, publications in EclipseMag etc. each
>> addressing a bunch of topics. Last but not least GEF books address lots
>> of concepts of the GMF runtime.
>>
>> Conclusion:
>> My impression is that _the documentation isn't as bad as it looks like_,
>> but it takes a lot of time finding the right place. The reason for this
>> is because there's no aggregation (or index in terms of where to look
>> for a specific problem) of it. For me this results in mind-numbing tasks
>> like printing out the docs e.g. presentations, writing the treated
>> topics on top of it and later on when I actually need it trying to
>> remember in which resource I've read it.
>>
>> Suggestion(abstract):
>> In addition to invest time to write further documentation a better time/
>> benefit rate would be achieved with a link collection of the existing
>> documentation.
>>
>> Suggestion(concrete):
>> I guess a structured wiki-page like the index and/or the content of a
>> book would be a very good idea.
>>
>>
>> This could look like:
>> (+link for every item)
>>
>> EditPolicies:
>> Developer Guide to Diagram Runtime Framework P.10f
>> GMF Best Practices P.8-10
>> IBMs Redbook P.110ff
>>
>> Decorators(Shape):
>> Extending your DSM by ... P22-26
>> Creating your own DSM using GMF P.28
>>
>> Decorating Model:
>> GMF Best Practices P.19-24
>>
>> Diagram Partitioning:
>> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>>
>> Draw2D:
>> IBMs Redbook ...
>> Online Tutorials ...
>>
>> Of course this would need a better structure, but the idea should be clear.
>>
>>
>> Final words:
>> I assume the time creating this would be amortized soon in relation to
>> the time the gmf-professionals spend in answering the recurring
>> newsgroup questions.
>>
>> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>>
>> -stefan
>>
>>
>>
>>
>
|
|
|
| Re: General Documentation Issue [message #145828 is a reply to message #145540] |
Wed, 08 August 2007 08:57 |
| Eclipse User |
|
|
|
well, I added a template which we could use to put the index in a good
looking format and to stay flexible for view-changes.
Take a look
http://wiki.eclipse.org/Template:GMF_Index_ExternalResource
-stefan
Richard Gronback schrieb:
> Good idea, thanks! I've created a skeleton wiki index page based on your
> content below, and linked it from the main documentation wiki page.
>
> http://wiki.eclipse.org/GMF_Documentation_Index
>
> I'll add more content later, but would encourage you and others to
> contribute to this wiki as well. For some reason, people seem reluctant to
> create/edit our wiki pages (to Ward's dismay, no doubt).
>
> Thanks again,
> Rich
>
>
> On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
> <kuhn@oio.de> wrote:
>
>> hello,
>>
>> Intro:
>> I'm 'working' with GMF for over 4 month now (full time), but still
>> lacking an overview of the documentation. I think one problem is that
>> there's no GMF book, but I doubt it that one book could address all the
>> diversity of GMF.
>>
>> Existing documentation:
>> The documentation of GMF is split into GMF-Tools (wiki) and the
>> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
>> runtime-articles in the wiki. A lot of concepts / features are inplicit
>> explained in tutorials or are explained due to an implementation in an
>> open-source project which costs extra time to find the interesting place
>> in a complex set-up. Another good information source is of course the
>> EclipseCon and Jax presentations, publications in EclipseMag etc. each
>> addressing a bunch of topics. Last but not least GEF books address lots
>> of concepts of the GMF runtime.
>>
>> Conclusion:
>> My impression is that _the documentation isn't as bad as it looks like_,
>> but it takes a lot of time finding the right place. The reason for this
>> is because there's no aggregation (or index in terms of where to look
>> for a specific problem) of it. For me this results in mind-numbing tasks
>> like printing out the docs e.g. presentations, writing the treated
>> topics on top of it and later on when I actually need it trying to
>> remember in which resource I've read it.
>>
>> Suggestion(abstract):
>> In addition to invest time to write further documentation a better time/
>> benefit rate would be achieved with a link collection of the existing
>> documentation.
>>
>> Suggestion(concrete):
>> I guess a structured wiki-page like the index and/or the content of a
>> book would be a very good idea.
>>
>>
>> This could look like:
>> (+link for every item)
>>
>> EditPolicies:
>> Developer Guide to Diagram Runtime Framework P.10f
>> GMF Best Practices P.8-10
>> IBMs Redbook P.110ff
>>
>> Decorators(Shape):
>> Extending your DSM by ... P22-26
>> Creating your own DSM using GMF P.28
>>
>> Decorating Model:
>> GMF Best Practices P.19-24
>>
>> Diagram Partitioning:
>> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>>
>> Draw2D:
>> IBMs Redbook ...
>> Online Tutorials ...
>>
>> Of course this would need a better structure, but the idea should be clear.
>>
>>
>> Final words:
>> I assume the time creating this would be amortized soon in relation to
>> the time the gmf-professionals spend in answering the recurring
>> newsgroup questions.
>>
>> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>>
>> -stefan
>>
>>
>>
>>
>
|
|
|
| Re: General Documentation Issue [message #146143 is a reply to message #145540] |
Fri, 10 August 2007 08:46 |
| Eclipse User |
|
|
|
allright, I indexed 2 presentations to make a beginning for our index
(http://wiki.eclipse.org/GMF_Documentation_Index).
Added following stuff:
Best Practices
Extending your DSM by leveraging the GMF Runtime
Developer Guide to Diagram Runtime Framework
check out if we could start like this. As soon as I realize I'm not the
only person who tries to improve this index I'll add 3-4 presentations more.
-stefan
Richard Gronback schrieb:
> Good idea, thanks! I've created a skeleton wiki index page based on your
> content below, and linked it from the main documentation wiki page.
>
> http://wiki.eclipse.org/GMF_Documentation_Index
>
> I'll add more content later, but would encourage you and others to
> contribute to this wiki as well. For some reason, people seem reluctant to
> create/edit our wiki pages (to Ward's dismay, no doubt).
>
> Thanks again,
> Rich
>
>
> On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
> <kuhn@oio.de> wrote:
>
>> hello,
>>
>> Intro:
>> I'm 'working' with GMF for over 4 month now (full time), but still
>> lacking an overview of the documentation. I think one problem is that
>> there's no GMF book, but I doubt it that one book could address all the
>> diversity of GMF.
>>
>> Existing documentation:
>> The documentation of GMF is split into GMF-Tools (wiki) and the
>> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
>> runtime-articles in the wiki. A lot of concepts / features are inplicit
>> explained in tutorials or are explained due to an implementation in an
>> open-source project which costs extra time to find the interesting place
>> in a complex set-up. Another good information source is of course the
>> EclipseCon and Jax presentations, publications in EclipseMag etc. each
>> addressing a bunch of topics. Last but not least GEF books address lots
>> of concepts of the GMF runtime.
>>
>> Conclusion:
>> My impression is that _the documentation isn't as bad as it looks like_,
>> but it takes a lot of time finding the right place. The reason for this
>> is because there's no aggregation (or index in terms of where to look
>> for a specific problem) of it. For me this results in mind-numbing tasks
>> like printing out the docs e.g. presentations, writing the treated
>> topics on top of it and later on when I actually need it trying to
>> remember in which resource I've read it.
>>
>> Suggestion(abstract):
>> In addition to invest time to write further documentation a better time/
>> benefit rate would be achieved with a link collection of the existing
>> documentation.
>>
>> Suggestion(concrete):
>> I guess a structured wiki-page like the index and/or the content of a
>> book would be a very good idea.
>>
>>
>> This could look like:
>> (+link for every item)
>>
>> EditPolicies:
>> Developer Guide to Diagram Runtime Framework P.10f
>> GMF Best Practices P.8-10
>> IBMs Redbook P.110ff
>>
>> Decorators(Shape):
>> Extending your DSM by ... P22-26
>> Creating your own DSM using GMF P.28
>>
>> Decorating Model:
>> GMF Best Practices P.19-24
>>
>> Diagram Partitioning:
>> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>>
>> Draw2D:
>> IBMs Redbook ...
>> Online Tutorials ...
>>
>> Of course this would need a better structure, but the idea should be clear.
>>
>>
>> Final words:
>> I assume the time creating this would be amortized soon in relation to
>> the time the gmf-professionals spend in answering the recurring
>> newsgroup questions.
>>
>> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>>
>> -stefan
>>
>>
>>
>>
>
|
|
|
| Re: General Documentation Issue [message #146179 is a reply to message #146143] |
Fri, 10 August 2007 09:35 |
| Eclipse User |
|
|
|
Wow, that's quite a bit. At this rate, it seems the index will certainly be
larger than our accumulated documentation ;)
I'll try to add some today (at least my name as author of the tutorial).
Thanks,
Rich
On 8/10/07 8:46 AM, in article f9hmmg$98t$1@build.eclipse.org, "SKuhn"
<kuhn@oio.de> wrote:
> allright, I indexed 2 presentations to make a beginning for our index
> (http://wiki.eclipse.org/GMF_Documentation_Index).
>
> Added following stuff:
> Best Practices
> Extending your DSM by leveraging the GMF Runtime
> Developer Guide to Diagram Runtime Framework
>
> check out if we could start like this. As soon as I realize I'm not the
> only person who tries to improve this index I'll add 3-4 presentations more.
>
> -stefan
>
>
>
> Richard Gronback schrieb:
>> Good idea, thanks! I've created a skeleton wiki index page based on your
>> content below, and linked it from the main documentation wiki page.
>>
>> http://wiki.eclipse.org/GMF_Documentation_Index
>>
>> I'll add more content later, but would encourage you and others to
>> contribute to this wiki as well. For some reason, people seem reluctant to
>> create/edit our wiki pages (to Ward's dismay, no doubt).
>>
>> Thanks again,
>> Rich
>>
>>
>> On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
>> <kuhn@oio.de> wrote:
>>
>>> hello,
>>>
>>> Intro:
>>> I'm 'working' with GMF for over 4 month now (full time), but still
>>> lacking an overview of the documentation. I think one problem is that
>>> there's no GMF book, but I doubt it that one book could address all the
>>> diversity of GMF.
>>>
>>> Existing documentation:
>>> The documentation of GMF is split into GMF-Tools (wiki) and the
>>> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
>>> runtime-articles in the wiki. A lot of concepts / features are inplicit
>>> explained in tutorials or are explained due to an implementation in an
>>> open-source project which costs extra time to find the interesting place
>>> in a complex set-up. Another good information source is of course the
>>> EclipseCon and Jax presentations, publications in EclipseMag etc. each
>>> addressing a bunch of topics. Last but not least GEF books address lots
>>> of concepts of the GMF runtime.
>>>
>>> Conclusion:
>>> My impression is that _the documentation isn't as bad as it looks like_,
>>> but it takes a lot of time finding the right place. The reason for this
>>> is because there's no aggregation (or index in terms of where to look
>>> for a specific problem) of it. For me this results in mind-numbing tasks
>>> like printing out the docs e.g. presentations, writing the treated
>>> topics on top of it and later on when I actually need it trying to
>>> remember in which resource I've read it.
>>>
>>> Suggestion(abstract):
>>> In addition to invest time to write further documentation a better time/
>>> benefit rate would be achieved with a link collection of the existing
>>> documentation.
>>>
>>> Suggestion(concrete):
>>> I guess a structured wiki-page like the index and/or the content of a
>>> book would be a very good idea.
>>>
>>>
>>> This could look like:
>>> (+link for every item)
>>>
>>> EditPolicies:
>>> Developer Guide to Diagram Runtime Framework P.10f
>>> GMF Best Practices P.8-10
>>> IBMs Redbook P.110ff
>>>
>>> Decorators(Shape):
>>> Extending your DSM by ... P22-26
>>> Creating your own DSM using GMF P.28
>>>
>>> Decorating Model:
>>> GMF Best Practices P.19-24
>>>
>>> Diagram Partitioning:
>>> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>>>
>>> Draw2D:
>>> IBMs Redbook ...
>>> Online Tutorials ...
>>>
>>> Of course this would need a better structure, but the idea should be clear.
>>>
>>>
>>> Final words:
>>> I assume the time creating this would be amortized soon in relation to
>>> the time the gmf-professionals spend in answering the recurring
>>> newsgroup questions.
>>>
>>> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>>>
>>> -stefan
>>>
>>>
>>>
>>>
>>
|
|
|
| Re: General Documentation Issue [message #146907 is a reply to message #146179] |
Thu, 16 August 2007 19:02 |
| Eclipse User |
|
|
|
ok, I spend quite some time to build this up. I made sure that
everything from the GMF Doc site is also linked. So you might consider
linking this as the primary page (it's definitely better ;). I will now
just add stuff I'm currently using, so don't hope of too much
contribution from me.
I already ran into problems:
1) The page got too big (yes, a real problem): If someone edits the
whole wiki-page and press save, nothing is transported and the whole
page is empty (all content removed).
-> already wrote the eclipse-webmasters an email
-> splitting the article doesn't make sense because it's still an index
-> an alternative would be to use templates, but this would pollute the
template namespace of the wiki with article-stuff
2) I don't know how to change the "Based on work by" phrase at the very
end ;)
greets
stefan
Richard Gronback schrieb:
> Wow, that's quite a bit. At this rate, it seems the index will certainly be
> larger than our accumulated documentation ;)
>
> I'll try to add some today (at least my name as author of the tutorial).
>
> Thanks,
> Rich
>
>
> On 8/10/07 8:46 AM, in article f9hmmg$98t$1@build.eclipse.org, "SKuhn"
> <kuhn@oio.de> wrote:
>
>> allright, I indexed 2 presentations to make a beginning for our index
>> (http://wiki.eclipse.org/GMF_Documentation_Index).
>>
>> Added following stuff:
>> Best Practices
>> Extending your DSM by leveraging the GMF Runtime
>> Developer Guide to Diagram Runtime Framework
>>
>> check out if we could start like this. As soon as I realize I'm not the
>> only person who tries to improve this index I'll add 3-4 presentations more.
>>
>> -stefan
>>
>>
>>
>> Richard Gronback schrieb:
>>> Good idea, thanks! I've created a skeleton wiki index page based on your
>>> content below, and linked it from the main documentation wiki page.
>>>
>>> http://wiki.eclipse.org/GMF_Documentation_Index
>>>
>>> I'll add more content later, but would encourage you and others to
>>> contribute to this wiki as well. For some reason, people seem reluctant to
>>> create/edit our wiki pages (to Ward's dismay, no doubt).
>>>
>>> Thanks again,
>>> Rich
>>>
>>>
>>> On 8/7/07 7:46 AM, in article f99m36$6bm$1@build.eclipse.org, "SKuhn"
>>> <kuhn@oio.de> wrote:
>>>
>>>> hello,
>>>>
>>>> Intro:
>>>> I'm 'working' with GMF for over 4 month now (full time), but still
>>>> lacking an overview of the documentation. I think one problem is that
>>>> there's no GMF book, but I doubt it that one book could address all the
>>>> diversity of GMF.
>>>>
>>>> Existing documentation:
>>>> The documentation of GMF is split into GMF-Tools (wiki) and the
>>>> GMF-Runtime (eclipse-help). This gets mixed up with e.g. FAQs or some
>>>> runtime-articles in the wiki. A lot of concepts / features are inplicit
>>>> explained in tutorials or are explained due to an implementation in an
>>>> open-source project which costs extra time to find the interesting place
>>>> in a complex set-up. Another good information source is of course the
>>>> EclipseCon and Jax presentations, publications in EclipseMag etc. each
>>>> addressing a bunch of topics. Last but not least GEF books address lots
>>>> of concepts of the GMF runtime.
>>>>
>>>> Conclusion:
>>>> My impression is that _the documentation isn't as bad as it looks like_,
>>>> but it takes a lot of time finding the right place. The reason for this
>>>> is because there's no aggregation (or index in terms of where to look
>>>> for a specific problem) of it. For me this results in mind-numbing tasks
>>>> like printing out the docs e.g. presentations, writing the treated
>>>> topics on top of it and later on when I actually need it trying to
>>>> remember in which resource I've read it.
>>>>
>>>> Suggestion(abstract):
>>>> In addition to invest time to write further documentation a better time/
>>>> benefit rate would be achieved with a link collection of the existing
>>>> documentation.
>>>>
>>>> Suggestion(concrete):
>>>> I guess a structured wiki-page like the index and/or the content of a
>>>> book would be a very good idea.
>>>>
>>>>
>>>> This could look like:
>>>> (+link for every item)
>>>>
>>>> EditPolicies:
>>>> Developer Guide to Diagram Runtime Framework P.10f
>>>> GMF Best Practices P.8-10
>>>> IBMs Redbook P.110ff
>>>>
>>>> Decorators(Shape):
>>>> Extending your DSM by ... P22-26
>>>> Creating your own DSM using GMF P.28
>>>>
>>>> Decorating Model:
>>>> GMF Best Practices P.19-24
>>>>
>>>> Diagram Partitioning:
>>>> (Guess I've seen it in) Ecore Editor @ GmfMapClass XXX and GmfGen class XYZ
>>>>
>>>> Draw2D:
>>>> IBMs Redbook ...
>>>> Online Tutorials ...
>>>>
>>>> Of course this would need a better structure, but the idea should be clear.
>>>>
>>>>
>>>> Final words:
>>>> I assume the time creating this would be amortized soon in relation to
>>>> the time the gmf-professionals spend in answering the recurring
>>>> newsgroup questions.
>>>>
>>>> What do you think? Wouldn't this be a cheap, easy and feasable improvement?
>>>>
>>>> -stefan
>>>>
>>>>
>>>>
>>>>
>
|
|
|
Goto Forum:
Current Time: Fri May 09 16:56:16 EDT 2025
Powered by FUDForum. Page generated in 0.02581 seconds |
Home