proming / android-shuffle

Automatically exported from code.google.com/p/android-shuffle
0 stars 0 forks source link

tags for actions #153

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
instead of fixing actions to a specific project allow to set arbitrary tags. 
tags can be projects or clients or other things that the user defines. this 
would help for cases where an action should go to multiple projects or where 
projects need to be grouped by clients. 

contexts could also be a kind of tags. possibly the implementation could 
just use tags everywhere, and then separately define which tags are context 
tags, which are project tags, and other tags.

contexts view and projects view could then just filter on those tags.

one could even consider to allow the creation of arbitrary tag categories.

Original issue reported on code.google.com by mba...@iaeste.at on 5 May 2010 at 6:26

GoogleCodeExporter commented 9 years ago
I reckon just a simple tag functionality rather than complicating things. A 
user defined tag will allow users to to set up their own organising regime. 
Definitely tags though. You need to separate multiple projects from each other 
so I can see personal ones without looking at work ones and vice versa. And 
before you say use contexts, remember I work from home 2 days a week! Thanks.

Original comment by stephen....@gmail.com on 14 Nov 2011 at 8:56

GoogleCodeExporter commented 9 years ago

I completely agree with this proposition. Tags are very versatile and I use 
them that way in other applications. And it seems a fantastic idea to catalog 
them afterward as contexts, locations, contacts, notebooks or whatever, so that 
one can access them quicker according to its category (a screen for each). The 
versatility of tags sometimes make them be quite a few. I have many tags and 
cataloging them would be the solution. And it would be as simple as applying 
tags to tags. No further steps.

I also have actions that correspond to several projects (e.g. cooperative 
projects of to companies). Sometimes I also need to filter the tasks that I 
have to do in the context "Computer" from the "project Y" that I can only do 
with "David". Working with just tags, makes it possible. It would be great also 
to be able to save this kind of filter. And wonderfull if I could filter even 
using the operators "and", "or" and "not" (if possible).

I think that this is the panacea of the Organization of tasks (applying GTD), 
as this approach is simple and versatile at the same time. simple means to me 
easier to program, and versatile means to me adaptable to everybody's needs.

Original comment by jvcenten...@gmail.com on 20 Dec 2011 at 8:51

GoogleCodeExporter commented 9 years ago
Multiple contexts can effectively be used as tags

Original comment by andybry...@gmail.com on 23 Mar 2012 at 10:36