On Tue, Aug 30, 2011 at 8:08 AM, Sebastian Fischmeister <[email protected]> wrote: > What about the sequential and parallel projects idea? Any feedback? >
I'll probably pick this up after finishing the ability to add commas to project names. Thanks, Matt > On Monday, August 29, 2011, Reinier Balt <[email protected]> wrote: >> Cool, I'll add it to Tracks as an example how to use the REST API for CLI >> purposes. >> This will probably help people in the future too when we stop supporting >> SOAP! >> >> Reinier >> >>> -----Oorspronkelijk bericht----- >>> Van: Vitalie Lazu [mailto:[email protected]] >>> Verzonden: maandag 29 augustus 2011 9:35 >>> Aan: Reinier Balt >>> CC: 'Sebastian Fischmeister'; [email protected] >>> Onderwerp: Re: [Tracks-discuss] Two features / donation >>> >>> Hello, >>> >>> On Dum 28 Aug 2011, Reinier Balt wrote: >>> > Nice, I was not aware of the script by Vitalie. If Vitalie agrees, we >>> > could fold that gist into tracks master. >>> > >>> > Reinier >>> No problems, I updated gist today to work with https protocol. >>> >>> https://gist.github.com/45537 >>> >>> > > -----Oorspronkelijk bericht----- >>> > > Van: [email protected] >>> > > [mailto:tracks-discuss- [email protected]] Namens >>> > > Sebastian Fischmeister >>> > > Verzonden: zaterdag 27 augustus 2011 17:01 >>> > > Aan: [email protected] >>> > > Onderwerp: [Tracks-discuss] Two features / donation >>> > > >>> > > Hi, >>> > > >>> > > I'm interested in using tracks. The main reasons are that I can >>> > > host it >>> > >>> > myself, >>> > >>> > > it looks good, and it's a web-based solution. Having used GTD for >>> > > some >>> > >>> > while, >>> > >>> > > this is what I'm missing in tracks. >>> > > >>> > > 1) Sequential & parallel projects (taken from OmniFocus). A parallel >>> > >>> > project >>> > >>> > > defines that all actions can be done anytime. It's essentially what >>> > > tracks currently assumes when 'depends on' is undefined. A >>> > > sequential project means that every action depends on the action >>> > > listed before. So if you >>> > >>> > have >>> > >>> > > Action 1 >>> > > Action 2 >>> > > Action 3 >>> > > >>> > > this implicitly means that Action 2 depends on Action 1. >>> > > >>> > > Sequential projects are useful, because it keeps the list of >>> > > available >>> > >>> > actions >>> > >>> > > short and one can quickly enter the list of actions (without going >>> > > through >>> > >>> > the >>> > >>> > > depends on; albeit the autocomplete). >>> > > >>> > > 2) A CLI or pure textbox interface for adding actions with project, >>> > >>> > contexts, >>> > >>> > > due dates, and notes. There was one [1], however, I'm unsure whether >>> > > it's still working with tracks 2.0. The CLI would permit a lot of >>> > > scripting >>> > >>> > capabilities >>> > >>> > > outside tracks such as using templates and checklists. If one were >>> > > to integrate it into tracks, it would look like the quick-add field >>> > > you can >>> > >>> > find in >>> > >>> > > mgsd. >>> > > >>> > > I can offer a cash donation (I paid for other gtd software, so I see >>> > > the >>> > >>> > value) >>> > >>> > > or a PPC-based G4 macbook (I know it's old, but that's why I can >>> > > donate >>> > >>> > it) >>> > >>> > > for the project. Any comments? >>> > > >>> > > Sebastian >>> > > >>> > > [1] http://www.getontracks.org/forums/viewthread/319/ >>> >>> >>> -- >>> Best regards, >>> Vitalie >>> WWW: http://www.webng.md >> >> > _______________________________________________ > 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
