| Summary | Default time for new events should be ceil(current time) |
| Queue | Kronolith |
| Queue Version | 2.0.2 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | kevin_myer (at) iu13 (dot) org |
| Created | 04/11/2005 (7452 days ago) |
| Due | |
| Updated | 04/03/2006 (7095 days ago) |
| Assigned | 04/16/2005 (7447 days ago) |
| Resolved | 04/03/2006 (7095 days ago) |
| Milestone | |
| Patch | No |
me to always have the same time preselected.
State ⇒ Feedback
State ⇒ Accepted
"Defaulting to the current time" is a way of defaulting to the same
thing. So a preference would work fine - either current time, or
day_start_hour. I'm trying to think of situations outside the scope
of what we'd use that for and I'm not sure what else would be
reasonable values - maybe next available time slot in the current day
as a third option (but then you'd have to invoke a FB call to
determine that time which might kill performance).
And just to be a devil's advocate, just because Palm and MIcrosoft do
things one way, doesn't mean you can't innovate (although most of the
time, they've got it right - something about having a vast marketshare
that helps drive that home :)
both Palm Desktop and Outlook. All 3 agree: the start time should
always default to the same thing unless you clicked an hour-specific
link.
So I'm disinclined to change that. I'm open to making it a user
preference, though, and that could include "current hour" as an option.
Thoughts?
future days, just the current day. Events on future days could still
reasonably start at day_start_hour by default, or better yet, the
first available time slot greater than day_start_hour, if there's
already an event scheduled for the first part of the day.
State ⇒ Feedback
somewhat random that when creating an event on a day in the future,
that the hour defaulted to the current hour.
How about if we just avoid defaulting to a time in the past, so that
if you're creating an event *today*, the default time is now?
Assigned to Chuck Hagenbuch
State ⇒ Assigned
the rationale?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Default time for new events should be ceil(current time)
Queue ⇒ Kronolith
State ⇒ New
start time to be day_start_hour and the end time to be day_start_hour
+ 1 hour. However, it would be rare that you need to add an event for
some time in the past. I'd suggest that the start time for an event
be a ceiling function of whatever the current time is. I'm sure
there's a utiilty function in Horde to get that value, based on the
timezone setting a user has configured and then apply some sort of
ceiling function to that value.