Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343776

Summary:	Support element property in the master details content outline
Product:	z_Archived	Reporter:	Ling Hao <ling.hao>
Component:	Sapphire	Assignee:	Konstantin Komissarchik <konstantin>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	konstantin
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Ling Hao

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

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

2011-04-27 01:09:59 EDT

Please verify.

Comment 3 Ling Hao

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

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

2011-04-27 18:15:55 EDT

Now I've got it! Works great, thanks!