Can't find rajjan's post to simulate start date
(closed account) says:
Can someone point me to it? I've looked and searched for almost an hour and can't find it.
Thanks
Thanks
You can find it in the blog: http://blog.rememberthemilk.com/2009/04/tips-tricks-tuesday-using-sleeper-tags/
Please observe that copying from the blog gives you the wrong type of quotation marks, type them yourself instead.
Please observe that copying from the blog gives you the wrong type of quotation marks, type them yourself instead.
(closed account) says:
Thanks!
jsellen says:
However, I use something that I find much easier than suggested, to use the due date that is there. This works if you use smartlists for your important items.
My 'next action' list(s) are smartlist constructed like this:
((tag:@call and tag:na) or (tag:@call and tag:tickler and dueBefore:now))
Therefore, If I want to call to schedule an appointment 2 weeks from now, I tag it @call, tickler, and set a due date of 2 weeks. In two weeks it pops into my 'next action' list automagically. It is true that the actual tag of the item never changes to 'na' from 'tickler', but it's on the right list at the right time, so it's a small price to pay.
The main difference from rajjan's suggestion is that the 'due' date of mine is the 'sleeper' date in his system. The advantage of mine is I can have it pop up whenever I want, without having to modify my smartlist (which is important for me, since I'm sharing tasks, I can't force a change to everyone's smartlist). The advantage of rajjan's suggestion is that you don't have to separately manage the actual due date.
--
The real tragedy of all of this is that we have to go through such convoluted gyrations to accomplish something that would be *trivial* for developers. There is already a due date field that has input validation, etc. ALL RTM HAS TO DO IS ADD ANOTHER ONE and call it 'start date'. I think the fact that they acknowledged this 'tip and trick', but refuse to address the underlying problem is a bit dodgy. They're promoting the 'flexibility and adaptability' of the RTM system by highlighting tricks like rajjan's.
Imagine if I was an automobile manufacturer and I produced a car with a very fragile brake system. But then I promoted a 'tips and tricks' from a user suggesting that the handbrake/emergency brake could be used in situations when the regular brake failed, and tried to sell that as a good thing!!!!
I just wish RTM would get around to fixing some of these really trivial features in the plain, vanilla, non-twitter, non-iphone, non-gmail, core RTM functionality. I'd then get on board with my support. It would then be worth more than the $ they are asking for.
My 'next action' list(s) are smartlist constructed like this:
((tag:@call and tag:na) or (tag:@call and tag:tickler and dueBefore:now))
Therefore, If I want to call to schedule an appointment 2 weeks from now, I tag it @call, tickler, and set a due date of 2 weeks. In two weeks it pops into my 'next action' list automagically. It is true that the actual tag of the item never changes to 'na' from 'tickler', but it's on the right list at the right time, so it's a small price to pay.
The main difference from rajjan's suggestion is that the 'due' date of mine is the 'sleeper' date in his system. The advantage of mine is I can have it pop up whenever I want, without having to modify my smartlist (which is important for me, since I'm sharing tasks, I can't force a change to everyone's smartlist). The advantage of rajjan's suggestion is that you don't have to separately manage the actual due date.
--
The real tragedy of all of this is that we have to go through such convoluted gyrations to accomplish something that would be *trivial* for developers. There is already a due date field that has input validation, etc. ALL RTM HAS TO DO IS ADD ANOTHER ONE and call it 'start date'. I think the fact that they acknowledged this 'tip and trick', but refuse to address the underlying problem is a bit dodgy. They're promoting the 'flexibility and adaptability' of the RTM system by highlighting tricks like rajjan's.
Imagine if I was an automobile manufacturer and I produced a car with a very fragile brake system. But then I promoted a 'tips and tricks' from a user suggesting that the handbrake/emergency brake could be used in situations when the regular brake failed, and tried to sell that as a good thing!!!!
I just wish RTM would get around to fixing some of these really trivial features in the plain, vanilla, non-twitter, non-iphone, non-gmail, core RTM functionality. I'd then get on board with my support. It would then be worth more than the $ they are asking for.
jsellen says:
Don't forget the many requests here:
http://www.rememberthemilk.com/forums/ideas/2177/
http://www.rememberthemilk.com/forums/ideas/2177/
Log in
to post a reply.