Re: Waiting actions by person - Confused
Waiting actions by person Think of it more as Waiting Actions (grouped by person). Try adding a bunch of waiting actions and give some of them an associated contact then it might make more sense. A long time ago it used to be Waiting Actions by Context but then someone suggested that context wasn't that useful for a waiting action (after all it doesn't matter what your context is if you are waiting on some third party or other events to transpire) but associated contact was in fact quite a useful piece of information for waiting actions. The fact that (No Contact) is a clickable link is not really by design. It probably shouldn't be. Just btw (and for more advanced users), if you seldom use contacts and just want a flat list of waiting actions there then you can get it by modifying the appropriate mgtdList in the !Project section of TagDashboards tiddler. Remove the group:Contact param. Or you could change it back to group:Context it that works better for you. Simon. On Fri, May 8, 2009 at 1:03 PM, colinchristensen colinchristen...@iinet.net.au wrote: I can't make sense out of the waiting actions by person list and tiddler creation at the bottn of a project tiddler. I was half expecting it to give me list of contacts I have. However, it simply lets me create a tiddler with a Waiting tag. Once created I can of course then indicate an associated contact which could imply being waited for I suppose. And then, after Ihave done it all, it reports to me (No contact), and hovering over it tells me I have no tiddler of that name, further making me suspect that I should have been able to indicate an existing contact tiddler which would then be listed there. What is it trying to tell me with (No contact)? I think I'm having trouble generaly seeing the wood for the trees any time I need to flick something over to someone and then follow up later if they don't get back to me. I'm sure it will be obvious once I have grasped it but at this stage... Any ideas? Any examples on how others handle waiting on others or waiting on ither people? And finally - I get a (No Contact) -- simon.ba...@gmail.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
OK, a few haphazard thoughts: 1) I think I meant !Tickler instead of !Tiddler. I get those confused all of the time. =P TaggyTagging shows a list of all tiddlers tagged with the title of the current tiddler. In other words, if any actions are dependent on a certain action, they will be listed and linked at the bottom of the action tiddler. This is for convenience/ organization. Put it right before the closing /div in !Action (and optionally !Tickler). 2) I used the action dependencies to deal with mini 2-4 step projects when I don't want to create a whole project in mGTD. It seems simpler that way. 3) The dependent action button should create tags with the Future status. Make sure it's listed with the other tags? Originally I didn't think of it but someone suggested it, so the code's in this thread somewhere. 4) The dropdown list SHOULD show the action selected. It does in my system. Did you make sure to add Action to the tagsToIndex list in MgtdConf? This step is important. 5) Multiple dependencies: This is doable, but it seems like it would be a MESS to create dozens of checkboxes. :( Cheers, Kralik On Apr 20, 5:08 am, Arma armadil...@googlemail.com wrote: Hi there, thank you for helping me out with the wiki pre-tag, bkh! I adjusted the other code. But I am still not really sure about the last part. As Kralik mentioned, he still includes _ To show dependent actions, add the following to TitleButtons under ! Action and !Tiddler (also right before last /div): div macro=tagglyTagging class=tagglyTagging/div _ i also have this in my mGTD, but in TitleButtons I only found !Action and i could not figure out where !Tiddler is. My mGTD seems to work fine though. And although I included everything now mentioned in the wiki-article still the new dependent action is not set to future if it is created with the dependent action button in the toolbar. Also the dropdownmenu does not show then the action on which it is dependent. Nevertheless if I choose it in the dropdown manually it sets the action to future. (not really a bug, or?) @Kralik: - could you please specify again what this line div macro=tagglyTagging class=tagglyTagging/div does and where to include it exactly? Then I will be glad to update the wiki accordingly. - I agree, that it would be better to remove the entry for new action from the dropdown-list as long as it is not consistent. - To show dependent actions, but as noted, I changed the dependent action code a bit. - mh, what part do you mean with dependent action code? I am not sure to have it included in the wiki. And the last one: I would like to hear your opinions about multi-dependencies. Is there a need for something like A depends on the completion of all B,C and D? Technical possibility? As far as I know, I never saw so far a combination of a dropdown-list with a checkbox-field, which would be kind of needed if this design should include several choices for dependencies. e.g. like this Action A Depends on: [ ] | _ V_ | [ ] Action B | | [ x ] Action C | | [ x ] Action D | |___| Referring to the GTD-principles, shouldn't this be done with projects/ subprojects rather than with interdependent actions? Any suggestions or comments? I would appreciate it! Again many thanks for the efforts! Arma --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Hi there, thank you all very much!! This is just what makes mGTD even more useful. I have just two remarks: 1) On the wikipage If you're gonna write a summary, don't do it here -- do it on the wiki:http://tiddlywiki.org/index.php?title=MonkeyGTD/Customization_Guide/W... the instructions do not really lead to functional version (I followed the instructions given here in the posts) My guess is that the final step (which is an earlier one here in the posts) is somehow truncated. 2) I noticed in the dropdown-list, there is one item New Action... but on clicking this, there is something generated, but it is not a full blown action. Somehow I can find it via search, but it (the tiddler presumably with this name) has no project associated and it is not set to anything (next, waiting, future). If I may I would like to suggest to open this newly created action (from the New Action... of the dropdown-list) instantaneously as a next-action of the same-project (I don't see any good way right now to specify, thus one would have to adjust the action-type manually (if it should be also a future action, not a next) but next should definetly be the default, don't you think? I would like to here your suggestions, and please keep up the excellent work, this is getting more fantastic! (I already infected some of my friends with mGTD ;-) ) THX Arma --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Another thing; it is a bit inconsistent now in that the default for
created actions is 'next'. I suggest a quick-fix(?): Setting a
Depends on pretty much by definition means that an action is
Future and IMO should be changed into that by default (if it was
tagged Next, but not SomedayMaybe or Waiting). As it is now, this has
to be done manually.
Possible?
Great idea! Here you go, put this in MgtdTagControls --
MultiSelectTag. Find the following:
// if selectedItem is null this works to remove any
actOnTiddler.setTagFromGroup(tag,selectedItem);
Then add below:
// automatically make dependent actions future
if (tag == Action) {
if (selectedItem == null)
actOnTiddler.setTagFromGroup(ActionStatus, Next);
else
actOnTiddler.setTagFromGroup(ActionStatus, Future);
}
Note that if an action is dependent and you remove that dependency, it
will become a Next action.
Works for me -- let me know what you think!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups GTD
TiddlyWiki group.
To post to this group, send email to GTD-TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to
gtd-tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/GTD-TiddlyWiki?hl=en
-~--~~~~--~~--~--~---
Re: Waiting actions
This is getting GREAT
I did a little testing and found the following; If an action B is set
as dependant on A, but B is marked as Waiting for. Then, finishing
A, auto-sets B to *both* Next and Waiting for. I think only Future
actions should be auto-set to Next. (Less serious is that also Done
actions seem to get an extra Next).
:-)
/Mat
On 4 Apr, 20:46, Kralik bakerb...@gmail.com wrote:
Another thing; it is a bit inconsistent now in that the default for
created actions is 'next'. I suggest a quick-fix(?): Setting a
Depends on pretty much by definition means that an action is
Future and IMO should be changed into that by default (if it was
tagged Next, but not SomedayMaybe or Waiting). As it is now, this has
to be done manually.
Possible?
Great idea! Here you go, put this in MgtdTagControls --
MultiSelectTag. Find the following:
// if selectedItem is null this works to remove any
actOnTiddler.setTagFromGroup(tag,selectedItem);
Then add below:
// automatically make dependent actions future
if (tag == Action) {
if (selectedItem == null)
actOnTiddler.setTagFromGroup(ActionStatus, Next);
else
actOnTiddler.setTagFromGroup(ActionStatus, Future);
}
Note that if an action is dependent and you remove that dependency, it
will become a Next action.
Works for me -- let me know what you think!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups GTD
TiddlyWiki group.
To post to this group, send email to GTD-TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to
gtd-tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/GTD-TiddlyWiki?hl=en
-~--~~~~--~~--~--~---
Re: Waiting actions
For the record, in the last code provided by Kralik, the final } becomes hidden because of googlegrups hide quoted message feature. I.e the whole thingy should end with a } Another thing; it is a bit inconsistent now in that the default for created actions is 'next'. I suggest a quick-fix(?): Setting a Depends on pretty much by definition means that an action is Future and IMO should be changed into that by default (if it was tagged Next, but not SomedayMaybe or Waiting). As it is now, this has to be done manually. Possible? (Ideally, when typing actions into the wonderful QuickAdd feature, they are typically naturally sequenced. As such it would be superb if QuickAdd automagically added the preceding actions as tags to the latter. Thanx! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Even better than the last tweak (though you could certainly use both), here is a GUI-dropdown addition that lets you assign an action a dependent action. It's pretty easy: 1) Edit MgtdConf and add Action, to the tagsToIndex list. 2) Edit TitleButtons and add the following code under the !Action heading: // reference line, near the top div style=float:right; class=smaller // new line right here: span class=labelDepends on:/spanspan macro=multiSelectTag Action allowNone:on/spanspan macro=linkToParent Action/span Tada! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Excelent! Thank you, There is only one way to show the actions that belong only to this project and not to show all Action of the mGTD? On Wed, Mar 25, 2009 at 4:33 PM, Kralik bakerb...@gmail.com wrote: Even better than the last tweak (though you could certainly use both), here is a GUI-dropdown addition that lets you assign an action a dependent action. It's pretty easy: 1) Edit MgtdConf and add Action, to the tagsToIndex list. 2) Edit TitleButtons and add the following code under the !Action heading: // reference line, near the top div style=float:right; class=smaller // new line right here: span class=labelDepends on:/spanspan macro=multiSelectTag Action allowNone:on/spanspan macro=linkToParent Action/span Tada! -- Jorge A. Ramos M. SuSE, Debian GNU/Linux - FreeBSD Support Consultor System Administrator Cartagena de Indias, Colombia - http://jramosm.wordpress.com/ --- www.champetux.org Grupo de Usuarios de Software Libre del Caribe Colombiano - http://www.gnu.org/philosophy/free-sw.es.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Here's something that works for me:
Add the following to the bottom of !ViewTemplateToolbar in
MonkeyGTDTheme (right before last /div):
span macro=showWhenTaggedAny Action Once
span macro=newSavedTiddler title:'new dependent action'
label:'dependent action' tag:{{'Action Future
[['+config.macros.mgtdList.getRealm()+']] [['+tiddler.title+']]'}}/
span
/span
To show dependent actions, add the following to TitleButtons under !
Action and !Tiddler (also right before last /div):
div macro=tagglyTagging class=tagglyTagging/div
This works to provide a simple way to add dependent actions to
ticklers or other actions. Not as good as a drop-down box, but it
works well so far.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups GTD
TiddlyWiki group.
To post to this group, send email to gtd-tiddlyw...@googlegroups.com
To unsubscribe from this group, send email to
gtd-tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/GTD-TiddlyWiki?hl=en
-~--~~~~--~~--~--~---
Re: Waiting actions
I love the concept of SequencedActionsPlugin but in practice use I've found it too iffy with all the additional manual work it requires to write or copy-paste the names of actions as tags etc etc. For it to be practical, I say it would have to be integrated more - Humbly asking if there's any news from anyone on this? It is such a wonderful thing, improving a fundamental issue in mGTD. Thank you. /Mat --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Just a little followup form a user; I love the concept of SequencedActionsPlugin but in practice use I've found it too iffy with all the additional manual work it requires to write or copy-paste the names of actions as tags etc etc. For it to be practical, I say it would have to be integrated more - and I really hope it can be because I believe the concept of it can be very time saving. (Following core GTD in combo with mGTD otherwise means not updating 'future actions' into 'next actions' more than once a week otherwise. What projects can actually progress at such a slow speed?) Something like SequencedActionsPlugin would really allow us to do this admin work where it belongs, i.e during the weekly review. IMO ;-) Some thoughts on integrating it; * A checkbox-type-dropdown menu next to each action, listing all other actions that same project. I guess the dropdown-menu could be present both in an actual action tiddler, but also in e.g project tiddlers next to each listed action. There are typically not that many, and I think 99% of the need should be covered if there is such a menu for only Next, Future and Waiting actions... or even 90% if it was only on the Future actions even... ...but, more importantly, some way in 'quick add'. Actually - actions inserted there *are* typically already more or less in order, so maybe pressing create now could by default append the previously listed action as a tag to the following one. Or a 'middle step' before pressing create now - i.e a button saying action sequencing or such to do this and resulting only in changes in the quick add text field, i.e nothing was yet actually created. Another thought would perhaps be to simply have each row in quick add numbered(!) - either manually as items are added there or simply haveing a permanent numbering of each row (e.g permanent numbers showing outside the text-field) for each row. Thus, inserting a row number as a tag, actually represents the whole action (name) at that position. ...or, an invisible prefix to the names. I.e as it is not, actions are presented in alphabetical order. It is of course already possible to e.g number items so that they are presented in desired order, but it is not very elegant for many reasons. Ann invidible prefix would be more elegant, and of course in combo with the system automatically resetting an action from future to next as soon as the previous next was done. ...and for mGTD 8.5 I suggest... ;-) Drag-n-drop feature, i.e in project view one can smoothly just rearrange listed actions. Same inside the quick add tool. Thanks /Mat --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
On Wed, Jan 14, 2009 at 8:17 AM, Mat matiasg...@gmail.com wrote: I like the idea of a drop down List. The TaggerPlugin suggested by Mat may help. But i think that the list of tags should be filtered somehow. E.g. only Tags that are used together with Action- or Tickler-Tags should be displayed. Maybe I misunderstand, but for actions it should be enough with that they belong to the project, no? I imagine this should be possible to implement just like specifying a Realm filters out which Areas that are presented in a Project tiddler. Yeah, we don't need TaggerPlugin or the like. We have all the UI elements we need already in MGTD. Simon. -- simon.ba...@gmail.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to GTD-TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Hello Simon, On 13 Jan., 05:12, Simon Baird simon.ba...@gmail.com wrote: Carsten, I'm excited about this. Nice work. As for Jim's comments, I think this seems lightweight enough so you can just ignore it if you don't want to use it. When I get a chance I will have a play with this and hopefully include it in MGTD. I have some ideas about the UI also, something similar to the contact drop down but for other actions. Thank you for your comment. It would be great if you could include this in MGTD. I like the idea of a drop down List. The TaggerPlugin suggested by Mat may help. But i think that the list of tags should be filtered somehow. E.g. only Tags that are used together with Action- or Tickler-Tags should be displayed. Thanks for the contribution. Now that some time has passed, is anyone out there using this in production? Since two weeks i am using it in my production MGTD. And until now all seems to work as expected :-) Carsten --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
I just started using this and it is great! I can see we'll need some kind of drop down. Tags are case sensitive... found out the hard way when I couldn't get this to work for a while then noticed I missed a capital letter. On Tue, Jan 13, 2009 at 12:02 PM, Carsten Thiele googlegro...@carsten-thiele.de wrote: Hello Simon, On 13 Jan., 05:12, Simon Baird simon.ba...@gmail.com wrote: Carsten, I'm excited about this. Nice work. As for Jim's comments, I think this seems lightweight enough so you can just ignore it if you don't want to use it. When I get a chance I will have a play with this and hopefully include it in MGTD. I have some ideas about the UI also, something similar to the contact drop down but for other actions. Thank you for your comment. It would be great if you could include this in MGTD. I like the idea of a drop down List. The TaggerPlugin suggested by Mat may help. But i think that the list of tags should be filtered somehow. E.g. only Tags that are used together with Action- or Tickler-Tags should be displayed. Thanks for the contribution. Now that some time has passed, is anyone out there using this in production? Since two weeks i am using it in my production MGTD. And until now all seems to work as expected :-) Carsten --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
I like the idea of a drop down List. The TaggerPlugin suggested by Mat may help. But i think that the list of tags should be filtered somehow. E.g. only Tags that are used together with Action- or Tickler-Tags should be displayed. Maybe I misunderstand, but for actions it should be enough with that they belong to the project, no? I imagine this should be possible to implement just like specifying a Realm filters out which Areas that are presented in a Project tiddler. /Mat P.S Regarding my attempted thread name change; One reason I did not find this until just today was because of the not so informative old thread title. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
I'm using it. It's fabulous.
I like the idea of including a drop down so that dependencies can be set
without editing the tiddler manually. You'd want a multi-select list box,
if such a thing exists in MonkeyGTD, because some actions depend on more
than one prior action.
On Mon, Jan 12, 2009 at 8:12 PM, Simon Baird simon.ba...@gmail.com wrote:
Carsten,
I'm excited about this. Nice work. As for Jim's comments, I think this
seems lightweight enough so you can just ignore it if you don't want to use
it.
When I get a chance I will have a play with this and hopefully include it
in MGTD. I have some ideas about the UI also, something similar to the
contact drop down but for other actions.
Thanks for the contribution. Now that some time has passed, is anyone out
there using this in production?
Best wishes,
Simon
On Sat, Dec 20, 2008 at 11:33 PM, Carsten Thiele
googlegro...@carsten-thiele.de wrote:
Hello,
i converted my Hack to a complete plugin. I Uploaded a Demo into
this group as file: monkeygtd-SequencedActionsPlugin-demo.zip (
http://gtd-tiddlywiki.googlegroups.com/web/monkeygtd-SequencedActionsPlugin-demo.zip
) The html-Upload did not work, so i added the zip-File, that can be
downloaded from the files area.
When you unzip it, and open the file with this added to the filename:
#[[SequencedActions%20Demo]]%20Action1%20Action2%20Action3%20Action4%20
[[Do%20Something]]%20Action5
or just open the SequencedActions Demo Tidder for instructions.
Maybe this helps,
Carsten
On 17 Dez., 22:22, Carsten Thiele googlegro...@carsten-thiele.de
wrote:
Hello,
i modified my monkeygtd to support sequenced-Actions. I use the
normal Tag-Feature to Control the sequence of the actions. When i
create an action that depends on another action i just Tag it with
the name of the first one, and set it to Future. When the first
Action is marked as Done or, if it is a Ticker, is marked as
Actioned (only works for one-time-Ticklers). the second action is
modified from Future to Next. There is no GUI-Support for this, i
have to edit the Actions and type in manualy the name of the Actions
in the Tags-Field.
Maybe with an Example its more clear to understand:
First
Action:
Action 1
Can be done when Action 1 is finished: Action
2 Action3
Can be done when A2 and A3 are finished: Action
4
I create the actions like this
Action 1, a normal Next Action
Action 2 and Action 3 Future Actions Tagged with [Action 1]
Action 4 Future action Tagged with [Action 2] [Action 3]
- Now, when i finish Action 1, the code searches for Actions with
the Tag Action 1, and finds Action 2 and Action 3.
- For each Action the code searches if all required Actions (only
Action 1 in this case) are done. If this is true, the Action (here
Action 2 and 3) are moved from Future to Next
- If i undo Action 1, Action 2 and Action 3 are moved from Next to
Future
- When Action 2 is finished, again all Actions with the Tag Action
2 are searched, in this case just Action 4.
- The Code starts searching all Actions and Ticklers that are
referenced in the Tag-field of Action 4. It finds Action 2 as done,
but Action 3 as not done, so the Action 4-Action is NOT moved from
Future to Next
- Now Action 3 is done, too.
- The Code again searches for all Actions and Tickers that are
referenced in the Tag-field of Action 4. Now it finds both Actions
(Action 2 and Action 3) as Done so Action 4 is moved from
Future to Next.
The visualisation in the GUI for this solution is not very good. In
the Project-Dashboard the Actions are not ordered in the right way,
and you can not see that there are dependencies between the actions.
But for me this is ok, its just for auto-nexting one of the future
actions, so that i dont have to do a check of the Projects with no
next action-View. Or Project Dashboard every time i finish an Action
that is part of a Project.
Maybe someone else can add some UI-Support to this solution.
Until now i did not test it with MonkeyGTDs with many Actions, so
maybe there is still a performance problem with this, but for my (at
the moment) small test environment it works good. Next step will be
more tests and the integration in my production-monkeygtd.
Please do not integrate this without good testing in your production-
Monkey-GTDs. Maybe there is still something wrong that can cause your
data to be damaged!
So here is what i have done.
I modified the function TiddlyWiki.prototype.setTiddlerTag. now it
contains this code:
TiddlyWiki.prototype.setTiddlerTag = function(title,status,tag)
{
var tiddler = this.fetchTiddler(title);
if(tiddler) {
var t = tiddler.tags.indexOf(tag);
if(t != -1)
tiddler.tags.splice(t,1);
if(status)
Re: Waiting actions
If either action is turned into a project will the dependency still hold. Examples: Fix Porch depends on Buy Tools 1) If Fix Porch is converted to a someday project will Fix Porch become active once Buy Tools is completed? 2) If Buy Tools is converted to a project will Fix Porch become active once Buy Tools is completed? Thanks for your work on this plugin, Drew On Dec 31 2008, 4:02 pm, Daniel Baird danielba...@gmail.com wrote: On Tue, Dec 30, 2008 at 7:04 AM, jdunham jwdun...@gmail.com wrote: [...] I tested some circular dependencies (e.g. Action1 depending on Action5 in your demo), and nothing broke, which was good. I don't think there is a good way to handle this, but at least the TW didn't go into an infinite loop. You don't have to look very far to find circular action lists in real life -- lots of tasks need regular doing, along the lines of sleep - shower - work - eat - sleep. Maybe the right thing to do is to un-DO a done action if it gets triggered when it's already done. It's probably a little more complicated in implication that it sounds, but that's perfect for a plugin type enhancement. Cheers ;Daniel -- Daniel Baird /to be or not to be/ = /(2b|[^2]b)/ = /(2|[^2])b/ = /.b/ ...optimise your regexes, people! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
Re: Waiting actions
Hi,
Well done on the coding. Action dependancies are outside of GTD
though, and within the realm of project planning. There are loads of
free and commercial project planning tools on the market, that will do
dependancies, critical path ananlysis, float, resource management
etc. MS Project is one.
However there are very few GTD tools, and MGTD is probably the best
there is. Please don't change MGTD from a GTD tool into a ten-a-penny
project manager.
About half the posts to this group are requests for MGTD to be turned
into something else, eg. project planner, mail client, address book,
PIM tool, calenndar manager. All worthy applications, but nothing to
do with GTD really, and well catered for elsewhere.
Sorry to be so negative around Christmas time. Have a happy
Christmas! And well done on the coding, it's more than I could have
managed.
Jim.
On Dec 20, 1:33 pm, Carsten Thiele googlegro...@carsten-thiele.de
wrote:
Hello,
i converted my Hack to a complete plugin. I Uploaded a Demo into
this group as file: monkeygtd-SequencedActionsPlugin-demo.zip
(http://gtd-tiddlywiki.googlegroups.com/web/monkeygtd-SequencedActions...
) The html-Upload did not work, so i added the zip-File, that can be
downloaded from the files area.
When you unzip it, and open the file with this added to the filename:
#[[SequencedActions%20Demo]]%20Action1%20Action2%20Action3%20Action4%20
[[Do%20Something]]%20Action5
or just open the SequencedActions Demo Tidder for instructions.
Maybe this helps,
Carsten
On 17 Dez., 22:22, Carsten Thiele googlegro...@carsten-thiele.de
wrote:
Hello,
i modified my monkeygtd to support sequenced-Actions. I use the
normal Tag-Feature to Control the sequence of the actions. When i
create an action that depends on another action i just Tag it with
the name of the first one, and set it to Future. When the first
Action is marked as Done or, if it is a Ticker, is marked as
Actioned (only works for one-time-Ticklers). the second action is
modified from Future to Next. There is no GUI-Support for this, i
have to edit the Actions and type in manualy the name of the Actions
in the Tags-Field.
Maybe with an Example its more clear to understand:
First
Action:
Action 1
Can be done when Action 1 is finished: Action
2 Action3
Can be done when A2 and A3 are finished: Action
4
I create the actions like this
Action 1, a normal Next Action
Action 2 and Action 3 Future Actions Tagged with [Action 1]
Action 4 Future action Tagged with [Action 2] [Action 3]
- Now, when i finish Action 1, the code searches for Actions with
the Tag Action 1, and finds Action 2 and Action 3.
- For each Action the code searches if all required Actions (only
Action 1 in this case) are done. If this is true, the Action (here
Action 2 and 3) are moved from Future to Next
- If i undo Action 1, Action 2 and Action 3 are moved from Next to
Future
- When Action 2 is finished, again all Actions with the Tag Action
2 are searched, in this case just Action 4.
- The Code starts searching all Actions and Ticklers that are
referenced in the Tag-field of Action 4. It finds Action 2 as done,
but Action 3 as not done, so the Action 4-Action is NOT moved from
Future to Next
- Now Action 3 is done, too.
- The Code again searches for all Actions and Tickers that are
referenced in the Tag-field of Action 4. Now it finds both Actions
(Action 2 and Action 3) as Done so Action 4 is moved from
Future to Next.
The visualisation in the GUI for this solution is not very good. In
the Project-Dashboard the Actions are not ordered in the right way,
and you can not see that there are dependencies between the actions.
But for me this is ok, its just for auto-nexting one of the future
actions, so that i dont have to do a check of the Projects with no
next action-View. Or Project Dashboard every time i finish an Action
that is part of a Project.
Maybe someone else can add some UI-Support to this solution.
Until now i did not test it with MonkeyGTDs with many Actions, so
maybe there is still a performance problem with this, but for my (at
the moment) small test environment it works good. Next step will be
more tests and the integration in my production-monkeygtd.
Please do not integrate this without good testing in your production-
Monkey-GTDs. Maybe there is still something wrong that can cause your
data to be damaged!
So here is what i have done.
I modified the function TiddlyWiki.prototype.setTiddlerTag. now it
contains this code:
TiddlyWiki.prototype.setTiddlerTag = function(title,status,tag)
{
var tiddler = this.fetchTiddler(title);
if(tiddler) {
var t = tiddler.tags.indexOf(tag);
if(t != -1)
tiddler.tags.splice(t,1);
if(status)
Re: Waiting actions
Something like that (where completing an action auto-magically makes another action in to a Next action) has been mentioned a few times. I like the plan where each action depends on one or more other preceding actions, and when all the preceding actions are done, that action becomes Next. It's gonna require a reasonable JavaScript programmer with a bit of free time, though, as I understand it. Cheers ;Daniel On Tue, Dec 16, 2008 at 7:06 PM, Alexis alexis.ko...@gmail.com wrote: Hello, could it be possible within MonkeyGTD to define an action waiting for another action to finish ? Sometimes I encounter the situation where several actions need to be performed in a certain order. It would be nice to define this order of actions using a waiting for other action. When an action is marked done, all actions waiting for this action should be marked active. Cheers, Alexis Kotte -- Daniel Baird /to be or not to be/ = /(2b|[^2]b)/ = /(2|[^2])b/ = /.b/ ...optimise your regexes, people! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~--~~~~--~~--~--~---
