[haiku-bugs] Re: [Haiku] #5102: Add "Not applicable" selection to Milestone, Version and Platform fields in Trac

  • From: "nielx" <trac@xxxxxxxxxxxx>
  • Date: Fri, 11 Dec 2009 18:16:11 -0000

#5102: Add "Not applicable" selection to Milestone, Version and Platform fields 
in
Trac
--------------------------+-------------------------------------------------
 Reporter:  koki          |       Owner:  nielx   
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:          
Component:  Website/Trac  |     Version:          
 Keywords:                |   Blockedby:          
 Platform:  All           |    Blocking:          
--------------------------+-------------------------------------------------
Changes (by nielx):

  * owner:  haiku-web => nielx
  * status:  new => assigned


Comment:

 Replying to [comment:5 koki]:
 > Replying to [comment:3 umccullough]:
 > > From a usability point of view, Jorge's position on this is very
 common. Users do generally feel better about selecting *something* into a
 drop down box rather than nothing.
 >
 > It is not good practice (nor is it common AFAIK) to have unlabelled
 controls in a GUI. Maybe in a drop-down menu an empty selection that is
 not visible does not strike as awkward at first glance; but move the same
 functionality to a group of radio buttons (where all selections are
 exposed), and you will see how visually awkward, unintuitive and
 potentially confusing it would be have an unlabelled/unspecified
 selection.

 Okay, I agree, but I think you're overanalyzing the problem. I think it is
 actually that people don't care to alter the default values to 'empty'
 ones.

 > Replying to [comment:4 axeld]:
 > > I don't mind relabeling the empty entry, I just wouldn't like to have
 extra entries for "N/A".
 >
 > Relabeling the entry (to N/A, None or the like) would work IMHO.

 I will try another approach:

 I am going to write a short script that changes the Version, Milestone and
 Platform field to an empty one, and that disables the fields when the
 component Website is selected. I think that would most effectively solve
 the problem. Any thoughts?

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5102#comment:6>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts:

  1. Home
  2. haiku-bugs
  3. Archive
  4. 12-2009