Home » Modeling » EMF » [editor] Tree with Columns
| |
| Re: [editor] Tree with Columns [message #413796 is a reply to message #413500] |
Mon, 15 October 2007 01:47   |
 Miles Parker
Messages: 1341
Registered: July 2009 |
Senior Member |
|
|
Ed et. al.
It seems that it would be pretty 'easy' ;) to support say columns for
some interface shared across EClasses for each of that interface's
properties. For example for the Ecore meta-model itself you could have
a column for names and annotations for all ENamedElements -- trivial
example, I know. In general, one could imagine some way of mapping
property n of each column to an aribtrary EAttribute for a given
cooresponding EObject. Before I attempt to implement something custom,
any plans to support Tree Column's in EMF.edit or thoughts about
patterns for doing so?
On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
> Philipp,
>
> The MappingEditor has some fancier examples. Eclipse now directly
> supports a Tree Viewer with columns so there's no need to use a table
> tree. You'll need to learn about cell editors to support editing of
> the columns. Other than the mapping editor, which is very old, I don't
> have anything specific to point you at. In terms of EMF.edit support,
> it's a matter of making the factory's supported types include
> ITableItemLabelProvider and then specialize the item providers to
> implement getColumnText. (Eclipse 3.3.0 had a problem that
> getColumnText was used even for a tree without columns but that's fixed
> in 3.3.1.)
>
>
> Philipp W. Kutter wrote:
>> Hi.
>> There is a version of the generated Editor, named "Tree with Columns"
>>
>> Is there a tutorial or example how to add more columns, and especially
>> how to make fields editable directly in the columns?
>>
>> Has someone developed specific templates supporting this, and is ready
>> to share them?
>>
>> Any input or experience is welcome. I will post my own experiences here
>> once I am successful in doing this.
>>
>> Best, Philipp
|
|
|
| Re: [editor] Tree with Columns [message #413802 is a reply to message #413796] |
Mon, 15 October 2007 11:13 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Miles,
I've never thought about an automatic way to generate that. Generally I
would expect column support to be specific to the viewer for which the
support is being defined. I assume you know about
ITableItemLabelProvider; you can make your item providers implement that
and make your factory support that type...
Miles Parker wrote:
>
> Ed et. al.
>
> It seems that it would be pretty 'easy' ;) to support say columns for
> some interface shared across EClasses for each of that interface's
> properties. For example for the Ecore meta-model itself you could have
> a column for names and annotations for all ENamedElements -- trivial
> example, I know. In general, one could imagine some way of mapping
> property n of each column to an aribtrary EAttribute for a given
> cooresponding EObject. Before I attempt to implement something custom,
> any plans to support Tree Column's in EMF.edit or thoughts about
> patterns for doing so?
>
>
> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>
>> Philipp,
>>
>> The MappingEditor has some fancier examples. Eclipse now directly
>> supports a Tree Viewer with columns so there's no need to use a table
>> tree. You'll need to learn about cell editors to support editing of
>> the columns. Other than the mapping editor, which is very old, I
>> don't have anything specific to point you at. In terms of EMF.edit
>> support, it's a matter of making the factory's supported types
>> include ITableItemLabelProvider and then specialize the item
>> providers to implement getColumnText. (Eclipse 3.3.0 had a problem
>> that getColumnText was used even for a tree without columns but
>> that's fixed in 3.3.1.)
>>
>>
>> Philipp W. Kutter wrote:
>>> Hi.
>>> There is a version of the generated Editor, named "Tree with Columns"
>>>
>>> Is there a tutorial or example how to add more columns, and
>>> especially how to make fields editable directly in the columns?
>>>
>>> Has someone developed specific templates supporting this, and is
>>> ready to share them?
>>>
>>> Any input or experience is welcome. I will post my own experiences
>>> here once I am successful in doing this.
>>>
>>> Best, Philipp
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: [editor] Tree with Columns [message #413813 is a reply to message #413796] |
Mon, 15 October 2007 15:05 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi,
I'd say with the new TreeViewerColumn and EditingSupport-API this could
be done much easier than with the old index-based one.
This way you would generate an EditingSupport/ColumnLabelProvider pair
and use it in all Trees/Tables.
Tom
Miles Parker schrieb:
>
> Ed et. al.
>
> It seems that it would be pretty 'easy' ;) to support say columns for
> some interface shared across EClasses for each of that interface's
> properties. For example for the Ecore meta-model itself you could have a
> column for names and annotations for all ENamedElements -- trivial
> example, I know. In general, one could imagine some way of mapping
> property n of each column to an aribtrary EAttribute for a given
> cooresponding EObject. Before I attempt to implement something custom,
> any plans to support Tree Column's in EMF.edit or thoughts about
> patterns for doing so?
>
>
> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>
>> Philipp,
>>
>> The MappingEditor has some fancier examples. Eclipse now directly
>> supports a Tree Viewer with columns so there's no need to use a table
>> tree. You'll need to learn about cell editors to support editing of
>> the columns. Other than the mapping editor, which is very old, I
>> don't have anything specific to point you at. In terms of EMF.edit
>> support, it's a matter of making the factory's supported types include
>> ITableItemLabelProvider and then specialize the item providers to
>> implement getColumnText. (Eclipse 3.3.0 had a problem that
>> getColumnText was used even for a tree without columns but that's
>> fixed in 3.3.1.)
>>
>>
>> Philipp W. Kutter wrote:
>>> Hi.
>>> There is a version of the generated Editor, named "Tree with Columns"
>>>
>>> Is there a tutorial or example how to add more columns, and
>>> especially how to make fields editable directly in the columns?
>>>
>>> Has someone developed specific templates supporting this, and is
>>> ready to share them?
>>>
>>> Any input or experience is welcome. I will post my own experiences
>>> here once I am successful in doing this.
>>>
>>> Best, Philipp
>
>
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
|
| Re: [editor] Tree with Columns [message #413816 is a reply to message #413813] |
Mon, 15 October 2007 16:03 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Tom,
We'll need to understand what we could do in EMF to exploit/enable
this. So much to do and so little time...
Tom Schindl wrote:
> Hi,
>
> I'd say with the new TreeViewerColumn and EditingSupport-API this
> could be done much easier than with the old index-based one.
>
> This way you would generate an EditingSupport/ColumnLabelProvider pair
> and use it in all Trees/Tables.
>
> Tom
>
> Miles Parker schrieb:
>>
>> Ed et. al.
>>
>> It seems that it would be pretty 'easy' ;) to support say columns for
>> some interface shared across EClasses for each of that interface's
>> properties. For example for the Ecore meta-model itself you could
>> have a column for names and annotations for all ENamedElements --
>> trivial example, I know. In general, one could imagine some way of
>> mapping property n of each column to an aribtrary EAttribute for a
>> given cooresponding EObject. Before I attempt to implement something
>> custom, any plans to support Tree Column's in EMF.edit or thoughts
>> about patterns for doing so?
>>
>>
>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Philipp,
>>>
>>> The MappingEditor has some fancier examples. Eclipse now directly
>>> supports a Tree Viewer with columns so there's no need to use a
>>> table tree. You'll need to learn about cell editors to support
>>> editing of the columns. Other than the mapping editor, which is
>>> very old, I don't have anything specific to point you at. In terms
>>> of EMF.edit support, it's a matter of making the factory's supported
>>> types include ITableItemLabelProvider and then specialize the item
>>> providers to implement getColumnText. (Eclipse 3.3.0 had a problem
>>> that getColumnText was used even for a tree without columns but
>>> that's fixed in 3.3.1.)
>>>
>>>
>>> Philipp W. Kutter wrote:
>>>> Hi.
>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>
>>>> Is there a tutorial or example how to add more columns, and
>>>> especially how to make fields editable directly in the columns?
>>>>
>>>> Has someone developed specific templates supporting this, and is
>>>> ready to share them?
>>>>
>>>> Any input or experience is welcome. I will post my own experiences
>>>> here once I am successful in doing this.
>>>>
>>>> Best, Philipp
>>
>>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: [editor] Tree with Columns [message #413817 is a reply to message #413816] |
Mon, 15 October 2007 16:06 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Ed,
Once I have time I'll try to come up with a solution :-)
Tom
Ed Merks schrieb:
> Tom,
>
> We'll need to understand what we could do in EMF to exploit/enable
> this. So much to do and so little time...
>
>
> Tom Schindl wrote:
>> Hi,
>>
>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>> could be done much easier than with the old index-based one.
>>
>> This way you would generate an EditingSupport/ColumnLabelProvider pair
>> and use it in all Trees/Tables.
>>
>> Tom
>>
>> Miles Parker schrieb:
>>>
>>> Ed et. al.
>>>
>>> It seems that it would be pretty 'easy' ;) to support say columns for
>>> some interface shared across EClasses for each of that interface's
>>> properties. For example for the Ecore meta-model itself you could
>>> have a column for names and annotations for all ENamedElements --
>>> trivial example, I know. In general, one could imagine some way of
>>> mapping property n of each column to an aribtrary EAttribute for a
>>> given cooresponding EObject. Before I attempt to implement something
>>> custom, any plans to support Tree Column's in EMF.edit or thoughts
>>> about patterns for doing so?
>>>
>>>
>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>
>>>> Philipp,
>>>>
>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>> supports a Tree Viewer with columns so there's no need to use a
>>>> table tree. You'll need to learn about cell editors to support
>>>> editing of the columns. Other than the mapping editor, which is
>>>> very old, I don't have anything specific to point you at. In terms
>>>> of EMF.edit support, it's a matter of making the factory's supported
>>>> types include ITableItemLabelProvider and then specialize the item
>>>> providers to implement getColumnText. (Eclipse 3.3.0 had a problem
>>>> that getColumnText was used even for a tree without columns but
>>>> that's fixed in 3.3.1.)
>>>>
>>>>
>>>> Philipp W. Kutter wrote:
>>>>> Hi.
>>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>>
>>>>> Is there a tutorial or example how to add more columns, and
>>>>> especially how to make fields editable directly in the columns?
>>>>>
>>>>> Has someone developed specific templates supporting this, and is
>>>>> ready to share them?
>>>>>
>>>>> Any input or experience is welcome. I will post my own experiences
>>>>> here once I am successful in doing this.
>>>>>
>>>>> Best, Philipp
>>>
>>>
>>
>>
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
|
| Re: [editor] Tree with Columns [message #413820 is a reply to message #413817] |
Mon, 15 October 2007 16:15 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Tom,
You're like an angel from heaven! O:-)
Tom Schindl wrote:
> Ed,
>
> Once I have time I'll try to come up with a solution :-)
>
> Tom
>
> Ed Merks schrieb:
>> Tom,
>>
>> We'll need to understand what we could do in EMF to exploit/enable
>> this. So much to do and so little time...
>>
>>
>> Tom Schindl wrote:
>>> Hi,
>>>
>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>> could be done much easier than with the old index-based one.
>>>
>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>> pair and use it in all Trees/Tables.
>>>
>>> Tom
>>>
>>> Miles Parker schrieb:
>>>>
>>>> Ed et. al.
>>>>
>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>> for some interface shared across EClasses for each of that
>>>> interface's properties. For example for the Ecore meta-model itself
>>>> you could have a column for names and annotations for all
>>>> ENamedElements -- trivial example, I know. In general, one could
>>>> imagine some way of mapping property n of each column to an
>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>> attempt to implement something custom, any plans to support Tree
>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>
>>>>
>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>
>>>>> Philipp,
>>>>>
>>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>>> supports a Tree Viewer with columns so there's no need to use a
>>>>> table tree. You'll need to learn about cell editors to support
>>>>> editing of the columns. Other than the mapping editor, which is
>>>>> very old, I don't have anything specific to point you at. In
>>>>> terms of EMF.edit support, it's a matter of making the factory's
>>>>> supported types include ITableItemLabelProvider and then
>>>>> specialize the item providers to implement getColumnText.
>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even for
>>>>> a tree without columns but that's fixed in 3.3.1.)
>>>>>
>>>>>
>>>>> Philipp W. Kutter wrote:
>>>>>> Hi.
>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>> Columns"
>>>>>>
>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>> especially how to make fields editable directly in the columns?
>>>>>>
>>>>>> Has someone developed specific templates supporting this, and is
>>>>>> ready to share them?
>>>>>>
>>>>>> Any input or experience is welcome. I will post my own
>>>>>> experiences here once I am successful in doing this.
>>>>>>
>>>>>> Best, Philipp
>>>>
>>>>
>>>
>>>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: [editor] Tree with Columns [message #413825 is a reply to message #413802] |
Mon, 15 October 2007 19:29 |
Miles Parker
Messages: 1341
Registered: July 2009 |
Senior Member |
|
|
On 2007-10-15 07:13:21 -0400, Ed Merks <merks@ca.ibm.com> said:
> Miles,
>
> I've never thought about an automatic way to generate that. Generally
> I would expect column support to be specific to the viewer for which
> the support is being defined.
Yes, that is definetly true..I guess I was thinking of something along
the lines of the default Tree Editor which has worked very well for me.
I find it awkward to click back and forth from the tree view to the
property editor, so I'd love the ability to allow users to edit key
attributes directly from the Tree row. Together with drag and drop that
would create a very powerful intuitive editor for hierarchically
organized data. (Say a visual behavior editor.)
> I assume you know about ITableItemLabelProvider; you can make your item
> providers implement that and make your factory support that type...
Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
is still pretty light, but yes -- especially with the nice support for
custom provider roots (thanks again) it would be a very simple matter
to continue to use the same adapters for all of my base
behavior..perfect. The "only" remaining piece then would be editing
support as Tom discusses.
It seems in fact from my reading of things that at the EMF API level
anyway would be to do something like provide a
getColumnPropertyDescriptor(int columnIndex)
in ITableItemProvider or elsewhere. That would be extremely nice..
>
>
> Miles Parker wrote:
>>
>> Ed et. al.
>>
>> It seems that it would be pretty 'easy' ;) to support say columns for
>> some interface shared across EClasses for each of that interface's
>> properties. For example for the Ecore meta-model itself you could have
>> a column for names and annotations for all ENamedElements -- trivial
>> example, I know. In general, one could imagine some way of mapping
>> property n of each column to an aribtrary EAttribute for a given
>> cooresponding EObject. Before I attempt to implement something custom,
>> any plans to support Tree Column's in EMF.edit or thoughts about
>> patterns for doing so?
>>
>>
>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Philipp,
>>>
>>> The MappingEditor has some fancier examples. Eclipse now directly
>>> supports a Tree Viewer with columns so there's no need to use a table
>>> tree. You'll need to learn about cell editors to support editing of
>>> the columns. Other than the mapping editor, which is very old, I don't
>>> have anything specific to point you at. In terms of EMF.edit support,
>>> it's a matter of making the factory's supported types include
>>> ITableItemLabelProvider and then specialize the item providers to
>>> implement getColumnText. (Eclipse 3.3.0 had a problem that
>>> getColumnText was used even for a tree without columns but that's fixed
>>> in 3.3.1.)
>>>
>>>
>>> Philipp W. Kutter wrote:
>>>> Hi.
>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>
>>>> Is there a tutorial or example how to add more columns, and especially
>>>> how to make fields editable directly in the columns?
>>>>
>>>> Has someone developed specific templates supporting this, and is ready
>>>> to share them?
>>>>
>>>> Any input or experience is welcome. I will post my own experiences here
>>>> once I am successful in doing this.
>>>>
>>>> Best, Philipp
|
|
|
| Re: [editor] Tree with Columns [message #413826 is a reply to message #413825] |
Mon, 15 October 2007 20:02 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Miles,
Yes, support for editing cells of a table would be cool. Something
like IUpdateableItemText already lets you do some in place editing in
the tree itself...
Miles Parker wrote:
>
>
> On 2007-10-15 07:13:21 -0400, Ed Merks <merks@ca.ibm.com> said:
>
>> Miles,
>>
>> I've never thought about an automatic way to generate that.
>> Generally I would expect column support to be specific to the viewer
>> for which the support is being defined.
>
> Yes, that is definetly true..I guess I was thinking of something along
> the lines of the default Tree Editor which has worked very well for
> me. I find it awkward to click back and forth from the tree view to
> the property editor, so I'd love the ability to allow users to edit
> key attributes directly from the Tree row. Together with drag and drop
> that would create a very powerful intuitive editor for hierarchically
> organized data. (Say a visual behavior editor.)
>
>> I assume you know about ITableItemLabelProvider; you can make your
>> item providers implement that and make your factory support that type...
>
> Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
> is still pretty light, but yes -- especially with the nice support for
> custom provider roots (thanks again) it would be a very simple matter
> to continue to use the same adapters for all of my base
> behavior..perfect. The "only" remaining piece then would be editing
> support as Tom discusses.
>
> It seems in fact from my reading of things that at the EMF API level
> anyway would be to do something like provide a
>
> getColumnPropertyDescriptor(int columnIndex)
>
> in ITableItemProvider or elsewhere. That would be extremely nice..
>
>
>>
>>
>> Miles Parker wrote:
>>>
>>> Ed et. al.
>>>
>>> It seems that it would be pretty 'easy' ;) to support say columns
>>> for some interface shared across EClasses for each of that
>>> interface's properties. For example for the Ecore meta-model itself
>>> you could have a column for names and annotations for all
>>> ENamedElements -- trivial example, I know. In general, one could
>>> imagine some way of mapping property n of each column to an
>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>> attempt to implement something custom, any plans to support Tree
>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>
>>>
>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>
>>>> Philipp,
>>>>
>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>> supports a Tree Viewer with columns so there's no need to use a
>>>> table tree. You'll need to learn about cell editors to support
>>>> editing of the columns. Other than the mapping editor, which is
>>>> very old, I don't have anything specific to point you at. In terms
>>>> of EMF.edit support, it's a matter of making the factory's
>>>> supported types include ITableItemLabelProvider and then specialize
>>>> the item providers to implement getColumnText. (Eclipse 3.3.0 had
>>>> a problem that getColumnText was used even for a tree without
>>>> columns but that's fixed in 3.3.1.)
>>>>
>>>>
>>>> Philipp W. Kutter wrote:
>>>>> Hi.
>>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>>
>>>>> Is there a tutorial or example how to add more columns, and
>>>>> especially how to make fields editable directly in the columns?
>>>>>
>>>>> Has someone developed specific templates supporting this, and is
>>>>> ready to share them?
>>>>>
>>>>> Any input or experience is welcome. I will post my own experiences
>>>>> here once I am successful in doing this.
>>>>>
>>>>> Best, Philipp
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: [editor] Tree with Columns [message #413827 is a reply to message #413826] |
Mon, 15 October 2007 20:33 |
Miles Parker
Messages: 1341
Registered: July 2009 |
Senior Member |
|
|
I didn't know that..cool!
On 2007-10-15 16:02:29 -0400, Ed Merks <merks@ca.ibm.com> said:
> Miles,
>
> Yes, support for editing cells of a table would be cool. Something
> like IUpdateableItemText already lets you do some in place editing in
> the tree itself...
>
>
> Miles Parker wrote:
>>
>>
>> On 2007-10-15 07:13:21 -0400, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Miles,
>>>
>>> I've never thought about an automatic way to generate that. Generally
>>> I would expect column support to be specific to the viewer for which
>>> the support is being defined.
>>
>> Yes, that is definetly true..I guess I was thinking of something along
>> the lines of the default Tree Editor which has worked very well for me.
>> I find it awkward to click back and forth from the tree view to the
>> property editor, so I'd love the ability to allow users to edit key
>> attributes directly from the Tree row. Together with drag and drop that
>> would create a very powerful intuitive editor for hierarchically
>> organized data. (Say a visual behavior editor.)
>>
>>> I assume you know about ITableItemLabelProvider; you can make your item
>>> providers implement that and make your factory support that type...
>>
>> Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
>> is still pretty light, but yes -- especially with the nice support for
>> custom provider roots (thanks again) it would be a very simple matter
>> to continue to use the same adapters for all of my base
>> behavior..perfect. The "only" remaining piece then would be editing
>> support as Tom discusses.
>>
>> It seems in fact from my reading of things that at the EMF API level
>> anyway would be to do something like provide a
>>
>> getColumnPropertyDescriptor(int columnIndex)
>>
>> in ITableItemProvider or elsewhere. That would be extremely nice..
>>
>>
>>>
>>>
>>> Miles Parker wrote:
>>>>
>>>> Ed et. al.
>>>>
>>>> It seems that it would be pretty 'easy' ;) to support say columns for
>>>> some interface shared across EClasses for each of that interface's
>>>> properties. For example for the Ecore meta-model itself you could have
>>>> a column for names and annotations for all ENamedElements -- trivial
>>>> example, I know. In general, one could imagine some way of mapping
>>>> property n of each column to an aribtrary EAttribute for a given
>>>> cooresponding EObject. Before I attempt to implement something custom,
>>>> any plans to support Tree Column's in EMF.edit or thoughts about
>>>> patterns for doing so?
>>>>
>>>>
>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>
>>>>> Philipp,
>>>>>
>>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>>> supports a Tree Viewer with columns so there's no need to use a table
>>>>> tree. You'll need to learn about cell editors to support editing of
>>>>> the columns. Other than the mapping editor, which is very old, I don't
>>>>> have anything specific to point you at. In terms of EMF.edit support,
>>>>> it's a matter of making the factory's supported types include
>>>>> ITableItemLabelProvider and then specialize the item providers to
>>>>> implement getColumnText. (Eclipse 3.3.0 had a problem that
>>>>> getColumnText was used even for a tree without columns but that's fixed
>>>>> in 3.3.1.)
>>>>>
>>>>>
>>>>> Philipp W. Kutter wrote:
>>>>>> Hi.
>>>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>>>
>>>>>> Is there a tutorial or example how to add more columns, and especially
>>>>>> how to make fields editable directly in the columns?
>>>>>>
>>>>>> Has someone developed specific templates supporting this, and is ready
>>>>>> to share them?
>>>>>>
>>>>>> Any input or experience is welcome. I will post my own experiences here
>>>>>> once I am successful in doing this.
>>>>>>
>>>>>> Best, Philipp
|
|
|
| Re: [editor] Tree with Columns [message #413828 is a reply to message #413827] |
Mon, 15 October 2007 20:41 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040000020600050300080909
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Miles,
*E*xceedingly *M*any *F*eatures. Or is that *E*xcellent *M*ystery
*F*unctionality.
Miles Parker wrote:
>
> I didn't know that..cool!
>
> On 2007-10-15 16:02:29 -0400, Ed Merks <merks@ca.ibm.com> said:
>
>> Miles,
>>
>> Yes, support for editing cells of a table would be cool. Something
>> like IUpdateableItemText already lets you do some in place editing in
>> the tree itself...
>>
>>
>> Miles Parker wrote:
>>>
>>>
>>> On 2007-10-15 07:13:21 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>
>>>> Miles,
>>>>
>>>> I've never thought about an automatic way to generate that.
>>>> Generally I would expect column support to be specific to the
>>>> viewer for which the support is being defined.
>>>
>>> Yes, that is definetly true..I guess I was thinking of something
>>> along the lines of the default Tree Editor which has worked very
>>> well for me. I find it awkward to click back and forth from the tree
>>> view to the property editor, so I'd love the ability to allow users
>>> to edit key attributes directly from the Tree row. Together with
>>> drag and drop that would create a very powerful intuitive editor for
>>> hierarchically organized data. (Say a visual behavior editor.)
>>>
>>>> I assume you know about ITableItemLabelProvider; you can make your
>>>> item providers implement that and make your factory support that
>>>> type...
>>>
>>> Well, that might be assuming a lot ;) esp. as my SWT/JFace
>>> expereince is still pretty light, but yes -- especially with the
>>> nice support for custom provider roots (thanks again) it would be a
>>> very simple matter to continue to use the same adapters for all of
>>> my base behavior..perfect. The "only" remaining piece then would be
>>> editing support as Tom discusses.
>>>
>>> It seems in fact from my reading of things that at the EMF API level
>>> anyway would be to do something like provide a
>>>
>>> getColumnPropertyDescriptor(int columnIndex)
>>>
>>> in ITableItemProvider or elsewhere. That would be extremely nice..
>>>
>>>
>>>>
>>>>
>>>> Miles Parker wrote:
>>>>>
>>>>> Ed et. al.
>>>>>
>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>> for some interface shared across EClasses for each of that
>>>>> interface's properties. For example for the Ecore meta-model
>>>>> itself you could have a column for names and annotations for all
>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>> imagine some way of mapping property n of each column to an
>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>> attempt to implement something custom, any plans to support Tree
>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>
>>>>>
>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>
>>>>>> Philipp,
>>>>>>
>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>> directly supports a Tree Viewer with columns so there's no need
>>>>>> to use a table tree. You'll need to learn about cell editors to
>>>>>> support editing of the columns. Other than the mapping editor,
>>>>>> which is very old, I don't have anything specific to point you
>>>>>> at. In terms of EMF.edit support, it's a matter of making the
>>>>>> factory's supported types include ITableItemLabelProvider and
>>>>>> then specialize the item providers to implement getColumnText.
>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even for
>>>>>> a tree without columns but that's fixed in 3.3.1.)
>>>>>>
>>>>>>
>>>>>> Philipp W. Kutter wrote:
>>>>>>> Hi.
>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>> Columns"
>>>>>>>
>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>
>>>>>>> Has someone developed specific templates supporting this, and is
>>>>>>> ready to share them?
>>>>>>>
>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>> experiences here once I am successful in doing this.
>>>>>>>
>>>>>>> Best, Philipp
>
>
--------------040000020600050300080909
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Miles,<br>
<br>
<big><b>E</b></big>xceedingly <big><b>M</b></big>any <big><b>F</b></big>eatures.
Or is that <big><b>E</b></big>xcellent <big><b>M</b></big>ystery <big><b>F</b></big>unctionality.<br>
<br>
<br>
Miles Parker wrote:
<blockquote cite="mid:ff0iqm$m6b$1@build.eclipse.org" type="cite"><br>
I didn't know that..cool!
<br>
<br>
On 2007-10-15 16:02:29 -0400, Ed Merks <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
<br>
<br>
<blockquote type="cite">Miles,
<br>
<br>
Yes, support for editing cells of a table would be cool. Something
like IUpdateableItemText already lets you do some in place editing in
the tree itself...
<br>
<br>
<br>
Miles Parker wrote:
<br>
<blockquote type="cite"><br>
<br>
On 2007-10-15 07:13:21 -0400, Ed Merks <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
<br>
<br>
<blockquote type="cite">Miles,
<br>
<br>
I've never thought about an automatic way to generate that. Generally
I would expect column support to be specific to the viewer for which
the support is being defined.
<br>
</blockquote>
<br>
Yes, that is definetly true..I guess I was thinking of something along
the lines of the default Tree Editor which has worked very well for me.
I find it awkward to click back and forth from the tree view to the
property editor, so I'd love the ability to allow users to edit key
attributes directly from the Tree row. Together with drag and drop that
would create a very powerful intuitive editor for hierarchically
organized data. (Say a visual behavior editor.)
<br>
<br>
<blockquote type="cite">I assume you know about
ITableItemLabelProvider; you can make your item providers implement
that and make your factory support that type...
<br>
</blockquote>
<br>
Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
is still pretty light, but yes -- especially with the nice support for
custom provider roots (thanks again) it would be a very simple matter
to continue to use the same adapters for all of my base
behavior..perfect. The "only" remaining piece then would be editing
support as Tom discusses.
<br>
<br>
It seems in fact from my reading of things that at the EMF API level
anyway would be to do something like provide a
<br>
<br>
getColumnPropertyDescriptor(int columnIndex)
<br>
<br>
in ITableItemProvider or elsewhere. That would be extremely nice..
<br>
<br>
<br>
<blockquote type="cite"><br>
<br>
Miles Parker wrote:
<br>
<blockquote type="cite"><br>
Ed et. al.
<br>
<br>
It seems that it would be pretty 'easy' ;) to support say columns for
some interface shared across EClasses for each of that interface's
properties. For example for the Ecore meta-model itself you could have
a column for names and annotations for all ENamedElements -- trivial
example, I know. In general, one could imagine some way of mapping
property n of each column to an aribtrary EAttribute for a given
cooresponding EObject. Before I attempt to implement something custom,
any plans to support Tree Column's in EMF.edit or thoughts about
patterns for doing so?
<br>
<br>
<br>
On 2007-10-02 07:27:25 -0400, Ed Merks <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
<br>
<br>
<blockquote type="cite">Philipp,
<br>
<br>
The MappingEditor has some fancier examples. Eclipse now directly
supports a Tree Viewer with columns so there's no need to use a table
tree. You'll need to learn about cell editors to support editing of
the columns. Other than the mapping editor, which is very old, I don't
have anything specific to point you at. In terms of EMF.edit support,
it's a matter of making the factory's supported types include
ITableItemLabelProvider and then specialize the item providers to
implement getColumnText. (Eclipse 3.3.0 had a problem that
getColumnText was used even for a tree without columns but that's fixed
in 3.3.1.)
<br>
<br>
<br>
Philipp W. Kutter wrote:
<br>
<blockquote type="cite">Hi.
<br>
There is a version of the generated Editor, named "Tree with Columns"
<br>
<br>
Is there a tutorial or example how to add more columns, and especially
how to make fields editable directly in the columns?
<br>
<br>
Has someone developed specific templates supporting this, and is ready
to share them?
<br>
<br>
Any input or experience is welcome. I will post my own experiences here
once I am successful in doing this.
<br>
<br>
Best, Philipp
<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>
--------------040000020600050300080909--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: [editor] Tree with Columns [message #413830 is a reply to message #413828] |
Mon, 15 October 2007 21:10 |
Miles Parker
Messages: 1341
Registered: July 2009 |
Senior Member |
|
|
I much prefer a tool where the rate of new feature implementation
exceeds that of the rate of feature promotion to one in which the rate
of new feature promotion greatly exceeds the rate of actual feature
implementation. Not naming ..cough..(redmond)..cough.. names..
On 2007-10-15 16:41:15 -0400, Ed Merks <merks@ca.ibm.com> said:
>
> Miles,
>
> *E*xceedingly *M*any *F*eatures. Or is that *E*xcellent *M*ystery
> *F*unctionality.
>
>
> Miles Parker wrote:
>>
>> I didn't know that..cool!
>>
>> On 2007-10-15 16:02:29 -0400, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Miles,
>>>
>>> Yes, support for editing cells of a table would be cool. Something
>>> like IUpdateableItemText already lets you do some in place editing in
>>> the tree itself...
>>>
>>>
>>> Miles Parker wrote:
>>>>
>>>>
>>>> On 2007-10-15 07:13:21 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>
>>>>> Miles,
>>>>>
>>>>> I've never thought about an automatic way to generate that. Generally
>>>>> I would expect column support to be specific to the viewer for which
>>>>> the support is being defined.
>>>>
>>>> Yes, that is definetly true..I guess I was thinking of something along
>>>> the lines of the default Tree Editor which has worked very well for me.
>>>> I find it awkward to click back and forth from the tree view to the
>>>> property editor, so I'd love the ability to allow users to edit key
>>>> attributes directly from the Tree row. Together with drag and drop that
>>>> would create a very powerful intuitive editor for hierarchically
>>>> organized data. (Say a visual behavior editor.)
>>>>
>>>>> I assume you know about ITableItemLabelProvider; you can make your item
>>>>> providers implement that and make your factory support that type...
>>>>
>>>> Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
>>>> is still pretty light, but yes -- especially with the nice support for
>>>> custom provider roots (thanks again) it would be a very simple matter
>>>> to continue to use the same adapters for all of my base
>>>> behavior..perfect. The "only" remaining piece then would be editing
>>>> support as Tom discusses.
>>>>
>>>> It seems in fact from my reading of things that at the EMF API level
>>>> anyway would be to do something like provide a
>>>>
>>>> getColumnPropertyDescriptor(int columnIndex)
>>>>
>>>> in ITableItemProvider or elsewhere. That would be extremely nice..
>>>>
>>>>
>>>>>
>>>>>
>>>>> Miles Parker wrote:
>>>>>>
>>>>>> Ed et. al.
>>>>>>
>>>>>> It seems that it would be pretty 'easy' ;) to support say columns for
>>>>>> some interface shared across EClasses for each of that interface's
>>>>>> properties. For example for the Ecore meta-model itself you could have
>>>>>> a column for names and annotations for all ENamedElements -- trivial
>>>>>> example, I know. In general, one could imagine some way of mapping
>>>>>> property n of each column to an aribtrary EAttribute for a given
>>>>>> cooresponding EObject. Before I attempt to implement something custom,
>>>>>> any plans to support Tree Column's in EMF.edit or thoughts about
>>>>>> patterns for doing so?
>>>>>>
>>>>>>
>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>
>>>>>>> Philipp,
>>>>>>>
>>>>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>>>>> supports a Tree Viewer with columns so there's no need to use a table
>>>>>>> tree. You'll need to learn about cell editors to support editing of
>>>>>>> the columns. Other than the mapping editor, which is very old, I don't
>>>>>>> have anything specific to point you at. In terms of EMF.edit support,
>>>>>>> it's a matter of making the factory's supported types include
>>>>>>> ITableItemLabelProvider and then specialize the item providers to
>>>>>>> implement getColumnText. (Eclipse 3.3.0 had a problem that
>>>>>>> getColumnText was used even for a tree without columns but that's fixed
>>>>>>> in 3.3.1.)
>>>>>>>
>>>>>>>
>>>>>>> Philipp W. Kutter wrote:
>>>>>>>> Hi.
>>>>>>>> There is a version of the generated Editor, named "Tree with Columns"
>>>>>>>>
>>>>>>>> Is there a tutorial or example how to add more columns, and especially
>>>>>>>> how to make fields editable directly in the columns?
>>>>>>>>
>>>>>>>> Has someone developed specific templates supporting this, and is ready
>>>>>>>> to share them?
>>>>>>>>
>>>>>>>> Any input or experience is welcome. I will post my own experiences here
>>>>>>>> once I am successful in doing this.
>>>>>>>>
>>>>>>>> Best, Philipp
>>
>>
>
>
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> Miles,<br>
> <br>
> <big><b>E</b></big>xceedingly <big><b>M</b></big>any
> <big><b>F</b></big>eatures.
> Or is that <big><b>E</b></big>xcellent <big><b>M</b></big>ystery
> <big><b>F</b></big>unctionality.<br>
> <br>
> <br>
> Miles Parker wrote:
> <blockquote cite="mid:ff0iqm$m6b$1@build.eclipse.org" type="cite"><br>
> I didn't know that..cool!
> <br>
> <br>
> On 2007-10-15 16:02:29 -0400, Ed Merks <a class="moz-txt-link-rfc2396E"
> href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
> <br>
> <br>
> <blockquote type="cite">Miles,
> <br>
> <br>
> Yes, support for editing cells of a table would be cool. Something
> like IUpdateableItemText already lets you do some in place editing in
> the tree itself...
> <br>
> <br>
> <br>
> Miles Parker wrote:
> <br>
> <blockquote type="cite"><br>
> <br>
> On 2007-10-15 07:13:21 -0400, Ed Merks <a class="moz-txt-link-rfc2396E"
> href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
> <br>
> <br>
> <blockquote type="cite">Miles,
> <br>
> <br>
> I've never thought about an automatic way to generate that. Generally
> I would expect column support to be specific to the viewer for which
> the support is being defined.
> <br>
> </blockquote>
> <br>
> Yes, that is definetly true..I guess I was thinking of something along
> the lines of the default Tree Editor which has worked very well for me.
> I find it awkward to click back and forth from the tree view to the
> property editor, so I'd love the ability to allow users to edit key
> attributes directly from the Tree row. Together with drag and drop that
> would create a very powerful intuitive editor for hierarchically
> organized data. (Say a visual behavior editor.)
> <br>
> <br>
> <blockquote type="cite">I assume you know about
> ITableItemLabelProvider; you can make your item providers implement
> that and make your factory support that type...
> <br>
> </blockquote>
> <br>
> Well, that might be assuming a lot ;) esp. as my SWT/JFace expereince
> is still pretty light, but yes -- especially with the nice support for
> custom provider roots (thanks again) it would be a very simple matter
> to continue to use the same adapters for all of my base
> behavior..perfect. The "only" remaining piece then would be editing
> support as Tom discusses.
> <br>
> <br>
> It seems in fact from my reading of things that at the EMF API level
> anyway would be to do something like provide a
> <br>
> <br>
> getColumnPropertyDescriptor(int columnIndex)
> <br>
> <br>
> in ITableItemProvider or elsewhere. That would be extremely nice..
> <br>
> <br>
> <br>
> <blockquote type="cite"><br>
> <br>
> Miles Parker wrote:
> <br>
> <blockquote type="cite"><br>
> Ed et. al.
> <br>
> <br>
> It seems that it would be pretty 'easy' ;) to support say columns for
> some interface shared across EClasses for each of that interface's
> properties. For example for the Ecore meta-model itself you could have
> a column for names and annotations for all ENamedElements -- trivial
> example, I know. In general, one could imagine some way of mapping
> property n of each column to an aribtrary EAttribute for a given
> cooresponding EObject. Before I attempt to implement something custom,
> any plans to support Tree Column's in EMF.edit or thoughts about
> patterns for doing so?
> <br>
> <br>
> <br>
> On 2007-10-02 07:27:25 -0400, Ed Merks <a class="moz-txt-link-rfc2396E"
> href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> said:
> <br>
> <br>
> <blockquote type="cite">Philipp,
> <br>
> <br>
> The MappingEditor has some fancier examples. Eclipse now directly
> supports a Tree Viewer with columns so there's no need to use a table
> tree. You'll need to learn about cell editors to support editing of
> the columns. Other than the mapping editor, which is very old, I don't
> have anything specific to point you at. In terms of EMF.edit support,
> it's a matter of making the factory's supported types include
> ITableItemLabelProvider and then specialize the item providers to
> implement getColumnText. (Eclipse 3.3.0 had a problem that
> getColumnText was used even for a tree without columns but that's fixed
> in 3.3.1.)
> <br>
> <br>
> <br>
> Philipp W. Kutter wrote:
> <br>
> <blockquote type="cite">Hi.
> <br>
> There is a version of the generated Editor, named "Tree with Columns"
> <br>
> <br>
> Is there a tutorial or example how to add more columns, and especially
> how to make fields editable directly in the columns?
> <br>
> <br>
> Has someone developed specific templates supporting this, and is ready
> to share them?
> <br>
> <br>
> Any input or experience is welcome. I will post my own experiences here
> once I am successful in doing this.
> <br>
> <br>
> Best, Philipp
> <br>
> </blockquote>
> </blockquote>
> </blockquote>
> </blockquote>
> </blockquote>
> </blockquote>
> <br>
> <br>
> </blockquote>
> <br>
> </body>
> </html>
|
|
| |
| Running Prototype for Tree with Columns [message #414504 is a reply to message #413820] |
Fri, 09 November 2007 15:49 |
Philipp Kutter
Messages: 306
Registered: July 2009 |
Senior Member |
|
|
Hi, Ed.
I have a running prototype.
It allows to have the same edit support you have in the
standard property view, for references and attributes.
If there is someone who has a couple days time, and wants to improve the
example, he can contact me at kutter@montages.com
With a little time, this can be turned into a useful example/tutorial
for the community. Maybe Miles, Tom, or Ron are interested.. With even
a little more time, it could be turned into an improved editor JET which
shows the label-feature editable in the second column.
Best, Philipp
Ed Merks wrote:
> Tom,
>
> You're like an angel from heaven! O:-)
>
>
> Tom Schindl wrote:
>> Ed,
>>
>> Once I have time I'll try to come up with a solution :-)
>>
>> Tom
>>
>> Ed Merks schrieb:
>>> Tom,
>>>
>>> We'll need to understand what we could do in EMF to exploit/enable
>>> this. So much to do and so little time...
>>>
>>>
>>> Tom Schindl wrote:
>>>> Hi,
>>>>
>>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>>> could be done much easier than with the old index-based one.
>>>>
>>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>>> pair and use it in all Trees/Tables.
>>>>
>>>> Tom
>>>>
>>>> Miles Parker schrieb:
>>>>>
>>>>> Ed et. al.
>>>>>
>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>> for some interface shared across EClasses for each of that
>>>>> interface's properties. For example for the Ecore meta-model itself
>>>>> you could have a column for names and annotations for all
>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>> imagine some way of mapping property n of each column to an
>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>> attempt to implement something custom, any plans to support Tree
>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>
>>>>>
>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>
>>>>>> Philipp,
>>>>>>
>>>>>> The MappingEditor has some fancier examples. Eclipse now directly
>>>>>> supports a Tree Viewer with columns so there's no need to use a
>>>>>> table tree. You'll need to learn about cell editors to support
>>>>>> editing of the columns. Other than the mapping editor, which is
>>>>>> very old, I don't have anything specific to point you at. In
>>>>>> terms of EMF.edit support, it's a matter of making the factory's
>>>>>> supported types include ITableItemLabelProvider and then
>>>>>> specialize the item providers to implement getColumnText.
>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even for
>>>>>> a tree without columns but that's fixed in 3.3.1.)
>>>>>>
>>>>>>
>>>>>> Philipp W. Kutter wrote:
>>>>>>> Hi.
>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>> Columns"
>>>>>>>
>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>
>>>>>>> Has someone developed specific templates supporting this, and is
>>>>>>> ready to share them?
>>>>>>>
>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>> experiences here once I am successful in doing this.
>>>>>>>
>>>>>>> Best, Philipp
>>>>>
>>>>>
>>>>
>>>>
>>
>>
|
|
|
| Re: Running Prototype for Tree with Columns [message #414507 is a reply to message #414504] |
Fri, 09 November 2007 16:19 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Philipp,
Maybe it would be good to open bugzilla feature request and put it as an
attachment.
Note that with IUpdateableItemText it's possible to support in-place
editing directly in the tree view.
Philipp W. Kutter wrote:
> Hi, Ed.
> I have a running prototype.
>
> It allows to have the same edit support you have in the
> standard property view, for references and attributes.
>
> If there is someone who has a couple days time, and wants to improve
> the example, he can contact me at kutter@montages.com
>
> With a little time, this can be turned into a useful example/tutorial
> for the community. Maybe Miles, Tom, or Ron are interested.. With even
> a little more time, it could be turned into an improved editor JET which
> shows the label-feature editable in the second column.
>
> Best, Philipp
>
>
> Ed Merks wrote:
>> Tom,
>>
>> You're like an angel from heaven! O:-)
>>
>>
>> Tom Schindl wrote:
>>> Ed,
>>>
>>> Once I have time I'll try to come up with a solution :-)
>>>
>>> Tom
>>>
>>> Ed Merks schrieb:
>>>> Tom,
>>>>
>>>> We'll need to understand what we could do in EMF to exploit/enable
>>>> this. So much to do and so little time...
>>>>
>>>>
>>>> Tom Schindl wrote:
>>>>> Hi,
>>>>>
>>>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>>>> could be done much easier than with the old index-based one.
>>>>>
>>>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>>>> pair and use it in all Trees/Tables.
>>>>>
>>>>> Tom
>>>>>
>>>>> Miles Parker schrieb:
>>>>>>
>>>>>> Ed et. al.
>>>>>>
>>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>>> for some interface shared across EClasses for each of that
>>>>>> interface's properties. For example for the Ecore meta-model
>>>>>> itself you could have a column for names and annotations for all
>>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>>> imagine some way of mapping property n of each column to an
>>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>>> attempt to implement something custom, any plans to support Tree
>>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>>
>>>>>>
>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>
>>>>>>> Philipp,
>>>>>>>
>>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>>> directly supports a Tree Viewer with columns so there's no need
>>>>>>> to use a table tree. You'll need to learn about cell editors to
>>>>>>> support editing of the columns. Other than the mapping editor,
>>>>>>> which is very old, I don't have anything specific to point you
>>>>>>> at. In terms of EMF.edit support, it's a matter of making the
>>>>>>> factory's supported types include ITableItemLabelProvider and
>>>>>>> then specialize the item providers to implement getColumnText.
>>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even
>>>>>>> for a tree without columns but that's fixed in 3.3.1.)
>>>>>>>
>>>>>>>
>>>>>>> Philipp W. Kutter wrote:
>>>>>>>> Hi.
>>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>>> Columns"
>>>>>>>>
>>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>>
>>>>>>>> Has someone developed specific templates supporting this, and
>>>>>>>> is ready to share them?
>>>>>>>>
>>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>>> experiences here once I am successful in doing this.
>>>>>>>>
>>>>>>>> Best, Philipp
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Running Prototype for Tree with Columns [message #414516 is a reply to message #414507] |
Fri, 09 November 2007 23:21 |
Philipp Kutter
Messages: 306
Registered: July 2009 |
Senior Member |
|
|
Hi, Ed.
I am actually not sure whether there should be anything added/changed in
EMF itself. But if someone has time to elaborate the topic, this person
may come up with a proposal for a feature request.
I assume just adding a prototype doing in-place editing in the tree view
will not be enough to motivate the EMF team to update the generator
template. At least, someone should provide the editor JET template
showing how this is done... this could be added.
Best, Philipp
Ed Merks wrote:
> Philipp,
>
> Maybe it would be good to open bugzilla feature request and put it as an
> attachment.
>
> Note that with IUpdateableItemText it's possible to support in-place
> editing directly in the tree view.
>
>
> Philipp W. Kutter wrote:
>> Hi, Ed.
>> I have a running prototype.
>>
>> It allows to have the same edit support you have in the
>> standard property view, for references and attributes.
>>
>> If there is someone who has a couple days time, and wants to improve
>> the example, he can contact me at kutter@montages.com
>>
>> With a little time, this can be turned into a useful example/tutorial
>> for the community. Maybe Miles, Tom, or Ron are interested.. With even
>> a little more time, it could be turned into an improved editor JET which
>> shows the label-feature editable in the second column.
>>
>> Best, Philipp
>>
>>
>> Ed Merks wrote:
>>> Tom,
>>>
>>> You're like an angel from heaven! O:-)
>>>
>>>
>>> Tom Schindl wrote:
>>>> Ed,
>>>>
>>>> Once I have time I'll try to come up with a solution :-)
>>>>
>>>> Tom
>>>>
>>>> Ed Merks schrieb:
>>>>> Tom,
>>>>>
>>>>> We'll need to understand what we could do in EMF to exploit/enable
>>>>> this. So much to do and so little time...
>>>>>
>>>>>
>>>>> Tom Schindl wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>>>>> could be done much easier than with the old index-based one.
>>>>>>
>>>>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>>>>> pair and use it in all Trees/Tables.
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>> Miles Parker schrieb:
>>>>>>>
>>>>>>> Ed et. al.
>>>>>>>
>>>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>>>> for some interface shared across EClasses for each of that
>>>>>>> interface's properties. For example for the Ecore meta-model
>>>>>>> itself you could have a column for names and annotations for all
>>>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>>>> imagine some way of mapping property n of each column to an
>>>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>>>> attempt to implement something custom, any plans to support Tree
>>>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>>>
>>>>>>>
>>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>>
>>>>>>>> Philipp,
>>>>>>>>
>>>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>>>> directly supports a Tree Viewer with columns so there's no need
>>>>>>>> to use a table tree. You'll need to learn about cell editors to
>>>>>>>> support editing of the columns. Other than the mapping editor,
>>>>>>>> which is very old, I don't have anything specific to point you
>>>>>>>> at. In terms of EMF.edit support, it's a matter of making the
>>>>>>>> factory's supported types include ITableItemLabelProvider and
>>>>>>>> then specialize the item providers to implement getColumnText.
>>>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even
>>>>>>>> for a tree without columns but that's fixed in 3.3.1.)
>>>>>>>>
>>>>>>>>
>>>>>>>> Philipp W. Kutter wrote:
>>>>>>>>> Hi.
>>>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>>>> Columns"
>>>>>>>>>
>>>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>>>
>>>>>>>>> Has someone developed specific templates supporting this, and
>>>>>>>>> is ready to share them?
>>>>>>>>>
>>>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>>>> experiences here once I am successful in doing this.
>>>>>>>>>
>>>>>>>>> Best, Philipp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
|
|
|
| Re: Running Prototype for Tree with Columns [message #414518 is a reply to message #414516] |
Sat, 10 November 2007 13:17 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Philipp,
It sounds like this would make another good EMF Recipe then:
http://wiki.eclipse.org/EMF/Recipes
Philipp W. Kutter wrote:
> Hi, Ed.
> I am actually not sure whether there should be anything added/changed
> in EMF itself. But if someone has time to elaborate the topic, this
> person may come up with a proposal for a feature request.
>
> I assume just adding a prototype doing in-place editing in the tree view
> will not be enough to motivate the EMF team to update the generator
> template. At least, someone should provide the editor JET template
> showing how this is done... this could be added.
>
> Best, Philipp
>
>
>
> Ed Merks wrote:
>> Philipp,
>>
>> Maybe it would be good to open bugzilla feature request and put it as
>> an attachment.
>>
>> Note that with IUpdateableItemText it's possible to support in-place
>> editing directly in the tree view.
>>
>>
>> Philipp W. Kutter wrote:
>>> Hi, Ed.
>>> I have a running prototype.
>>>
>>> It allows to have the same edit support you have in the
>>> standard property view, for references and attributes.
>>>
>>> If there is someone who has a couple days time, and wants to improve
>>> the example, he can contact me at kutter@montages.com
>>>
>>> With a little time, this can be turned into a useful
>>> example/tutorial for the community. Maybe Miles, Tom, or Ron are
>>> interested.. With even
>>> a little more time, it could be turned into an improved editor JET
>>> which
>>> shows the label-feature editable in the second column.
>>>
>>> Best, Philipp
>>>
>>>
>>> Ed Merks wrote:
>>>> Tom,
>>>>
>>>> You're like an angel from heaven! O:-)
>>>>
>>>>
>>>> Tom Schindl wrote:
>>>>> Ed,
>>>>>
>>>>> Once I have time I'll try to come up with a solution :-)
>>>>>
>>>>> Tom
>>>>>
>>>>> Ed Merks schrieb:
>>>>>> Tom,
>>>>>>
>>>>>> We'll need to understand what we could do in EMF to
>>>>>> exploit/enable this. So much to do and so little time...
>>>>>>
>>>>>>
>>>>>> Tom Schindl wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'd say with the new TreeViewerColumn and EditingSupport-API
>>>>>>> this could be done much easier than with the old index-based one.
>>>>>>>
>>>>>>> This way you would generate an
>>>>>>> EditingSupport/ColumnLabelProvider pair and use it in all
>>>>>>> Trees/Tables.
>>>>>>>
>>>>>>> Tom
>>>>>>>
>>>>>>> Miles Parker schrieb:
>>>>>>>>
>>>>>>>> Ed et. al.
>>>>>>>>
>>>>>>>> It seems that it would be pretty 'easy' ;) to support say
>>>>>>>> columns for some interface shared across EClasses for each of
>>>>>>>> that interface's properties. For example for the Ecore
>>>>>>>> meta-model itself you could have a column for names and
>>>>>>>> annotations for all ENamedElements -- trivial example, I know.
>>>>>>>> In general, one could imagine some way of mapping property n of
>>>>>>>> each column to an aribtrary EAttribute for a given
>>>>>>>> cooresponding EObject. Before I attempt to implement something
>>>>>>>> custom, any plans to support Tree Column's in EMF.edit or
>>>>>>>> thoughts about patterns for doing so?
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>>>
>>>>>>>>> Philipp,
>>>>>>>>>
>>>>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>>>>> directly supports a Tree Viewer with columns so there's no
>>>>>>>>> need to use a table tree. You'll need to learn about cell
>>>>>>>>> editors to support editing of the columns. Other than the
>>>>>>>>> mapping editor, which is very old, I don't have anything
>>>>>>>>> specific to point you at. In terms of EMF.edit support, it's
>>>>>>>>> a matter of making the factory's supported types include
>>>>>>>>> ITableItemLabelProvider and then specialize the item providers
>>>>>>>>> to implement getColumnText. (Eclipse 3.3.0 had a problem that
>>>>>>>>> getColumnText was used even for a tree without columns but
>>>>>>>>> that's fixed in 3.3.1.)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Philipp W. Kutter wrote:
>>>>>>>>>> Hi.
>>>>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>>>>> Columns"
>>>>>>>>>>
>>>>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>>>>
>>>>>>>>>> Has someone developed specific templates supporting this, and
>>>>>>>>>> is ready to share them?
>>>>>>>>>>
>>>>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>>>>> experiences here once I am successful in doing this.
>>>>>>>>>>
>>>>>>>>>> Best, Philipp
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Running Prototype for Tree with Columns [message #414534 is a reply to message #414504] |
Mon, 12 November 2007 01:26 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi Philipp,
I'm definately interested but given that my current time is very limited
I won't have the time look at it (or at least I don't know exactly when
I have time).
To me this sounds like a bugzilla where you add your code we can then
base the next steps on. All contributions have to made through bugzilla
because this ensures the IP-Process all committers have to follow!
To me it also have to possibility that others who might have the spirit
to work and give feedback could attach to the bug :-)
Tom
Philipp W. Kutter schrieb:
> Hi, Ed.
> I have a running prototype.
>
> It allows to have the same edit support you have in the
> standard property view, for references and attributes.
>
> If there is someone who has a couple days time, and wants to improve the
> example, he can contact me at kutter@montages.com
>
> With a little time, this can be turned into a useful example/tutorial
> for the community. Maybe Miles, Tom, or Ron are interested.. With even
> a little more time, it could be turned into an improved editor JET which
> shows the label-feature editable in the second column.
>
> Best, Philipp
>
>
> Ed Merks wrote:
>> Tom,
>>
>> You're like an angel from heaven! O:-)
>>
>>
>> Tom Schindl wrote:
>>> Ed,
>>>
>>> Once I have time I'll try to come up with a solution :-)
>>>
>>> Tom
>>>
>>> Ed Merks schrieb:
>>>> Tom,
>>>>
>>>> We'll need to understand what we could do in EMF to exploit/enable
>>>> this. So much to do and so little time...
>>>>
>>>>
>>>> Tom Schindl wrote:
>>>>> Hi,
>>>>>
>>>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>>>> could be done much easier than with the old index-based one.
>>>>>
>>>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>>>> pair and use it in all Trees/Tables.
>>>>>
>>>>> Tom
>>>>>
>>>>> Miles Parker schrieb:
>>>>>>
>>>>>> Ed et. al.
>>>>>>
>>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>>> for some interface shared across EClasses for each of that
>>>>>> interface's properties. For example for the Ecore meta-model
>>>>>> itself you could have a column for names and annotations for all
>>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>>> imagine some way of mapping property n of each column to an
>>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>>> attempt to implement something custom, any plans to support Tree
>>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>>
>>>>>>
>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>
>>>>>>> Philipp,
>>>>>>>
>>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>>> directly supports a Tree Viewer with columns so there's no need
>>>>>>> to use a table tree. You'll need to learn about cell editors to
>>>>>>> support editing of the columns. Other than the mapping editor,
>>>>>>> which is very old, I don't have anything specific to point you
>>>>>>> at. In terms of EMF.edit support, it's a matter of making the
>>>>>>> factory's supported types include ITableItemLabelProvider and
>>>>>>> then specialize the item providers to implement getColumnText.
>>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even for
>>>>>>> a tree without columns but that's fixed in 3.3.1.)
>>>>>>>
>>>>>>>
>>>>>>> Philipp W. Kutter wrote:
>>>>>>>> Hi.
>>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>>> Columns"
>>>>>>>>
>>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>>
>>>>>>>> Has someone developed specific templates supporting this, and is
>>>>>>>> ready to share them?
>>>>>>>>
>>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>>> experiences here once I am successful in doing this.
>>>>>>>>
>>>>>>>> Best, Philipp
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
|
| Re: Running Prototype for Tree with Columns [message #414558 is a reply to message #414504] |
Tue, 13 November 2007 03:17 |
Ron Bermejo
Messages: 30
Registered: July 2009 |
Member |
|
|
Philipp W. Kutter wrote:
> Hi, Ed.
> I have a running prototype.
> It allows to have the same edit support you have in the
> standard property view, for references and attributes.
> If there is someone who has a couple days time, and wants to improve the
> example, he can contact me at kutter@montages.com
> With a little time, this can be turned into a useful example/tutorial
> for the community. Maybe Miles, Tom, or Ron are interested.. With even
> a little more time, it could be turned into an improved editor JET which
> shows the label-feature editable in the second column.
> Best, Philipp
Hello Philipp!
I am interested in your example...
I think we implemented the same thing :-)
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=207324)
I am also currently interested in the developments in this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=75625
plus this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=144260
equals a tree/table editor for EMF objects that uses databinding!
-Ron
|
|
|
| Re: Running Prototype for Tree with Columns [message #414959 is a reply to message #414558] |
Mon, 26 November 2007 15:28 |
Philipp Kutter
Messages: 306
Registered: July 2009 |
Senior Member |
|
|
Hi, Ron.
I'll forward your feature request to our developer.
He will then see whether his classes can be combined with
what you already submitted.
Best, Philipp
Ron Bermejo wrote:
> Philipp W. Kutter wrote:
>
>> Hi, Ed.
>> I have a running prototype.
>
>> It allows to have the same edit support you have in the
>> standard property view, for references and attributes.
>
>> If there is someone who has a couple days time, and wants to improve
>> the example, he can contact me at kutter@montages.com
>
>> With a little time, this can be turned into a useful example/tutorial
>> for the community. Maybe Miles, Tom, or Ron are interested.. With even
>> a little more time, it could be turned into an improved editor JET which
>> shows the label-feature editable in the second column.
>
>> Best, Philipp
>
> Hello Philipp!
>
> I am interested in your example...
> I think we implemented the same thing :-)
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=207324)
>
> I am also currently interested in the developments in this bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=75625
> plus this bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=144260
> equals a tree/table editor for EMF objects that uses databinding!
>
> -Ron
>
>
|
|
|
| Re: Running Prototype for Tree with Columns [message #414960 is a reply to message #414534] |
Mon, 26 November 2007 15:34 |
Philipp Kutter
Messages: 306
Registered: July 2009 |
Senior Member |
|
|
Hi, Tom.
My developer will see how his classes fit with what Ron added in his
bug. He basically did two classes, which allow to have the normal EMF
editing stuff apearing in the columns of the tree editor.
Best, Philipp
Tom Schindl wrote:
> Hi Philipp,
>
> I'm definately interested but given that my current time is very limited
> I won't have the time look at it (or at least I don't know exactly when
> I have time).
>
> To me this sounds like a bugzilla where you add your code we can then
> base the next steps on. All contributions have to made through bugzilla
> because this ensures the IP-Process all committers have to follow!
>
> To me it also have to possibility that others who might have the spirit
> to work and give feedback could attach to the bug :-)
>
> Tom
>
> Philipp W. Kutter schrieb:
>> Hi, Ed.
>> I have a running prototype.
>>
>> It allows to have the same edit support you have in the
>> standard property view, for references and attributes.
>>
>> If there is someone who has a couple days time, and wants to improve
>> the example, he can contact me at kutter@montages.com
>>
>> With a little time, this can be turned into a useful example/tutorial
>> for the community. Maybe Miles, Tom, or Ron are interested.. With even
>> a little more time, it could be turned into an improved editor JET which
>> shows the label-feature editable in the second column.
>>
>> Best, Philipp
>>
>>
>> Ed Merks wrote:
>>> Tom,
>>>
>>> You're like an angel from heaven! O:-)
>>>
>>>
>>> Tom Schindl wrote:
>>>> Ed,
>>>>
>>>> Once I have time I'll try to come up with a solution :-)
>>>>
>>>> Tom
>>>>
>>>> Ed Merks schrieb:
>>>>> Tom,
>>>>>
>>>>> We'll need to understand what we could do in EMF to exploit/enable
>>>>> this. So much to do and so little time...
>>>>>
>>>>>
>>>>> Tom Schindl wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I'd say with the new TreeViewerColumn and EditingSupport-API this
>>>>>> could be done much easier than with the old index-based one.
>>>>>>
>>>>>> This way you would generate an EditingSupport/ColumnLabelProvider
>>>>>> pair and use it in all Trees/Tables.
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>> Miles Parker schrieb:
>>>>>>>
>>>>>>> Ed et. al.
>>>>>>>
>>>>>>> It seems that it would be pretty 'easy' ;) to support say columns
>>>>>>> for some interface shared across EClasses for each of that
>>>>>>> interface's properties. For example for the Ecore meta-model
>>>>>>> itself you could have a column for names and annotations for all
>>>>>>> ENamedElements -- trivial example, I know. In general, one could
>>>>>>> imagine some way of mapping property n of each column to an
>>>>>>> aribtrary EAttribute for a given cooresponding EObject. Before I
>>>>>>> attempt to implement something custom, any plans to support Tree
>>>>>>> Column's in EMF.edit or thoughts about patterns for doing so?
>>>>>>>
>>>>>>>
>>>>>>> On 2007-10-02 07:27:25 -0400, Ed Merks <merks@ca.ibm.com> said:
>>>>>>>
>>>>>>>> Philipp,
>>>>>>>>
>>>>>>>> The MappingEditor has some fancier examples. Eclipse now
>>>>>>>> directly supports a Tree Viewer with columns so there's no need
>>>>>>>> to use a table tree. You'll need to learn about cell editors to
>>>>>>>> support editing of the columns. Other than the mapping editor,
>>>>>>>> which is very old, I don't have anything specific to point you
>>>>>>>> at. In terms of EMF.edit support, it's a matter of making the
>>>>>>>> factory's supported types include ITableItemLabelProvider and
>>>>>>>> then specialize the item providers to implement getColumnText.
>>>>>>>> (Eclipse 3.3.0 had a problem that getColumnText was used even
>>>>>>>> for a tree without columns but that's fixed in 3.3.1.)
>>>>>>>>
>>>>>>>>
>>>>>>>> Philipp W. Kutter wrote:
>>>>>>>>> Hi.
>>>>>>>>> There is a version of the generated Editor, named "Tree with
>>>>>>>>> Columns"
>>>>>>>>>
>>>>>>>>> Is there a tutorial or example how to add more columns, and
>>>>>>>>> especially how to make fields editable directly in the columns?
>>>>>>>>>
>>>>>>>>> Has someone developed specific templates supporting this, and
>>>>>>>>> is ready to share them?
>>>>>>>>>
>>>>>>>>> Any input or experience is welcome. I will post my own
>>>>>>>>> experiences here once I am successful in doing this.
>>>>>>>>>
>>>>>>>>> Best, Philipp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 00:07:46 GMT 2024
Powered by FUDForum. Page generated in 0.12543 seconds |
] 
Search
Help
Register
Login
Home
