On Thu, 10 Mar 2011 21:28:44 -0500, Aryeh Gregor wrote:
On Wed, Mar 9, 2011 at 5:08 PM, Diogo Resende
drese...@thinkdigital.pt wrote:
That is perfect for 1 date scope. What if I have a meeting to
schedule in a
month (eg. March) and (according to other meeting attendees) the
meeting can
only
On Fri, Mar 11, 2011 at 5:50 AM, Diogo Resende drese...@thinkdigital.pt wrote:
On Thu, 10 Mar 2011 21:28:44 -0500, Aryeh Gregor wrote:
On Wed, Mar 9, 2011 at 5:08 PM, Diogo Resende
drese...@thinkdigital.pt wrote:
That is perfect for 1 date scope. What if I have a meeting to schedule in
a
On Wed, Mar 9, 2011 at 5:08 PM, Diogo Resende drese...@thinkdigital.pt wrote:
That is perfect for 1 date scope. What if I have a meeting to schedule in a
month (eg. March) and (according to other meeting attendees) the meeting can
only happen from 10-15, 19, 20-28 and 30. Do I have to make a
Am 09.03.2011 06:51 schrieb Jukka K. Korpela:
Jonas Sicking wrote:
I'm having a little bit hard of a time figuring out what a good UI
would look like in the general case. I.e. what should the UI look like
for
input type=date id=date name=date
value=2011-04-01 list=datelist exclusive
datalist
On Tue, 8 Mar 2011 16:51:25 -0800, Jonas Sicking wrote:
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch
wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker.
Diogo Resende:
I was thinking.. what about allowing big time spans, like: from April 1st to
June 30th? Giving that the date has - as date element separators we could
not use 1-MM1-DD1-2-MM2-DD2.
ISO 8601 specifies how to code time intervals (and durations) in several ways:
start
Christoph Päper wrote:
Diogo Resende:
I was thinking.. what about allowing big time spans, like: from
April 1st to June 30th? Giving that the date has - as date element
separators we could not use 1-MM1-DD1-2-MM2-DD2.
ISO 8601 specifies how to code time intervals (and durations) in
Am 09.03.2011 12:19 schrieb Diogo Resende:
On Tue, 8 Mar 2011 16:51:25 -0800, Jonas Sicking wrote:
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi
Jukka K. Korpela:
Christoph Päper wrote:
Diogo Resende:
I was thinking.. what about allowing big time spans,
ISO 8601 specifies how to code time intervals (and durations) … – the
separator always is
a forward slash ‘/’, replacable by a double hyphen ‘--’ if necessary.
If HTML was to
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker. Quite often, whether trying to
make dates or selling flights, there is a known set of
(non-consecutive) days that are possible, so
On Tue, 08 Mar 2011 19:46:41 +0100, Markus Ernst derer...@gmx.ch wrote:
I hope very much that this proposal will make it into the standard.
Except for date/time and color input elements, I can also imagine use
cases regarding the range element (if a part of the range is not
available).
We
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker. Quite often, whether trying to
make dates or selling
Jonas Sicking wrote:
I'm having a little bit hard of a time figuring out what a good UI
would look like in the general case. I.e. what should the UI look like
for
input type=date id=date name=date
value=2011-04-01 list=datelist exclusive
datalist id=datelist
option value=2011-04-01 label=April
13 matches
Mail list logo
