![]() It is not (nor may ever be) available on iOS or the new Web Beta. As far as I know, one is only able to view this nested tag structure on Desktop clients and Android.On the other hand, when a task is moved from one notebook to another, that involves one action - the deed is done. One has to have the proper tagging protocol in place. When moving a task from one category, priority or date context to another, one not only needs to drag and drop a task to a new tag (or tag it as such on mobile devices - from within a note) - one also needs to un-tag the previous tag, lest the task fall under conflicting dates, priorities etc.When compared with the Notebook/ Reminders list setup in Part 2, here are some notable minuses of the tagging dynamic: When we consider a huge core concept of Kanban - " Visualize your workflow" - in so far as a single task relates to all others, it is helpful to have it appear in just one place when looking at the scope of your tasks - the bird's-eye view. In fact the Kanban Calendar structure intuitively strips all of that duplicity away. (which are secondary contexts) it's best to keep it simple and have a task in one context. with multiple tags, which would be very helpful indeed - but when it comes to tasks, other than having "GTD" contexts similar to etc. You see, any reference material you may have in Evernote is a completely different ball game: You may wish to tag various kinds of documents, web-clippings, ideas, etc. To have a task appear in more than one main context would detract from what makes it such a low-maintenance, fuss-free system. I say this for one simple reason: if you've been following how I set Kanban Calendar up in a variety of wildly different apps - by now you will have caught on that the actual strength of this system lies in any particular task only really appearing in one context. Sorry to get you all excited about it and then drop a bomb on you. ![]() They do not contain any notes - they are there simply to create structure.īefore I go any further (and this might be an anticlimax to many) - the previously mentioned advantage of using tags to have a task appear in more than one context, is pretty much redundant (or very minimal) here. Except that the BACKLOGGED, TODAY and CALENDAR tags are simply place holders under which to nest (drag and drop) the component section, priority and date tags. In its essence, t he basic tag structure setup here is a mirror image of P art 2 in this series - in other words, each tag context seen here, is an exact replicate of its stack/ notebook counterpart, containing the same tasks. For our purposes here, I would liken tags in Evernote to these midi-chlorians: The higher the count, the more "contexts" your notes/ tasks can be found in. Though the Force was thought to flow through every living thing, its power could only be harnessed by beings described as "Force-sensitive." This Force-sensitivity was correlated with, and sometimes attributed to, a high count of internal microorganisms called midi-chlorians that were found in a Force-sensitive's blood: the higher the count, the greater the being's potential Force ability.īy the way, " ubiquitous" is a fancy word I learned a little over a year ago - meaning " to be present or found everywhere". The Force was a metaphysical, spiritual, omnipotent and ubiquitous power that held enormous importance for both the Jedi and Sith monastic orders. ![]() If this is too cheesy for you: hit the space bar once (on desktop).įor those Star Wars fans: An extract from the Star Wars Wiki: When one tags a note (or in this case a task) with more than one tag, that note takes on a super power - the ability to be in more than one place at the same time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |