How do I make a task active?
24 views
Skip to first unread message
Rob
Oct 28, 2011, 2:54:53 PM10/28/11
to MyLifeOrganized for Android
Okay, so I've entered more than 120 items into MLO for Android, and
have started processing the inbox. But now I've run into a problem:
when I add a context to a task and save the task, it remains in the
inbox.
Other GTD apps I've used convert an inbox task to active as soon as I
do any processing on a task. What am I missing?
have started processing the inbox. But now I've run into a problem:
when I add a context to a task and save the task, it remains in the
inbox.
Other GTD apps I've used convert an inbox task to active as soon as I
do any processing on a task. What am I missing?
MOK | MATSURU
Oct 30, 2011, 7:40:51 PM10/30/11
to mlo-a...@googlegroups.com
Rczerr,
Yup, you have to manually move your tasks to the desire branch. MLO doesn't move the task for ya.
1. Goto OUTLINE view. Do your processing there.
2. Move the task by switching into MOVE mode. It's under the setting.
3. Move your task by pressing on the "3 line button" on your right.
4. Exit MOVE mode under the setting menu.
Hope this helps.
Rob
Oct 30, 2011, 9:03:01 PM10/30/11
to MyLifeOrganized for Android
Thanks for the help. It didn't take as long as I expected it to, but
it's still a bit of a hassle and error-prone if you're moving a lot of
items. It would be nice if everything could be automatically moved to
an "Active Tasks" area in the outline upon processing.
it's still a bit of a hassle and error-prone if you're moving a lot of
items. It would be nice if everything could be automatically moved to
an "Active Tasks" area in the outline upon processing.
MOK | MATSURU
Oct 30, 2011, 9:17:35 PM10/30/11
to mlo-a...@googlegroups.com
Another way to do this is:
1. add/move all the tasks u wanna move as subtasks under 1 parent task. Then close the parent task.
2. Cut the parent task (it will also cut the subtask together)
3. Paste at the desire location. Subtasks will also be paste.
:-)
conrad...@gmail.com
Oct 30, 2011, 9:20:18 PM10/30/11
to mlo-a...@googlegroups.com
This is different in that the action you eiwcribe isn't enough to get it out if the inbox. This is designed to accommodate many systems and not all are gtd centric. However, it is infinately more powerful than anything else in the market and much more suited to gtd than any of the other so called gtd apps.
conrad...@gmail.com
Oct 30, 2011, 9:24:50 PM10/30/11
to mlo-a...@googlegroups.com
I think once you dug into mlo and use it more you will understand why that will never work. The system is designed to be very open yet still work with a high level of automation. What you are asking would simply never work.
----- Reply message -----
From: "Rob" <rcz...@gmail.com>
To: "MyLifeOrganized for Android" <MLO-A...@googlegroups.com>
----- Reply message -----
From: "Rob" <rcz...@gmail.com>
To: "MyLifeOrganized for Android" <MLO-A...@googlegroups.com>
MOK | MATSURU
Oct 30, 2011, 9:28:46 PM10/30/11
to mlo-a...@googlegroups.com
Conrad,
i agreed. MLO is deisgned to be flexible. People can use it in whichever way they wanted to.
regards,
MOK | MATSURU
- MALAYSIA -
--------------------------
www.matsuru.net
Support me at http://fans.matsuru.net
--------------------------
Saito College
Tel : +603 – 7954 7200 (ext221)
Fax : +603 – 7954 7211
www.saito.edu.my
Be our fan on Facebook!
www.facebook.com/saitocollege
--------------------------
Rob
Oct 30, 2011, 9:29:02 PM10/30/11
to MyLifeOrganized for Android
Hey, I think you're onto something. I'll have to try that out next
time I do a lot of collecting/processing.
time I do a lot of collecting/processing.
Rob
Oct 30, 2011, 10:32:14 PM10/30/11
to MyLifeOrganized for Android
Thanks for the clarification. I'll have to put in a feature
request. :)
I've also been evaluating Shuffle, which so far seems to be GTD
implemented to the letter. Shuffle isn't quite as feature-rich as MLO,
but some of the features that make MLO more attractive don't seem to
work quite as expected (for example, the inbox and contained
contexts). I'll have to try out MATSURU's workaround for the inbox,
and I hope the contexts get fixed soon. An attractive aspect of
Shuffle is that it's open source, so I could potentially add any
feature myself. I also tried ActionComplete but ran into some
unresolvable snags that turned out to be deal-breakers for me. But I
do have to give kudos to Boris (the ActionComplete developer) for
being incredibly responsive. He had some good suggestions and was
quite frank in explaining what his product can and cannot do, and what
is not likely to be added anytime soon.
On Oct 30, 8:20 pm, "conrad.mor...@gmail.com"
request. :)
I've also been evaluating Shuffle, which so far seems to be GTD
implemented to the letter. Shuffle isn't quite as feature-rich as MLO,
but some of the features that make MLO more attractive don't seem to
work quite as expected (for example, the inbox and contained
contexts). I'll have to try out MATSURU's workaround for the inbox,
and I hope the contexts get fixed soon. An attractive aspect of
Shuffle is that it's open source, so I could potentially add any
feature myself. I also tried ActionComplete but ran into some
unresolvable snags that turned out to be deal-breakers for me. But I
do have to give kudos to Boris (the ActionComplete developer) for
being incredibly responsive. He had some good suggestions and was
quite frank in explaining what his product can and cannot do, and what
is not likely to be added anytime soon.
On Oct 30, 8:20 pm, "conrad.mor...@gmail.com"
Rob
Oct 30, 2011, 10:44:41 PM10/30/11
to MyLifeOrganized for Android
Could you clarify why it would never work? I've tried 3 other apps
with GTD-style inboxes and they all made a task active after
processing it (i.e., setting any of its properties, such as context or
due date). If processing the task involves moving it to a different
place in the outline, then of course that task wouldn't be
automatically moved. But otherwise, I don't understand why the
"automatically remove from inbox after processing" feature couldn't be
implemented, or at least be added as an optional behavior if it's
undesirable for other personal organization methodologies.
On Oct 30, 8:24 pm, "conrad.mor...@gmail.com"
with GTD-style inboxes and they all made a task active after
processing it (i.e., setting any of its properties, such as context or
due date). If processing the task involves moving it to a different
place in the outline, then of course that task wouldn't be
automatically moved. But otherwise, I don't understand why the
"automatically remove from inbox after processing" feature couldn't be
implemented, or at least be added as an optional behavior if it's
undesirable for other personal organization methodologies.
On Oct 30, 8:24 pm, "conrad.mor...@gmail.com"
conrad...@gmail.com
Oct 30, 2011, 11:18:22 PM10/30/11
to mlo-a...@googlegroups.com
It has to do with the customization. Where would it move the tasks to once you assinged a context to it? Because the structure you make mlo into will most certainly not be mine. So where would it move it to? The reason I said you need to dig into mlo more to understand why that wont ever work is because you obviously have not created an mlo structure from scratch. If you did you would know that the sheer number of possible different designs would make what you ask a coding miricle... its simply not possible u less everyone created the exact same mlo structure and that's not why mlo is popular. Its popular because of the power behind it while still remaining customizable.
conrad...@gmail.com
Oct 30, 2011, 11:32:01 PM10/30/11
to mlo-a...@googlegroups.com
To add an example I have a context called "@sheriffs office" because I have a ton of items to do when I meet with him. Its a context but I do not have a folder for it other than "office" since I am pretty sure my design unique to me how would mlo handle me assigning a task to that context when it sits in my inbox? Where would it go? I wouldn't want mlo to automatically create a new branch in my outline and sometimes I place such items in a folder called "agenda" because it fits better there... how would mlo know how to handle that?
Rob
Oct 31, 2011, 12:23:43 AM10/31/11
to MyLifeOrganized for Android
Actually what I'm suggesting would work great along with your system.
You could still assign folders and contexts the same as you do now.
The only difference is that if you don't explicitly move a task to a
different folder, it would be automatically moved to the catch-all
"active tasks" folder instead of in the inbox.
In other GTD apps, the inbox is not a physical folder, it's a
collection of all tasks which only have a name assigned. That's
obviously not the only way to do it, but it works pretty well.
One aspect of GTD is that you shouldn't have to process a task more
than once, so that's why it's desirable to always desirable to remove
items from the inbox when processing--if you have a bunch of stuff
that stays in the inbox even after processing, you'll end up
processing it over and over again, every time you process the inbox.
I haven't studied other methodologies, but I don't think this way of
using the inbox would work any less well than the current inbox
behavior.
On Oct 30, 10:32 pm, "conrad.mor...@gmail.com"
You could still assign folders and contexts the same as you do now.
The only difference is that if you don't explicitly move a task to a
different folder, it would be automatically moved to the catch-all
"active tasks" folder instead of in the inbox.
In other GTD apps, the inbox is not a physical folder, it's a
collection of all tasks which only have a name assigned. That's
obviously not the only way to do it, but it works pretty well.
One aspect of GTD is that you shouldn't have to process a task more
than once, so that's why it's desirable to always desirable to remove
items from the inbox when processing--if you have a bunch of stuff
that stays in the inbox even after processing, you'll end up
processing it over and over again, every time you process the inbox.
I haven't studied other methodologies, but I don't think this way of
using the inbox would work any less well than the current inbox
behavior.
On Oct 30, 10:32 pm, "conrad.mor...@gmail.com"
conrad...@gmail.com
Oct 31, 2011, 7:10:35 AM10/31/11
to mlo-a...@googlegroups.com
I am sorry I am not seeing the need though. Because what you are proposing would just mean an extra step for me. I would create the task and it would appear in my inbox, which unlike moat people I do not have set to hidden, so any task I put in there is automatically an "active task" in the first place. It sits in there with a lesser priority because I have my inbox set to the least important and urgent, until I finally move it to the proper section in my outline (usually that evening if it wasn't handles that day). What you are suggesting means at the end if the day I would have to essentially clean out to "inboxes" at the end of the day (both inbox and active actions) to put my tasks in their proper priorities.
Remember this is not a gtd app. It works very well for that system (the best there is actually; I've tried ac, shuffle, and a couple others and they always lack the most important aspect of gtd which is the next action automation) but its not technically a gtd app. There are those who use Frank covey system and those like me who use a hybrid of gtd with their own tweaks.
Why don't you just make the inbox have a context called inbox and have that context "always closed" then check the option "only show open task" so your to do list wont show these tasks. Then when you assign them a different context, that is open, they become active. If you're like me and do a inbox clean at the end of the day most days, you could do a filtered view for all task with the inbox context and assign them as needed. This would meet your need without changing one of the core features of mlo (customization)
Remember this is not a gtd app. It works very well for that system (the best there is actually; I've tried ac, shuffle, and a couple others and they always lack the most important aspect of gtd which is the next action automation) but its not technically a gtd app. There are those who use Frank covey system and those like me who use a hybrid of gtd with their own tweaks.
Why don't you just make the inbox have a context called inbox and have that context "always closed" then check the option "only show open task" so your to do list wont show these tasks. Then when you assign them a different context, that is open, they become active. If you're like me and do a inbox clean at the end of the day most days, you could do a filtered view for all task with the inbox context and assign them as needed. This would meet your need without changing one of the core features of mlo (customization)
Rob
Oct 31, 2011, 1:20:08 PM10/31/11
to MyLifeOrganized for Android
Conrad, I must not be explaining it adequately, because the feature
I'm wishing for would not create any additional work for you. I had
also mentioned earlier that it could easily be a feature that is
enabled/disabled in the settings.
If you are one of the developers and there is a technical reason why
my suggestion cannot be implemented, then I respect that. But if you
are just a user like me, then I don't understand why you would take
such a strong position against another user's feature request. So far
the #1 turn-off to this app has not been any feature of the app
itself, but some of the negative attitudes I've seen on the forums.
These are supposed to be productive discussions, but over the past few
days I've seen over and over again that people would rather waste time
arguing instead of trying to be truly productive.
> Why don't you just make the inbox have a context called inbox and have that context "always closed" then check the option "only show open task" so your to do list wont show these tasks. Then when you assign them a different context, that is open, they become active. If you're like me and do a inbox clean at the end of the day most days, you could do a filtered view for all task with the inbox context and assign them as needed. This would meet your need without changing one of the core features of mlo (customization)
That's the problem--I don't think what you're suggesting now will work
for me in the first place because I only see options to view "Active
Actions" or "Active by Context." However, a task does not show up in
any of the "Active" views unless I have moved it out of the inbox. If
I were just using the inbox itself as a TODO list, then I'm not really
using any of the GTD-optimized features. But thank you for the
suggestion anyway.
On Oct 31, 6:10 am, "conrad.mor...@gmail.com"
I'm wishing for would not create any additional work for you. I had
also mentioned earlier that it could easily be a feature that is
enabled/disabled in the settings.
If you are one of the developers and there is a technical reason why
my suggestion cannot be implemented, then I respect that. But if you
are just a user like me, then I don't understand why you would take
such a strong position against another user's feature request. So far
the #1 turn-off to this app has not been any feature of the app
itself, but some of the negative attitudes I've seen on the forums.
These are supposed to be productive discussions, but over the past few
days I've seen over and over again that people would rather waste time
arguing instead of trying to be truly productive.
> Why don't you just make the inbox have a context called inbox and have that context "always closed" then check the option "only show open task" so your to do list wont show these tasks. Then when you assign them a different context, that is open, they become active. If you're like me and do a inbox clean at the end of the day most days, you could do a filtered view for all task with the inbox context and assign them as needed. This would meet your need without changing one of the core features of mlo (customization)
for me in the first place because I only see options to view "Active
Actions" or "Active by Context." However, a task does not show up in
any of the "Active" views unless I have moved it out of the inbox. If
I were just using the inbox itself as a TODO list, then I'm not really
using any of the GTD-optimized features. But thank you for the
suggestion anyway.
On Oct 31, 6:10 am, "conrad.mor...@gmail.com"
<conrad.mor...@gmail.com> wrote:
> I am sorry I am not seeing the need though. Because what you are proposing would just mean an extra step for me. I would create the task and it would appear in my inbox, which unlike moat people I do not have set to hidden, so any task I put in there is automatically an "active task" in the first place. It sits in there with a lesser priority because I have my inbox set to the least important and urgent, until I finally move it to the proper section in my outline (usually that evening if it wasn't handles that day). What you are suggesting means at the end if the day I would have to essentially clean out to "inboxes" at the end of the day (both inbox and active actions) to put my tasks in their proper priorities.
>
> Remember this is not a gtd app. It works very well for that system (the best there is actually; I've tried ac, shuffle, and a couple others and they always lack the most important aspect of gtd which is the next action automation) but its not technically a gtd app. There are those who use Frank covey system and those like me who use a hybrid of gtd with their own tweaks.
>
>
> I am sorry I am not seeing the need though. Because what you are proposing would just mean an extra step for me. I would create the task and it would appear in my inbox, which unlike moat people I do not have set to hidden, so any task I put in there is automatically an "active task" in the first place. It sits in there with a lesser priority because I have my inbox set to the least important and urgent, until I finally move it to the proper section in my outline (usually that evening if it wasn't handles that day). What you are suggesting means at the end if the day I would have to essentially clean out to "inboxes" at the end of the day (both inbox and active actions) to put my tasks in their proper priorities.
>
> Remember this is not a gtd app. It works very well for that system (the best there is actually; I've tried ac, shuffle, and a couple others and they always lack the most important aspect of gtd which is the next action automation) but its not technically a gtd app. There are those who use Frank covey system and those like me who use a hybrid of gtd with their own tweaks.
>
>
Lisa Stroyan
Oct 31, 2011, 4:39:48 PM10/31/11
to mlo-a...@googlegroups.com
NOTE: You are hitting a bug that will be fixed in the next release. Tasks in Inbox *should* be Active, as you say. but the Inbox from the Tutorial unfortunately has "Hide-In-Todo" set on it. If you remove that attribute they will become active.
(Apologies if someone else made this point, I haven't finished the thread but am running off elsewhere).
Lisa
Lisa
Rob
Oct 31, 2011, 5:39:47 PM10/31/11
to MyLifeOrganized for Android
Thanks, that helps a lot! It took me a couple minutes to figure out
how to remove the attribute (I was looking in settings at first, but
found it by long-pressing the Inbox in Outline view), but now the
tasks show up in the active views.
It would still be nice to have items removed from the inbox so my
inbox can be clear after processing the tasks, but I think I can abuse
the "(None)" context or use MATSURU's workaround for that purpose for
now.
On Oct 31, 3:39 pm, Lisa Stroyan <lstro...@gmail.com> wrote:
> NOTE: *You are hitting a bug that will be fixed in the next release. *Tasks
how to remove the attribute (I was looking in settings at first, but
found it by long-pressing the Inbox in Outline view), but now the
tasks show up in the active views.
It would still be nice to have items removed from the inbox so my
inbox can be clear after processing the tasks, but I think I can abuse
the "(None)" context or use MATSURU's workaround for that purpose for
now.
On Oct 31, 3:39 pm, Lisa Stroyan <lstro...@gmail.com> wrote:
> NOTE: *You are hitting a bug that will be fixed in the next release. *Tasks
Rob
Oct 31, 2011, 5:44:17 PM10/31/11
to MyLifeOrganized for Android
I forgot to mention, if anyone else is interested in the "remove from
inbox after processing" feature, you can vote for it on the MLO
UserVoice site:
http://mlo.uservoice.com/forums/9235-general/suggestions/2357839-android-remove-task-from-inbox-after-processing
inbox after processing" feature, you can vote for it on the MLO
UserVoice site:
http://mlo.uservoice.com/forums/9235-general/suggestions/2357839-android-remove-task-from-inbox-after-processing
Cirrob
Oct 31, 2011, 9:21:33 PM10/31/11
to MyLifeOrganized for Android
Sorry. Didnt meant to come off as stand offish. Its just that there
are dozens of other features that arent implimented yet, and I would
rather the full MLO for android be completed before we start to change
the way MLO works.
If the developer could impliment your suggestion as an option and it
wouldnt lag the development of the actual program, then I dont have a
problem with it. In the end, I dont have a say, I just want to make
sure the development stays on course. I myself see it as redundant
since your proposed" active actions" idea is already implimented in
the todo list. Creating a new folder for it is basically just another
inbox that would eventually have to be cleared out as the user moved
these tasks to their respective projects, folders, areas of focus or
whatnot in the organizer view (effectively touching each task twice
anyway).
It appears you are only using about 10% of MLO: you dump ideas into
your inbox, assign context to them and want that action alone to then
move it to another folder called active actions. However, mlo is more
powerful than that and you seem to be missing the forest for the
trees. It allows the user to create a task/project tree/outline of
folders and branches. It allows us to create any structure we like.
Each branch, project, or folder can then be assigned a context
priority and urgency. Furthermore, they can be assigned a star, flag,
or goal; automatically imparting all of those attributes onto its
subtasks. In the end, the user can then have his/her todo list
automatically filtered for next actions (active actions) and sorted
based on predefined priorities of the parrent task/project/folder time
of day and now, even location.
Your suggestions seems to bypass the meat and potatos of MLO and turn
it into something exactly like shuffle, action complete, next action
etc.
> > > > an "Active Tasks" area in the outline upon processing.- Hide quoted text -
>
> - Show quoted text -
are dozens of other features that arent implimented yet, and I would
rather the full MLO for android be completed before we start to change
the way MLO works.
If the developer could impliment your suggestion as an option and it
wouldnt lag the development of the actual program, then I dont have a
problem with it. In the end, I dont have a say, I just want to make
sure the development stays on course. I myself see it as redundant
since your proposed" active actions" idea is already implimented in
the todo list. Creating a new folder for it is basically just another
inbox that would eventually have to be cleared out as the user moved
these tasks to their respective projects, folders, areas of focus or
whatnot in the organizer view (effectively touching each task twice
anyway).
It appears you are only using about 10% of MLO: you dump ideas into
your inbox, assign context to them and want that action alone to then
move it to another folder called active actions. However, mlo is more
powerful than that and you seem to be missing the forest for the
trees. It allows the user to create a task/project tree/outline of
folders and branches. It allows us to create any structure we like.
Each branch, project, or folder can then be assigned a context
priority and urgency. Furthermore, they can be assigned a star, flag,
or goal; automatically imparting all of those attributes onto its
subtasks. In the end, the user can then have his/her todo list
automatically filtered for next actions (active actions) and sorted
based on predefined priorities of the parrent task/project/folder time
of day and now, even location.
Your suggestions seems to bypass the meat and potatos of MLO and turn
it into something exactly like shuffle, action complete, next action
etc.
>
> - Show quoted text -
Rob
Nov 1, 2011, 12:16:23 AM11/1/11
to MyLifeOrganized for Android
You're right that I'm not using all the features, but as everyone
keeps saying, the great thing about MLO is supposed to be that it
doesn't lock you into doing things a certain way. If I had to sit down
and learn about every feature and every use-case before being able to
use it, that would suggest the app is just too complex and poorly
designed for me to ever start using it. Really all I want is a tool
which I can start using right away, but which supports more advanced
features that I can start using as I need them.
I haven't tried Next Action, but even with the basic use-cases that
I've had so far, I've run into limitations in the other tools. For
example...
Shuffle: only supports one context per task. Some tasks can be
completed under multiple contexts--for example, @Ace and @Lowes. MLO
supports this, as well as much more advanced behavior via nested/
contained contexts, but the more advanced behavior seems to be broken
in MLO-Android (or maybe the feature just isn't as advanced as I would
have expected). I could probably get by with a single context if I
needed to, but it's less of a hassle if I don't have to deal with that
limitation.
ActionComplete: does not have an inbox or any optimized way of
simulating an inbox. It also does not support tasks nested more than
one level deep, so I'm concerned about not being able to manage future
complexity. Those two shortcomings give me the impression that it was
originally designed with a different methodology in mind, but people
have found ways to use it along with other tools to support a GTD-
style scheme. I already bought ActionComplete but would rather use an
app with proper inbox support (or, in the case of MLO, a workaround
that lets me simulate a proper inbox).
I've also used two tools on webOS. They are both pretty good, but
sadly the future of webOS is currently too hazy for me to trust my
organization system to it.
On Oct 31, 8:21 pm, Cirrob <conrad.mor...@gmail.com> wrote:
> Sorry. Didnt meant to come off as stand offish. Its just that there
> are dozens of other features that arent implimented yet, and I would see
keeps saying, the great thing about MLO is supposed to be that it
doesn't lock you into doing things a certain way. If I had to sit down
and learn about every feature and every use-case before being able to
use it, that would suggest the app is just too complex and poorly
designed for me to ever start using it. Really all I want is a tool
which I can start using right away, but which supports more advanced
features that I can start using as I need them.
I haven't tried Next Action, but even with the basic use-cases that
I've had so far, I've run into limitations in the other tools. For
example...
Shuffle: only supports one context per task. Some tasks can be
completed under multiple contexts--for example, @Ace and @Lowes. MLO
supports this, as well as much more advanced behavior via nested/
contained contexts, but the more advanced behavior seems to be broken
in MLO-Android (or maybe the feature just isn't as advanced as I would
have expected). I could probably get by with a single context if I
needed to, but it's less of a hassle if I don't have to deal with that
limitation.
ActionComplete: does not have an inbox or any optimized way of
simulating an inbox. It also does not support tasks nested more than
one level deep, so I'm concerned about not being able to manage future
complexity. Those two shortcomings give me the impression that it was
originally designed with a different methodology in mind, but people
have found ways to use it along with other tools to support a GTD-
style scheme. I already bought ActionComplete but would rather use an
app with proper inbox support (or, in the case of MLO, a workaround
that lets me simulate a proper inbox).
I've also used two tools on webOS. They are both pretty good, but
sadly the future of webOS is currently too hazy for me to trust my
organization system to it.
On Oct 31, 8:21 pm, Cirrob <conrad.mor...@gmail.com> wrote:
> Sorry. Didnt meant to come off as stand offish. Its just that there
conrad...@gmail.com
Nov 1, 2011, 10:17:29 AM11/1/11
to mlo-a...@googlegroups.com
Well I think where we differ is on the implementation: mlo is ultimately a task manager. Its focus is on the end result: a smarter to do list. It does this very well as long as the user puts forward at least some effort in the design of their outline. It seems you are more concerned with an inbox manager. I agree that it would be nice if mlo knew exactly where to place an inbox item as soon as I made a slight modification to it, but with the sheer number of different possibilities (based on the individual user designed outlines) I see this as virtually impossible for a smartphone app, hell I think its virtually impossible for a desktop app as well. Your alternative suggestion "active actions" folder misses the point of mlo.
I would suggest you make folders for your different @ contexts such as @home @calls etc. Then when working on your inbox instead of assigning a context to the task, move the task to the context folder so it imparts the context to the task and moves it out of your inbox. One touch of inbox items; properly assigns a context to it; and imparts other attributes such as priorities, time of day, and location... all automatically.
I would suggest you make folders for your different @ contexts such as @home @calls etc. Then when working on your inbox instead of assigning a context to the task, move the task to the context folder so it imparts the context to the task and moves it out of your inbox. One touch of inbox items; properly assigns a context to it; and imparts other attributes such as priorities, time of day, and location... all automatically.
MOK | MATSURU
Nov 1, 2011, 10:31:06 AM11/1/11
to mlo-a...@googlegroups.com
My simple suggestions:
No need to move tasks to other tree. Just keep everything in INBOX.
here's how:
1. create fast multiple tasks using the "Rapid task input" box on windows version. OR just key in your task on Android version as fast as you could. This is to clear things in your mind.
2. Go to Context view, you should be able to see a context that says "no context". Treat everything there as your inbox/task that are not yet process.
3. Process your task there. Rename, modify.....and Assign A Context.
4. Once context is assigned, your tasks will be out of the "No context" list.
5. If you wanna see your project, Assign your task as project under the project column and view them at the "project list"
Hope this is helpful.
just to let you know, i did not use this method. I thought of this idea while thinking about your situation. Thanks~! :-)
regards,
MOK | MATSURU
- MALAYSIA -
--------------------------
www.matsuru.net
Support me at http://fans.matsuru.net
--------------------------
Saito College
Tel : +603 – 7954 7200 (ext221)
Fax : +603 – 7954 7211
www.saito.edu.my
Be our fan on Facebook!
www.facebook.com/saitocollege
--------------------------
Rob
Nov 7, 2011, 5:32:23 PM11/7/11
to MyLifeOrganized for Android
Thanks MOK, along with the default configuration bug Lisa pointed out,
that's _exactly_ what I was looking for! This should be added to a
wiki or "Using MLO for GTD quick-start" article. :)
Also thanks to Conrad--I've started setting contexts on my folders,
and found out that feature works great for some of my other use-cases.
On Nov 1, 8:31 am, "MOK | MATSURU" <m...@matsuru.net> wrote:
> My simple suggestions:
>
> No need to move tasks to other tree. Just keep everything in INBOX.
> here's how:
>
> 1. create fast multiple tasks using the "Rapid task input" box on windows
> version. OR just key in your task on Android version as fast as you could.
> This is to clear things in your mind.
> 2. Go to Context view, you should be able to see a context that says "no
> context". Treat everything there as your inbox/task that are not yet
> process.
> 3. Process your task there. Rename, modify.....and Assign A Context.
> 4. Once context is assigned, your tasks will be out of the "No context"
> list.
> 5. If you wanna see your project, Assign your task as project under the
> project column and view them at the "project list"
>
> Hope this is helpful.
>
> just to let you know, i did not use this method. I thought of this idea
> while thinking about your situation. Thanks~! :-)
>
> regards,
>
> MOK | MATSURU
> - MALAYSIA -
> --------------------------
> *www.matsuru.net
> Support me athttp://fans.matsuru.net
>
> On Tue, Nov 1, 2011 at 10:17 PM, conrad.mor...@gmail.com <
> ...
>
> read more »
that's _exactly_ what I was looking for! This should be added to a
wiki or "Using MLO for GTD quick-start" article. :)
Also thanks to Conrad--I've started setting contexts on my folders,
and found out that feature works great for some of my other use-cases.
On Nov 1, 8:31 am, "MOK | MATSURU" <m...@matsuru.net> wrote:
> My simple suggestions:
>
> No need to move tasks to other tree. Just keep everything in INBOX.
> here's how:
>
> 1. create fast multiple tasks using the "Rapid task input" box on windows
> version. OR just key in your task on Android version as fast as you could.
> This is to clear things in your mind.
> 2. Go to Context view, you should be able to see a context that says "no
> context". Treat everything there as your inbox/task that are not yet
> process.
> 3. Process your task there. Rename, modify.....and Assign A Context.
> 4. Once context is assigned, your tasks will be out of the "No context"
> list.
> 5. If you wanna see your project, Assign your task as project under the
> project column and view them at the "project list"
>
> Hope this is helpful.
>
> just to let you know, i did not use this method. I thought of this idea
> while thinking about your situation. Thanks~! :-)
>
> regards,
>
> MOK | MATSURU
> - MALAYSIA -
> --------------------------
> Support me athttp://fans.matsuru.net
> --------------------------
> Saito College
> Tel : +603 – 7954 7200 (ext221)
> Fax : +603 – 7954 7211www.saito.edu.my
> Be our fan on Facebook!www.facebook.com/saitocollege
> *--------------------------
> Saito College
> Tel : +603 – 7954 7200 (ext221)
> Fax : +603 – 7954 7211www.saito.edu.my
> Be our fan on Facebook!www.facebook.com/saitocollege
>
> On Tue, Nov 1, 2011 at 10:17 PM, conrad.mor...@gmail.com <
>
> read more »
Reply all
Reply to author
Forward
0 new messages