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

Bug 84170

Summary:	[ViewMgmt] View API/implementation are in opposition
Product:	[Eclipse Project] Platform	Reporter:	Kim Horne <eclipse>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	dirk_baeumer, heinrich_soebke, martin.skorsky, pwebster
Version:	3.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Kim Horne

2005-02-01 14:08:03 EST

The view schema and the view implementation are at odds.  The schema says that
view categories may have parent categories.  Views may be defined to live in a
category based on path structure.  This is no the case.  Despite
IViewDescriptor.getCategoryPath() returning an array of segments only the first
one is ever used for determining the category that the view actually lives in. 
Additionally, the ViewContentProvider(for the view dialog) shows all Categories
in a flat structure.

Either the implementation is lying or the schema is lying.  :)

Comment 1 Nick Edgar

2005-02-03 12:34:07 EST

I don't see any reason why we should not support arbitrary nesting of categories.
But even if we do, the parent category of a view (or of a category) should just
be a single category id, not a path.

Comment 2 Nick Edgar

2005-02-03 12:42:21 EST

The wizards extension point has the same problem.
For example, org.eclipse.jdt.junit's plugin.xml has:

   <extension
         point="org.eclipse.ui.newWizards">
      <category
            name="%WizardCategory.name"
            parentCategory="org.eclipse.jdt.ui.java"
            id="org.eclipse.jdt.junit">
      </category>
      <wizard
            name="%TestCaseWizard.name"
            icon="icons/full/etool16/new_testcase.gif"
            category="org.eclipse.jdt.ui.java/org.eclipse.jdt.junit"
            id="org.eclipse.jdt.junit.wizards.NewTestCaseCreationWizard">
...
      </wizard>

The wizard should not have to specify the full path, which is duplicating the
parent path specified by the junit category.  It should suffice to just say:
      <wizard
            category="org.eclipse.jdt.junit"
...
      </wizard>

Comment 3 Dirk Baeumer

2005-02-03 13:14:39 EST

This seems to be the same as for action sets and menus.

Inside the org.eclipse.ui.newWizards you can define more than one category so
the wizard as to reference it categroy by a fully qualified name

Comment 4 Nick Edgar

2005-02-03 13:22:12 EST

Yes, the category id needs to be fully qualified, but it should suffice to
specify just the parent category id, not the full path to the category from the top.
We should not allow multiple categories with the same id, and a given category
has only a single parent chain, so the id by itself is unambiguous.

Comment 5 Nick Edgar

2006-03-15 13:28:03 EST

Reassigning bugs in component areas that are changing ownership.

Comment 6 Boris Bokowski

2009-11-11 17:32:46 EST

Remy is now responsible for watching the [ViewMgmt] category.

Comment 7 Eclipse Webmaster

2019-09-06 16:17:20 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 8 Eclipse Genie

2021-09-16 20:06:51 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.