From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilya Shlyakhter Subject: suggestion: balance tracking Date: Sat, 8 Aug 2009 23:13:44 +0200 Message-ID: <4b11f87e0908081413uf714a73g48bbfbb559e41ed8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZtEd-0003Y1-1I for emacs-orgmode@gnu.org; Sat, 08 Aug 2009 17:13:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZtEY-0003Vj-KQ for emacs-orgmode@gnu.org; Sat, 08 Aug 2009 17:13:50 -0400 Received: from [199.232.76.173] (port=47920 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZtEY-0003Vg-E4 for emacs-orgmode@gnu.org; Sat, 08 Aug 2009 17:13:46 -0400 Received: from mail-ew0-f207.google.com ([209.85.219.207]:40545) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZtEY-0008Nw-2f for emacs-orgmode@gnu.org; Sat, 08 Aug 2009 17:13:46 -0400 Received: by ewy3 with SMTP id 3so1406308ewy.31 for ; Sat, 08 Aug 2009 14:13:45 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode A small extension to orgmode would let you track how you're balancing your time among your projects: whether you're spending more than you want on some, and less than you want on others. It would work as follows. For any node you can define a property "goal", saying how many todo's you want to complete in that subtree per day (on average). For each todo item that you mark DONE, you would include in the entry the date of its completion. Then, an orgmode command would, for each subtree with a "goal" property at the root, compute how many todo's you completed in that subtree within the last 2 weeks (say), and would report those subtrees where the average # of todo's per day falls below the goal. The report would be sorted, with the most neglected goals first. Some todo's could be worth more than others; a todo could have a "goalvalue" property, in which case that property's value would be added to the subtree's sum, instead of the default value of 1. E.g. this could represent hours spent. The same mechanism could be used to check e.g. the balance of a budget (whether you're spending more/less money than you would like on some areas).