On Wed, Apr 14, 2010 at 1:06 PM, Tomasz Melcer <[email protected]> wrote:
> Tom Van Braeckel wrote: > > On Wed, Apr 14, 2010 at 1:51 AM, Tomasz Melcer <[email protected] > > <mailto:[email protected]>> wrote: > > Task requirements. Some tasks can only be done in specific places, > like > > home or work. Other need specific facilities, like access to the > > Internet. Work view is a good idea, but it shows too much things for > me. > > My solution for that is to make tags like @home, @work, @shop, > > @shop:grocery (subtag of @shop), @net (all things that need access to > > the Internet), @person:john_smith (subtag of @net, because I can > contact > > him by email). But I still have some issues: > > * How to check which tasks can be done when being at home and having > > connection to the Internet? (@home, @net) I can browse through tags, > but > > I'd like to simply see everything possible in one place. > > > > Search ? RTM has smartlists for this, which are just saved search > queries. > > If the feature isn't there yet, you can add a feature request or > > implement it yourself. > I dislike using webapps for private stuff... but thanks for suggestion. > I found that I can temporarily make @home a subtask of @net; then both > can be visible at the same time. Not a great solution, but should be > enough for now. > > > * How to make a task require both @home and @net? > > > > Give it 2 tags: @home and @net > Then I will see it when I filter f.e. only @home, or only @net. > > > * How to identify things that don't have any of these tags (but might > > have other tags, like related to projects they belong to)? I.e. a > task > > might already have a tag @journey_to_Japan, so it wont be visible in > the > > category "Tasks without tags". > > > > Strange example, why tag something with @journey_to_Japan ? > A project tag; temporary substitute for not having project name with > every task. > > > If you use the @ prefix for context, you shouldn't use it to tag > projects. > > Why not use the # prefix ? Then you can get a project list by searching > > for # or by sorting the tags alphabetically. > Is # a valid prefix for tags? It doesn't work for me. Or maybe you are > talking about @# prefix? > I'm sorry about that, I forgot that tags in GTG always have the @ prefix. You could of course use @#, but I forgot that the @ is mandatory. > > > Task templates. I run a series of lectures at my university. For each > > lecture I need to do a (fixed) set of tasks, there's almost 40 of > them > > (http://files.exroot.org/dump/tasks.png) with a complex dependency > > relations. This set of tasks needs to be repeated for each lecture. I > > don't want to reenter all the tasks by hand each time. To solve this > > problem I wrote a simple python script to import a set of tasks from > a > > custom text format. A better solution would be to firstly prepare a > > "template" inside GTG, then make a deep copy of it -- a good idea for > a > > plugin, I guess. Is there another way to do this? > > > > Seems like a good workaround, and perhaps it can be converted into a > > plugin already, and then extended later ? > Noted, maybe I'll find some time to do that later. Is 0.3 branch stable > enough to use it (I don't mind need for occasional reverts)? Are plugins > for 0.2.x and 0.3 compatible? > > > Projects and tasks. My projects usually contain one or more tasks and > a > > repository of data (documents, links). Going from a task to its > project > > repository should be easy... but now it would involve making a link > from > > each task by hand. > > > > There's no "list" concept, which I miss as well. But I think that's on > > the roadmap. > How would a "list" concept work? > Well, having named lists of tasks, instead of one big pool of tasks with optional tags. > > For now I use an additional tag per project, but this makes problems > with task requirements mentioned earlier. > > > Task names. My tasks are often very similar across different > projects. > > For example I might need to make a reservation for a room for two > > different lectures. Now to distinguish both tasks I would have to > place > > a project's name (in this case, a lecture name) into tasks' titles, > but > > I often forget about that when creating tasks. From what I see, to > > identify which project a given task belongs to, I always need to > place > > project's name into the task title. I don't want to use tags for > that, > > because I use them now for task requirements (if I started doing so, > I'd > > lose the possibility to list all tasks without requirements). > > > > A list concept would help, but you can also use tag prefixes, like the ~ > > prefix for task requirements... > Are these prefixes functionally different? > > Thank you for answer, > > Tomasz Melcer > > > _______________________________________________ > Mailing list: > https://launchpad.net/~gtg-user<https://launchpad.net/%7Egtg-user> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~gtg-user<https://launchpad.net/%7Egtg-user> > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~gtg-user Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg-user More help : https://help.launchpad.net/ListHelp
