This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 105137

Summary:	Libraries related nodes should be next to each other
Product:	obsolete	Reporter:	Ondrej Langr <olangr>
Component:	visualweb	Assignee:	_ potingwu <potingwu>
Status:	RESOLVED WONTFIX
Severity:	blocker	CC:	jrojcek
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	TASK	Exception Reporter:
Bug Depends on:
Bug Blocks:	93821
Attachments:	Theme UISpec

Description Ondrej Langr 2007-05-30 14:03:55 UTC

Noded in project view should be ordered so that all nodes related to libraries,
i.e. Libraries, Test Libraries and Component Libraries are one after another.
current ordering:
-----------------
...
Libraries
Test Libraries
Themes
Component Libraries
...

suggested ordering:
-------------------
... 
Libraries
Test Libraries
Component Libraries
Themes
...

Comment 1 _ potingwu 2007-06-05 03:22:35 UTC

Themes is actually also a library type. This arrangement is under HIE's design
and follows Creator's preferred order.

Comment 2 Ondrej Langr 2007-06-14 14:58:53 UTC

Shouldn't they be called 'Theme Libraries' then, for consistency? 

The theme node looks and behaves differently so the user may not know they are implemented as libraries. Wouldn't it be
really better to keep the name and move them below 'Component Libraries' node? Is there a spec. for this Creator's
preffered order or is it just how it has been in Creator?

Comment 3 _ krystyna 2007-06-14 18:15:06 UTC

FYI - attaching original theme spec from Creator 2 (2005)

Comment 4 _ krystyna 2007-06-14 18:16:23 UTC

Created attachment 43730 [details]
Theme UISpec

Comment 5 Ondrej Langr 2007-06-14 19:06:51 UTC

Thanks for the spec. However, it doesn't say anything about the 'Themes' node position.
Just as we have "Source Packages" and "Test Packages" one after another, we should have all "Libraries" nodes grouped
together. 

Themes is implemented as library, but it is not clear from the name. Imagine the user is looking for component libraries
.. get's caught by Libraries node .. goes on, sees 'Test Libraries' then 'Themes'. "OK, .. I passed the libraries
section, so there are no more libraries" .. could be his/her reasoning. Thinking whether Themes are still libraries or
not is a flow-stopper in this case. You may subject that user will simply continue through the list until they will find
the right node. But do we really want to force the user to get used to scanning the list of 10 items?

Please consider reopening the issue, quick navigation in project nodes is IMHO of a big importance and is visible most
of the time.