[kwlug-disc] Android / Google calendar - events as tasks.

[Nickle, Brian]

Opps missed the disclaimer regarding Google tasks
On 2012-10-01 8:20 PM, "Nickle, Brian" <brian at nickle.ca> wrote:

> Gmail has tasks.  Google tasks are not perfect but they work well enough
> for Light use.
>
> Brian
> On 2012-10-01 6:01 PM, "unsolicited" <unsolicited at swiz.ca> wrote:
>
>> One of the annoying things about (Google) calendar is that it has no
>> sense of tasks as events (or vice versa). [Never mind google tasks for the
>> purpose of this message.]
>>
>> It just occurred to me I could create two calendars, 'mycal' (shown) and
>> 'mycal-done' (not shown). When a meeting has happened, for example, moving
>> the event from 'mycal' to 'mycal-done' would be the equivalent to marking
>> the meeting as completed. (Or cancelled.) Turning the display of
>> 'mycal-done' on/off would be the equivalent to ticking (or not) 'Show
>> Completed'.
>>
>> It also occurs to me that if one has a regular 'project' [never mind that
>> by definition a project is unique], one could export the (calendar) project
>> as a .csv, edit the dates for the next round, and import the modified .csv.
>>
>> [<tongue in cheek> Should I be looking to apply for a software patent for
>> these ideas?]
>>
>> Any reasons why approaching these these ways doesn't make sense / are
>> there better ways?
>>
>> Anyone know of any good web places where such tips and 'tricks' are
>> bandied about?
>>
>> [It appears to be pointless to hold one's breath that google will ever
>> add the concept of 'complete' to calendar events / integrate tasks into
>> calendar - a la Palm Desktop / Agendus / DateBk.]
>>
>> ______________________________**_________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/**listinfo/kwlug-disc_kwlug.org<http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20121001/1e0befbf/attachment.htm>