Open GoogleCodeExporter opened 8 years ago
Can you specify the behaviour in conjunction with the view's settings? It's not
obvious to me hat should happen if the implicit [no XYZ] container does not
meet the view's filtering rules.
Original comment by el.goog....@gmail.com
on 2 May 2012 at 9:57
Another approach to this issue could be an individualizable inbox behavior.
That is:
There is an option "behavior" in the view settings of inbox. This option
consists of four alternative behaviors: "no project and no context" (standard,
used right now), "no project", "no context", "neither project nor context" (was
used some time ago as behavior).
Original comment by LippertsJan
on 2 May 2012 at 10:04
I'm not sure what the difference between "(no project) and (no context)" and
"neither project nor context" would be, since I would translate "neither
project nor context" to just that. I think "(no project) or (no context)" would
be an alternative, which I would descibe as "either no project or no context".
Regarding your suggestion to allow additional Inbox view settings, I feel it
would be nice to maintain the current approach in which all view options are
available in all view's settings, even if some are grayed out in some views
because they're fixed.
Original comment by el.goog....@gmail.com
on 3 May 2012 at 4:49
My mistake. I meant "(no project) or (no context)" and "(no project) and (no
context)" as options. The latter one is used right now to select the actions
displayed in the inbox. Some time ago the first one
Also look at http://code.google.com/p/android-shuffle/issues/detail?id=34#c9
Issue 34 was about actions without projects, but the comment gives some
suggestions about contexts too.
[quote (shortened)]
* How about setting the default context to "Inbox" or "To process"?
* Make the default project "None" and give it no other implicit meaning that
what it
is: does not say anything about the status of that task.
* Make it possible to have "None" be a valid choice for context as well. And
again:
it should mean just that and be treated exactly the same as any other context.
That would make it clear which actions still have to be moved out of the inbox, and
it gets rid of the dependency of assigning a project.
[/quote]
Original comment by LippertsJan
on 3 May 2012 at 6:05
Interesting indeed.
I must admit I'll have to think about this, since my original intention was
simply to point out that the suggestion appeared not very straightforward with
respect to the current Shuffle features. I was by no means intending to suggest
I had a concept available. ;)
Original comment by el.goog....@gmail.com
on 3 May 2012 at 7:17
Original issue reported on code.google.com by
Blablat...@gmail.com
on 27 May 2011 at 7:55