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 35695 - Lower the reliance on Property Sheets as the main user interface concept in the
Summary: Lower the reliance on Property Sheets as the main user interface concept in the
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ tboudreau
Depends on:
Blocks: 35735
  Show dependency tree
Reported: 2003-08-21 11:21 UTC by mvinar
Modified: 2008-12-22 20:36 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description mvinar 2003-08-21 11:21:15 UTC
User problem:
The property sheet concept does not work very well
as intuitive user interface. For many parts, a
dedicated, rich UI is much more usable and intuitive.

User need:
The user needs to be able to quickly and easily
change options, or settings in the IDE.

Product requirement:
For the main portion of user interface, design and
implement custom, rich user interface that
increases the usability of those parts.
Comment 1 _ tboudreau 2003-08-24 16:23:34 UTC
This needs to be done with care - in other words, the dialogs
that replace property sheet usage need to be carefully
designed and scoped.

My reasoning:
One of the things I liked about NetBeans when I first saw
it was the fact that a common object-and-properties model
was used pervasively.  You may just think that makes me a 
geek, but hear me out:

One of the things I tremendously disliked in Delphi was 
configuring a project.  The main reason was that I did 
not do it very often, but when I wanted to, I was presented
with a huge tabbed dialog with tons of options, and I
didn't reconfigure it often enough to learn where things
were - so every time it was difficult.

Had Delphi used a property-sheet metaphor, I would have had
no problem locating what I needed.  The problem was many 
panels with different designs for similar functions.

So we need to take into consideration that, while property
sheets are less intuitive, there is only one UI to learn,
and it is learnable.  In replacing the property sheet, we
should also reduce the number of options exposed, down to
those that are truly useful.

Otherwise we will have just replaced one UI problem with
another, equally bad one.
Comment 2 Jesse Glick 2004-07-24 19:47:32 UTC
Already more specific items open for e.g. Options.