Great!
One easy way to get started might be to create a "skin" that users
can install that sets Chandler up with a GTD template of example
collections and items.
For example, you could do things like:
+ Create "GTD Context" Collections - Calls, Agendas, Errands, Home,
Office, etc
- For the Agendas Collection, you could go one step further and
create some example items that demonstrate how people can best
leverage Chandler to keep track of Agendas.
- For example, Katie has come up with a cool way to keep track of the
many 1:1 meetings she has with people by creating a weekly, recurring
event series for each person. It sort of doesn't matter when she
meets with each person, but each week, she jots down what she needs
to talk to that person about on that week's occurrence. Because it's
an event, she can use the calendar as a way of finding agenda notes
when she needs to review them, but she can also manage them from the
List View like tasks.
+ Create a GTD Projects Collection
Repurpose the Dashboard to be a GTD Collection Box.
+ Rename the Dashboard collection --> Collect
+ Change the rules governing the Dashboard collection to allow users
to remove individual items from the Dashboard (otherwise, your
Collection Box can never get to zero!) - https://
bugzilla.osafoundation.org/show_bug.cgi?id=7599
+ It might also be useful if the "Collect" collection automatically
picked up new items that other people have added to shared collections
+ Repurpose the "Needs Reply" status to be "Waiting for" instead.
("Needs Reply" is the 3rd option when cycling through Read/Unread
status in the List View)
- Note: There are some kinks to work out here.
+ Add a "Next Action" field to the Item Details where users can
create a new item. (Basically, you'd be putting a 2nd quick-entry
field inside the Detail View.) Ideally, the item you create would
persist as a linked item in the Detail View, but this might
challenging to implement today.
Is this along the lines of what you were thinking?
Mimi
On Mar 25, 2008, at 11:48 AM, Marcelo de Moraes Serpa wrote:
Hi Mimi, thanks for replying.
Yes, currently I could use a hand on designing this thing :)
Thanks.
On Tue, Mar 25, 2008 at 3:38 PM, Mimi Yin <[EMAIL PROTECTED]>
wrote:
Hi Marcelo,
I started writing a reply and then realized I wasn't sure exactly
what kind of help you're looking for. Would you like suggestions for
product design? or help with technical design issues?
I can help you with the former and Grant will respond if it's the
latter.
Also, it would help Grant and/or I, if you could come up with some
specific questions you'd like answers to.
Mimi
On Mar 24, 2008, at 11:04 AM, Marcelo de Moraes Serpa wrote:
> Hello folks,
>
> I'm willing to start developing a full-fledged GTD plugin for
> Chandler. The objective is to formalize many (if not all) of the
> concepts so as to make Chandler aware of them and make it easier
> (straightforward) to implement the Getting Things Done methodology
> in Chandler. I think Chandler can turn to be the "perfect" platform
> for GTD.
>
> However, I'm not sure where to start. Ok, I know, the plug-in
> architecture documentation - but that's not what I'm talking about
> actually. I would like suggestions on how I could do it while
> maintaining much of the current Chandler desktop infra-structure
> (not reinventing the wheel) - I think I'm really asking for design
> suggestions.
>
> I might be writing a document later to help me shape the "product",
> for now, if anyone could help me with suggestion, I would be
grateful.
>
> Marcelo.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
