[dev] [commits] Horde branch master updated. 16dc216eb1fddd04b94a83528723296508ef5ab6

[mrubinsk at horde.org]

Quoting Jan Schneider <jan at horde.org>>
> Zitat von mrubinsk at horde.org:
>
>>> commit 16dc216eb1fddd04b94a83528723296508ef5ab6
>>> Author: Jan Schneider <jan at horde.org>
>>> Date:   Tue Sep 4 14:40:15 2012 +0200
>>>
>>>   "Save As New"?
>>>
>>> nag/lib/Form/Task.php |    2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> http://git.horde.org/horde-git/-/commit/16dc216eb1fddd04b94a83528723296508ef5ab6
>>>
>>>
>>> --
>>> commits mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: commits-unsubscribe at lists.horde.org
>>>
>>
>> This is indeed supposed to be "Save And New".  Chuck's (?) original  
>> ticket was about having an additional save option that would save  
>> the new ticket then go back to the Add Task form (instead of back  
>> to the list view). Maybe better represented by  checkbox?
>
> Ah, like the hermes time entry form? That was really unintuitive then.
>
> Is this also going to keep the submitted information like in hermes?  
> If not, it doesn't make much sense anyway, and we should drop this  
> instead.
> -- 
> Jan Schneider
> The Horde Project
> http://www.horde.org/
>
> -- 
> dev mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>

Sort of like Hermes, yeah. We don't keep the existing info though; I  
don't think that makes sense for tasks except for maybe the parent  
task attribute. I still think its useful though for people adding  
multiple tasks at once. It can be fairly annoying to be shot back to  
the task list each time.

On an unrelated note it looks like I still need to tweak the email  
reply logic for active sync :)

mike


Jan Schneider <jan at horde.org> wrote: