Dwight, Is there someone in charge of gather similar requests? I mean, very often, there are request that are formulated differently but are, indeed, the same need. (It can be an old request). The problem is that it underestimates the number of votes. For this reason, I don't use the MLO voic anymore. Olivier
Le vendredi 4 avril 2014 13:09:31 UTC+2, Dwight Arthur a écrit : > > Hi, Stephen. I just wanted to point out that nobody tracks how many > comments in this forum say that they are voting for some enhancement. If > you want to vote and have it count you should use > http://mlo.uservoice.com > -Dwight > Mlo betazoid on Android sgn2 > > On Apr 3, 2014, ssintay <[email protected] <javascript:>> wrote: >> >> I just wanted to add my vote for this capability to be added in the >> future. >> >> On Saturday, January 19, 2013 11:38:30 AM UTC-7, Brad Konia wrote: >>> >>> I agree with the previous postings requesting logical linking >>> functionality within MLO. I've also used Ultra Recall and I find their >>> logical linking implementation to be nearly perfect, as well as extremely >>> simple. >>> >>> This feature would not require any changes to the hierarchical >>> structure, nor would it introduce any added complexity. You would simply be >>> creating aliases or pointers to specific branches in the hierarchy, at >>> other locations in the hierarchy. This would be analogous to a symbolic >>> link within a Linux file system, which is also hierarchical. >>> >>> Implementing this functionality would make it much easier to create task >>> hierarchies without having to stress over where to place each task, when it >>> could logically be placed in more than one location within the hierarchy. >>> >>> I realize you can get much of this functionality using contexts. The >>> problem is, the MLO user interface is designed primarily around the task >>> hierarchy, not contexts. I tried using a flat task list and organizing >>> everything by context and it didn't work out. The context editor allows you >>> to include contexts within other contexts, but there's no way to build an >>> inclusion hierarchy. It just allows you to enter a list if contexts that >>> are included within another context. Additionally, when you add a new task, >>> the context selector displays every context you've created in one long >>> list, rather than allowing you to select contexts hierarchically. If you >>> try to use contexts as your primary organizational strategy within MLO, >>> you'll end up with a big mess that will ultimately be too cumbersome to use >>> efficiently. >>> >>> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/f2dae4e0-0265-414e-9a52-abad4693bbca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
