Two (or more) weeks ahead view

[xhoy]

Hi,

Today i was using my datepicker as i do daily for various applications. But since it is the 29th of the month it was really annoyed that I needed to select the 'next' month every time I needed a date that was not in this month.

So I looked a bit around and the only solution seems to be to add a 2 months view… Since that isn’t always desirable I thought why wouldn’t it be possible to show the ‘next’ 2/3/4 weeks? There are several problems to this, for example, what month are you looking at? (when there is just a simple list) The ‘next’ and ‘prev’ button where should they go?

Solution 1: The most logical solution I could think of at this moment would be that dates in the ‘next month’ (or the previous month) could be ‘greyed’ out but selectable.

Something like this [[Image(​http://unifaceinfo.com/wp-content/uploads/2013/03/u96_datepicker_screen.png )]] Solution 2: This option is would make the date picker more flexible, it list 4/5 weeks without thinking about the month’s and when you select a date the interface around the calendar would change to that week When you select a date in another month the prev/next button would be update with the selected date as centre, the view wouldn’t change except ofcourse the ‘current’ listed month. Next/prev would still move you one week up/down.

Don’t know if this is the right location but maby some of you could think about it :)

[Scott González]

​http://jqueryui.com/datepicker/#other-months

[xhoy]

Hi Scott,

I know that option, but what if you don’t want to show 2 full months?

And why wouldn't date picker act the same way as the MS clock calendar works? When you click a date in another month, the hole calendar shifts to that month.

Maby I should rephrase my report: I think the current interaction with prev/next isn't optimal and could be improved. As told above there are several options for this.

My biggest problem with the current date picker that I always get annoyed when it’s almost at the end of the month :)

[Scott González]

You said:

Solution 1: The most logical solution I could think of at this moment would be that dates in the ‘next month’ (or the previous month) could be ‘greyed’ out but selectable

...and provided ​this screenshot.

As far as I can tell, that demo is exactly what you requested.

[xhoy]

Sorry I see I wasn’t clear on that.

I think it should show at least one or two weeks ahead of current date. When that passes the current month, there should be added an additional row with an extra weeks.

The current Date picker is based on “months”. There are cases where ‘months’ isn’t the main interval but for example it could be ‘weeks’. Forexample our case, we use OTRS (ticketing system), when we called a customer we set that ticket to ‘pending’ for one week. The current jQuery date picker interface doesn’t really provide this. And at the end of the month we get annoyed buy always needing to click the ‘next’ button. The rest of the month, this isn’t a problem since in 1 click we have the full month.

Basically what I wonder is Why can’t it just show 2 weeks ahead? why does it always need to be a full month interval?

At the end of the month we need to clicks instead of one, this can be fixed and maybe should!

Thanks for the feedback. These are just some thoughts of a lost user :)

[Scott González]

Because that's how calendars work? I'm not really inclined to add support for a feature that is pretty rare. Feel free to investigate what would need to be done in the ​rewrite to make it possible for you to implement this as an extension.

[xhoy]

This isn't fully want i mean but it is a lot belter then the current date picker

As you see, there is an additional row with dates (september 2-8)

And when i click on (for example 6) i get:

It changes the context of the hole calendar to september 2013.

[Scott González]

So it takes you exactly the same number of clicks as using the existing navigation. Again, I don't think we'll be implementing this, but look into what it would take to make an extension.

[tj.vantoll]

Just as an fyi, this is very similar to #7210, which is an open feature request.