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

Bug 346267

Summary:	Allow generator property page to display option to override parent settings
Product:	z_Archived	Reporter:	Justin Spadea <jspadea>
Component:	EDT	Assignee:	Justin Spadea <jspadea>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	alicec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Justin Spadea

2011-05-18 10:52:15 EDT

At the project level, would display a blurb about overriding defaults from preferences:

[  ] Override settings inherited from preferences

At the folder/file level, would display a blurb about overriding inherited settings. Should display what the inherited values are, as well as the resource they come from. Optional: provide a link to the resource providing inherited settings:

[  ] Override settings inherited from /myProject/EGLSource/foo


When unchecked, the inherited settings are displayed but the widgets are disabled. Check the box and they're enabled and blank

Comment 1 Justin Spadea

2011-05-27 11:58:07 EDT

The look of the property page has changed since this task was originally opened. A different approach would probably be better.

Instead of having the checkbox in the generator settings tabs, should there be a single checkbox for overriding all generator settings? Right now users have no clue if the settings for a resource are inherited from a parent resource, or if those settings really are for the current resource. This applies to the enabled generators as well as the enabled generators' settings tabs.

The checkbox would probably go above the generator tree. When unchecked the tree and the tabs would be disabled, when checked the tree and tabs would be enabled. The checkbox label should indicate which resource is being overridden. This lets you say "for this resource and all its kids, use this different set of generators, and/or use these different settings for the enabled generators".

For clarity, a resource's settings can come from anywhere in the resource heirarchy: for a file "/myProject/eglsource/pkg/foo.egl" we first check foo.egl for the setting, then if it's not found we check pkg, then eglsource, then myProject, and finally the workspace default.

If "eglsource" were to specify generator settings, and "pkg" did not, then "foo.egl" would display a label on the checkbox as "Override generator settings inherited from /myProject/eglsource". It would be clear to the user exactly where the settings are coming from.

Comment 2 Justin Spadea

2011-07-08 11:06:46 EDT

Part of multi-bug fix, files affected may include:

GenerationSettingsComposite
CompilerAndGeneratorControls
CompilerPropertyAndPreferencePage
PropertyAndPreferencePage
ProjectSettingsUtility
plugin.xml from edt.ide.ui

Comment 3 Justin Spadea

2011-09-07 15:53:39 EDT

Verified