at the current exchange rate, that's more like 1p :) On 4/20/07, Stephen Boulet <[EMAIL PROTECTED]> wrote:
On Apr 20, 2007, at 12:18 PM, BSAG wrote: > On 19 Apr 2007, at 21:16, [EMAIL PROTECTED] wrote: > >> I know that some have talked about wanting to make some next actions >> dependent on others. I was wondering if the tickler mechanism could >> somehow be used to implement this. >> >> Ticklers become visible on a date; it would be nice to have a >> given next >> action become visible when the next action it depends on gets >> completed. > > Yes, that would be the way to do it, I think, using the state to > make dependent actions inactive. The difficult bit is a) how you > deal with making multiple actions dependent on one action as well > as single actions, and b) how you show the dependencies in the GUI. > > cheers, > > bsag Hi bsag, Here's my two cents (two p? ;). In the GUI (that is, on the project page), the dependent actions could be in a dependent actions section, just like the tickler actions are in their own section. I would, for simplicity's sake, only let a next action be dependent on one and only one other next action. Each action then could have only one parent and one child. One could choose to have a dependency chain, to use the tickler, or to avoid dependencies altogether. Stephen _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
