Per se, the depending actions implementation is wonderful - but in practice, the procedure forces you to do a lot of manual figdeting after creating a project, in effect weakening the power of quick-add.
So hoping for some development on this, here's yet another alternative twist; However, first, just to clarify my preceding post; the numbers seen (i.e "4|" ) are not actually written by the user. Rather the suggestion is to have them permanently in the outside of the quick-add frame, merely as references to specific rows in quick-add. Here's a different approach: http://kronenpj.tiddlyspot.com/ i.e small up/down arrows letting the user push the action a step up or down. Very intuitive. Could perhaps even be embedded *directly* into the quick-add!? Possibly a working for that arrow type solution or some other could be "fields". I just discovered these myself (under ToolsMenu>More>fields). Apparently it's a place to store tiddler specific meta information. If an action (or any tiddler) is supposed to have some type of relation to something else, such as depencdence in our example, maybe a value could be stored here. For an action sequence listing, one could then use a fET; <<forEachTiddler sortBy 'tiddler.fields.changecount' descending write '"* [["+tiddler.title+"]] ("+tiddler.fields.changecount+")\n"' >> E.g GridPlugin (Shulman) lets you directly create and set specific fields and values http://www.tiddlytools.com/#GridPlugin ...and I just found this thread, stating that there is a *core* filtering for fields which I guess means *speed*! http://groups.google.com/group/tiddlywiki/browse_thread/thread/313055747ca1a706# Just brainstorming out loud ;-) On 27 Okt, 17:57, Mat <matiasg...@gmail.com> wrote: > On 23 Okt, 13:22, Simon Baird <simon.ba...@gmail.com> wrote: > > > > > > An alternative approach: All actions listed in Quick add could by > > > default get a Next tag, unless manually tagged with WaitingFor, but > > > then as an action is tagged with 'PrecedingAction', this Next tag is > > > eliminated. This would *keep* the 'Next-status' of actions that don't > > > get a following action. Tagging with 'PrecedingAction' would also omit > > > the need for a "Future" tag alltogether. Whatever is not tagged Next > > > or W/F is, per definition, Future! > > > This could work. The above example might look like this. (I'm choosing > > D for 'Dependent') > > > Make sandwich > > .get bread|N > > .spread butter|D > > .spread jam|D > > .cut in half|D > > For dependence on multiple preceding actions, how about this; > Along the left gray edge of the 'quick add' box there are "lables" for > referencing a certian row in the 'quick-add field'. > E.g the left edge (outside the actual writing field) could be > permanently numbered from top down, looking like this; > > 1| Make sandwich > 2| .get bread > 3| .spread butter > 4| .spread jam > 5| .cut in half > 6| > 7| > > to smoothly declare actions dependent on multiple previous actions, > you use the 'label', i.e > > 1| Make sandwich > 2| .get bread|N > 3| .spread butter|D > 4| .spread jam > 5| .cut in half|D3 > 6| .stick in toothpick > 7| .put on plate|D|D2 > > (or, even more compact, maybe optionally to "D|D2" it could read > "DD2" ) > > The same nomenclature could probably by used for subprojects, as long > as they are declared simultaneously in the quick-add box, i.e > referencing the line/label where it's superior project is. > > :-) -- 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.
