Applied nic's patch to fix #8. Next actions now only get marked with the staleness flag if they '''don't''' have a due date.

git-svn-id: http://www.rousette.org.uk/svn/tracks-repos/trunk@94 a4c988fc-2ded-0310-b66e-134b36920a42

tracks/app/views/context/_show_items.rhtml

@@ -25,7 +25,11 @@
   <!-- end div.checkbox -->
   </div>
   <!-- start of div which has a class 'description' or 'stale_7d', 'stale_14d' etc -->
-  <%= staleness(item.created) %>
+  <% if item.due %>
+    <div class="description">
+  <% else %>
+    <%= staleness(item.created) %>
+  <% end %>
 	<%= due_date( item.due ) %> 
 	<%= item.description %>
 	<% if item.project_id %>

tracks/app/views/project/_show_items.rhtml

@@ -25,7 +25,12 @@
   </div>
   <!-- end div.checkbox -->
   <!-- start of div which has a class 'description' or 'stale_7d', 'stale_14d' etc -->
-  <%= staleness(item.created) %>
+  <% if item.due %>
+    <div class="description">
+  <% else %>
+    <%= staleness(item.created) %>
+  <% end %>
+ 
 	<%= due_date( item.due ) %> 
 	<%= item.description %>
 	<% if item.context_id %>

tracks/app/views/todo/_show_items.rhtml

@@ -25,7 +25,11 @@
   <input type="checkbox" name="item_id" value="<%= item.id %>" onclick="document.forms['checkbox-notdone-<%= item.id %>'].onsubmit();" />
   </div>
   <!-- start of div which has a class 'description' or 'stale_7d', 'stale_14d' etc -->
-	<%= staleness(item.created) %>
+  <% if item.due %>
+    <div class="description">
+  <% else %>
+    <%= staleness(item.created) %>
+  <% end %>
 	<%= due_date( item.due ) %> 
 	<%= item.description %>
 	<% if item.project_id %>

tracks/doc/CHANGENOTES.txt

@@ -27,9 +27,7 @@ Project wiki: <http://www.rousette.org.uk/projects/wiki/>
 13. Can now uncheck actions from the completed actions list, so that they dynamically appear back in the uncompleted actions area.
 14. A tiny improvement: the toggling of the individual notes now uses Element.toggle from prototype.js, so it doesn't have to be an onLoad property of the body tag. This means that you don't get the notes flashing before they are hidden when you load or reload a page.
 15. All the adding, updating, deleting and marking actions done is performed using Ajax, so happens without needing to refresh the page.
-16. There's a new setting in settings.yml (staleness_starts) which defines the number of days before which actions get marked as stale. Let's say you set it to 7 days. Actions created between 7 and 14 days ago get marked pale yellow, those created between 14 and 28 days ago (staleness_starts * 2) get
-marked darker yellow, and those created more than 28 days ago (staleness_starts * 3) are fluorescent
-yellow!
+16. There's a new setting in settings.yml ('staleness_starts') which defines the number of days before which actions get marked as stale. Let's say you set it to 7 days. Actions created between 7 and 14 days ago get marked pale yellow, those created between 14 and 28 days ago (staleness_starts * 2) get marked darker yellow, and those created more than 28 days ago (staleness_starts * 3) are fluorescent yellow! This is only applied to items without a due date, so you can add items to be done some time in the future without getting yellow splashed all over the place (thanks to nic for the patch to restrict to items with no due date).
 17. Contexts and projects can now be sorted in any order you like. Arrow buttons on the /contexts and /projects pages let you move an item to the top, up, down or to the bottom. For contexts, this affects the order in which they sort on the home page.
 18. You can mark projects as completed (by editing the project on /projects). In the 'sidebar' active and completed projects are shown separately, but you can still view the completed project.
 19. New images (from eclipse.org) for the edit, delete, notes and up, down, top and bottom buttons. I've made a greyscale version for the default, then the coloured version gets loaded when the mouse is hovering over the button.