Start and Due Dates for Tasks

[bensinep]

Okay, I used Agendus for quite awhile on Palm OS before switching to WM5 and an iPaq 6955. I think its great that we can finally have Agendus on WM but there's a few areas that I'd like to see the program take advantage of. One of those is:

I know on the Palm, the advance function for tasks was great because, as I recall, the PalmOS had no field in a task record for the start date of the task. Well, WM does have a start date and a due date and that is what I've been using and it seems to work quite well. Could you maybe modify Agendus so that the advance feature actually sets the start date rather than putting a code in a note? I don't mind the notes codes being used when there is no equivalent field that can be used but I don't think that's the case here. It would also make it play much nicer with other apps that use the built in PIM database (PocketBreeze etc.).

Still great to finally have Agendus again.

-Bill

[casapel]

I know on the Palm, the advance function for tasks was great because, as I recall, the PalmOS had no field in a task record for the start date of the task. Correct.

I'm guessing Agendus for Windows has an advance field to keep it in line with users synchronizing with Palms, and so AGWM has it to keep it consistent with the desktop application.

Could you maybe modify Agendus so that the advance feature actually sets the start date rather than putting a code in a note?I like your idea. I think it would be great if Agendus for Palm OS's advance feature worked this way as well (maybe developers could add a Start Date field to AGP).

[casapel]

I want to make sure I understood you. Is the following what you had in mind by “modify Agendus so that the advance feature actually sets the start date”?

When enabled, instead of tasks appearing in a view based on a #-of-days-before Advance setting, tasks appear based on their Start Date. The Start Date picker would include typical date picking options (eg. Calendar style) as well as current Advance feature options, eg. 1 day before, 2 days before, etc.

[bensinep]

Yes, that's what I'm talking about. In fact, I like the concept of the Advance feature and even if you want to keep the UI the same that's fine. I just think it should store the info in the Start Date field so any other applications have access to it.

So, if you set a task due on Feb 28 with a 4 day advance, it would actually store Feb 24 in the Start Date field. Of course, having both options like you describe below would be even better!

[hezahonker]

Yes, that's what I'm talking about. In fact, I like the concept of the Advance feature and even if you want to keep the UI the same that's fine. I just think it should store the info in the Start Date field so any other applications have access to it.

So, if you set a task due on Feb 28 with a 4 day advance, it would actually store Feb 24 in the Start Date field. Of course, having both options like you describe below would be even better!

Bill,

I really like your idea. Thanks for suggesting. Seems really efficient. I don't know what is involved on the development side. I am not the developer but it seems like this should work if implemented. I am a pocketbreeze user so I have a good appreciation for this. Especially since I was the one that asked Amit at SBSH to implement the timed task feature in PB.:) :up: