Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343776 - Support element property in the master details content outline
Summary: Support element property in the master details content outline
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2011-04-25 17:56 EDT by Ling Hao CLA
Modified: 2021-11-19 09:22 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ling Hao CLA 2011-04-25 17:56:07 EDT 
An example would be the contacts.xml sample -> primary occupation. It would be nice to create the occupation in the outline view (similar to adding contact to the contacts node)
Comment 1 Konstantin Komissarchik CLA 2011-04-27 01:09:50 EDT 
Enhancement implemented. Added example to the gallery sample and sections to what's new and migration docs.
Comment 2 Konstantin Komissarchik CLA 2011-04-27 01:09:59 EDT 
Please verify.
Comment 3 Ling Hao CLA 2011-04-27 15:45:56 EDT 
In my case I have 11 different occupations. And each occupation there may be various number (zero, one or more) of child nodes. It would be a lot easier for my test case if each <node-factory> is for <property> and <model-element-type> pair. Or at the minimum, there should be an option to not show the node for a model-element-type.
Comment 4 Konstantin Komissarchik CLA 2011-04-27 17:20:28 EDT 
> In my case I have 11 different occupations. And each occupation there may be
> various number (zero, one or more) of child nodes. It would be a lot easier for
> my test case if each <node-factory> is for <property> and <model-element-type>
> pair. Or at the minimum, there should be an option to not show the node for a
> model-element-type.

I do not comprehend the above statements. The semantics are identical to how lists are handled. I am not sure what you are trying to achieve.
Comment 5 Ling Hao CLA 2011-04-27 18:15:55 EDT 
Now I've got it! Works great, thanks!