Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » EMF Client Platform
| | |
Re: EMF Client Platform [message #1065897 is a reply to message #1065833] |
Fri, 28 June 2013 07:55 |
Jonas Helming Messages: 699 Registered: July 2009 |
Senior Member |
|
|
Hi Alex,
that sounds like a good use case for ECP. The basic idea is always, you
can start with using the default components, you can adapt them step by
step or, if they don't fit at all, you can replace them.
As you only right the code you need for adaptations, this approach
should be very maintanable. Even if you would later on stop to use ECP,
you would only had coded thing, you need anyways.
Have you tried to get started using the default model explorer and the
default editor?
Regards
Jonas
Am 27.06.2013 18:42, schrieb Alex Kravets:
> Thanks Jonas.
>
> I mainly want to use the editor for the model and may some variation of
> model explorer.
>
> What I am doing is generating model editors using EMF generators
> (http://christiandietrich.files.wordpress.com/2011/07/xtend-emf-models.png)
> and refactor them for so that similar components have one base editor
> and other things that go with it. It's a bit of slow process, and in
> some instances error prone. My model is relatively simple, just a root
> node with children going to depth 3 and some constraints described in
> schema that is used by ecore. I was wondering if using ECP would make
> what I am trying to do easier and more maintainable.
>
> Regards,
> Alex
|
|
|
Re: EMF Client Platform [message #1065979 is a reply to message #1065897] |
Fri, 28 June 2013 15:35 |
Alex Kravets Messages: 561 Registered: November 2009 |
Senior Member |
|
|
Thanks Jonas,
Just starting to get familiar with the framework. Will post here if I'll have any questions. Thanks!
Jonas Helming wrote on Fri, 28 June 2013 03:55Hi Alex,
that sounds like a good use case for ECP. The basic idea is always, you
can start with using the default components, you can adapt them step by
step or, if they don't fit at all, you can replace them.
As you only right the code you need for adaptations, this approach
should be very maintanable. Even if you would later on stop to use ECP,
you would only had coded thing, you need anyways.
Have you tried to get started using the default model explorer and the
default editor?
Regards
Jonas
Am 27.06.2013 18:42, schrieb Alex Kravets:
> Thanks Jonas.
>
> I mainly want to use the editor for the model and may some variation of
> model explorer.
>
> What I am doing is generating model editors using EMF generators
> (http://christiandietrich.files.wordpress.com/2011/07/xtend-emf-models.png)
> and refactor them for so that similar components have one base editor
> and other things that go with it. It's a bit of slow process, and in
> some instances error prone. My model is relatively simple, just a root
> node with children going to depth 3 and some constraints described in
> schema that is used by ecore. I was wondering if using ECP would make
> what I am trying to do easier and more maintainable.
>
> Regards,
> Alex
|
|
| | | | | | |
Re: EMF Client Platform [message #1070556 is a reply to message #1070282] |
Thu, 18 July 2013 07:56 |
Jonas Helming Messages: 699 Registered: July 2009 |
Senior Member |
|
|
Hi Alex,
currently the editor does not support this case (including a tree
viewer), which is some kind of master detail view. However, we are
currently working on these kind of layout. But it will take some month,
until this will be released. In the meantime, I think it is pretty easy
for you, to build something like that yourself. Basically you only have
to implement a composite with two parts. On the left you use a standard
treeviewer, showing the element and its children. If you double click
the element, you render the existing editor of ECP to the right side and
pass the element which was double clicked.
Does that makes sense?
Regards
Jonas
Am 17.07.2013 18:15, schrieb Alex Kravets:
> I want to use Model Explorer content and label providers as well XMI
> input to construct a tree based on that XMI. So let's say user creates
> Libaray model in Model Explorer:
>
> Library
> ----Book
> ------Title
>
> Then editor will be tied to this model with extension .library (for
> example) and opening this file with the editor will render similar model
> as in Model Explorer. So opening Library element from Explorer will open
> Library and all its children and opening Book element will open Book and
> Title.
>
> Use case for this is our current application written in GMF. There is an
> editor that allows user to represent model using blocks (). We are
> looking into changing this to tree based approach because GMF is too
> difficult to maintain for such a simplistic model. The reason it's in
> the editor is because user can work in an editor to create model and
> editor can maximized. Editor can be broken up into different sections
> using SashForms for example.
>
> Hope this makes sense.
>
> Thanks,
> Alex
>
|
|
| | |
Re: EMF Client Platform [message #1071217 is a reply to message #1071026] |
Fri, 19 July 2013 15:22 |
Alex Kravets Messages: 561 Registered: November 2009 |
Senior Member |
|
|
Thanks Jonas. I will also look for the documentation mentioned in another thread. Regarding target definition, it all works now after I hit "update" button in the TD editor.
Alex
Jonas Helming wrote on Fri, 19 July 2013 03:21Hi,
I suggest you look at the class ModelExplorerView in *ecp.ui.e3. It
should contain everything you need (actually it does propably much
more). About the target definition: Can you tell me which elements do
not resolve?
Regards
Jonas
Am 18.07.2013 17:07, schrieb Alex Kravets:
> Yup that's exactly what I want to do, and obviously not a big deal. Are
> there any help classes available in ECP that I can use for example to
> initialize TreeViewer from the model and a base content provider that
> ECP utilized? I can of course do this myself, but wanted to see if there
> is something already available since ECP already uses reflection to do
> that and I would like to take advantage of that if possible. Also, how
> can I use constraints actions to create children based on schemas rules
> that is already done by ECP.
> Lastly, I pulled source code for ECP, but resolving target definition
> fails because some entries couldn't be resolved. I am using Eclipse 4.3.
|
|
|
Goto Forum:
Current Time: Thu Sep 19 11:03:11 GMT 2024
Powered by FUDForum. Page generated in 0.05238 seconds
|