90289 - implement a better date picker (for search and filters)

Status: VERIFIED DUPLICATE of bug 92174

(MailNews Core :: Filters, defect)

Description

[(not reading, please use [e-mail] instead)]

implement a better date picker (for search and filters)

the current date picker is just a textbox.

see bug #40380 for some screen shots and some comments on what we'd need.

Comment 1

[(not reading, please use [e-mail] instead)]

I vote for the 4.x style picker.

mac and windows had similar pickers, mac was especially nice.

once hwaara has a spin control, he could do the mac picker.

[textbox for day] / [textbox for month] / [textbox for year] [<spinner>]

the basic idea is if you click the spinner, we adjust what ever text box has focus.

and, they user can quickly type in the (1/2/2001) date like so:
1 (tab to month) 2 (tab to year) 2001

I'll get a screen shot of mac. 

Comment 2

[laurel]

Attachment: mac screenshot of date picker

Comment 3

[laurel]

Attachment: screenshot (jpg)

Comment 4

[Håkan Waara]

Since the spinbuttons widget is actually a up and a down arrow, wouldn't it make
more sense to have them change the actual value inside the textboxes?

Example: The year-texfield contains 2001, if you click up and it has focus we
will change it to 2002, if you click down 2000 ...

That's how that widget works on Mac as far as I can 

Comment 5

[Håkan Waara]

... remember. (sorry)

Comment 6

[(not reading, please use [e-mail] instead)]

hwaara, that sounds right.

what I was saying about tabs was, we should do the tab order correct so that
users can quickly enter a date, using tabs.

Comment 7

[Håkan Waara]

I was working on this, but then hewitt came along and ignore this effort. I
don't like reinventing the wheel so I will duplicate this against hewitt's bug. :(

*** This bug has been marked as a duplicate of 92174 ***

Comment 8

[laurel]

FYI -- I'm leaving this in a resolved state rather than verifying as a duplicate
so that I'll be reminded to check up on progress every once in awhile.  
PLEASE DON'T MARK VERIFIED AS DUPLICATE until master problem is fixed.

Comment 9

[laurel]

Nevermind.  The master bug has been futured, and I'm afraid I don't want to have
this duplicate on my resolved list for another project timeframe+.  So I'm
marking this verified as a duplicate.