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 <[email protected]> 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 [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 -~----------~----~----~----~------~----~------~--~---
