Hi dmic ... The way you and I work is a lot alike. The way I consider this "PIM" is that you would use Final Version as just one piece of it. Thus, the Ticklers could theoretically be considered as outside Final Version (FV), but inside the PIM. The same goes for the Inbox. I hope to have the Inbox finished this weekend (or Monday at the latest since I have Monday off). The way I see it working is that there will be an option as to whether you want to use an Inbox or not. If you do, just to the left of the "Next " button will be another button labeled Inbox. For right now, if you want to use Inboxes, this button will be checked until you check "Next" or give it a Tickler date or "Waiting For" or "Future, etc. In other words, each item in that row is mutually exclusive with all other items in that row. Exactly one of them is always checked. That's what I've been envisioning and it sounds like it will perfectly for you. Am I correct? Oh, and one other thing, I think I want ticklers that become due to automatically become Actions in the Inbox. I would still have to figure out how Recurring ticklers get handled, so this might not happen right away. The idea behind this is that the sole purpose of a tickler is to keep an idea "in the system, but of of site/out of mind" until it's "Show Date" (i.e., tickler date). At that point in time, it's like your "secretary" puts a file card on your desk in your Inbox to remind you about it. What do you think of this? For sorting by "View Date", I've had a different concept in mind that I want to ask your opinion of. I've been envisioning a separate "pushbutton" that would be labelled something like "FV Re-Add" or "AF4 Re-Add". There is also a new date field tied to that pushbutton (maybe called "AF/FV-Re-Add Date". Any time you push that button, the current date/time gets put into that field. Then that's the field that you would sort by. How does that sound? That way, someone can look at an item and decide not to do anything on it and the sorting isn't changed. They have to actually say to themselves "I did it". If you like the idea, do you have any thoughts as to what the pushbutton should be labeled? Assuming I can figure out how to add new fields this weekend, I think I can have that piece also done by Monday. Thanks for your thoughts! Jeff
On Monday, May 28, 2012 7:51:08 PM UTC-4, dmic wrote: > There's a lot here that I really like - keep going! > > I wanted to pick up on 11.a. I've recently put together a dashboard for > integrating Final Version (FV) into mGSD for choosing which tasks to do. > > Before I get to the code, a bit of background: I use mGSD as my main inbox > as well (which goes against the design philosophy). That is, I use the > QuickAdd to add any action, project, email, thought to the system. This > then shows up in a list of actions without contexts, that I work through > and make the relevant type of tiddler and give appropriate tags to (such as > context). Only once an action has a context does it appear on my to do > lists. This is important because this is a little different to FV, where > projects are added to the main 'to do' list, and just readded if they > aren't finished. I wanted to avoid this because part of the power of mGSD > is having the rest of the project stored relationally without appearing on > the actual list of things to currently do. > > Thus, this FV dashboard takes actions that are 'in the system' - they are > an actual action and have a context assigned. These actions are arranged as > the current list, ordered by last modified date. Then, using the FV > algorithm (which can be seen here: > http://archive.constantcontact.com/fs004/1100358239599/archive/1109511856508.html), > > I go down and 'dot' the actions I want to make a chain using the starred > feature. These starred items then show up on the 'current chain' list in > reverse viewed order (ie things at the bottom of the full list are at the > top of the chain). Then I work through the chain, marking complete the ones > I complete, and viewing the ones I don't so that they move to the bottom of > the full list. > > The one change I would like to make but don't know how is to make the > lists ordered by last viewed date (ie when the tiddler was last opened), > but sort: viewed doesn't work. Anyone know the answer to this one? > > You may also notice that unlike FV, I've added ticklers above the full > list, and at the bottom of the chain. This is because I think ticklers are > worthwhile as they keep action in the system, but out of sight until they > are needed (ie not having to constantly 'move' something on the main list > because it can't be done until a certain day). These then really form the > start of the full list to make sure they get done on the day they ping. > > Here is the actual code for the FV dashboard. Let me know what you think. > > * {{cols2{ > > {{col{ > > <<tiddler 'Ticklers Requiring Action'>> > > <<mgtdList > title:'Complete List' > startTag:Action > tags:'Next && !Done' > where:tiddler.hasActiveProject()&&(tiddler.hasParent('Context')) > view:ActionProj > mode:global > sort:modified > >> > > }}} > > {{col{ > > <<mgtdList title:'Current Chain' > startTag:Starred > tags:'Next && !Done' > view:ActionProj > mode:global > gView:bold > sort:-modified > >> > > <<mgtdList > startTag:Starred > tags:'Tickler && !Done' > view:Tickler > mode:global > gView:bold > sort:-modified > >> > > }}} > > }}} > * > -- You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/gtd-tiddlywiki/-/XDfPOTFyOvkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
