<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/heffalump/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/heffalump/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/heffalump/feature-requests/</id><updated>2007-12-07T19:29:00Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Requirements field on items which require physical review</title><link href="https://sourceforge.net/p/heffalump/feature-requests/10/" rel="alternate"/><published>2007-12-07T19:29:00Z</published><updated>2007-12-07T19:29:00Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net3342df6808bb7c4592a53091f3b2d8ba4a395131</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'd like to use Heffalump to learn how to tie some useful knots (call me sad).  I'd like to be able to specify that the item requires a physical resource - a piece of string, or whatever else - and have Heffalump warn me when I start my review that I'll need to prepare whatever bits and bobs for the items due that session.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Configurable startup behaviour</title><link href="https://sourceforge.net/p/heffalump/feature-requests/9/" rel="alternate"/><published>2007-11-15T13:03:46Z</published><updated>2007-11-15T13:03:46Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net108ce89fa9426373d04975cef3fdb18fd8af6429</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Give me a preference that lets me choose what happens after autoload - show the database summary window or dive straight into reviewing due items.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Preferences dialog should exist</title><link href="https://sourceforge.net/p/heffalump/feature-requests/8/" rel="alternate"/><published>2007-10-30T11:38:53Z</published><updated>2007-10-30T11:38:53Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.nete8bafdf1215aa44e1e8179aa0c5bf92242d86d52</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Even though there are precious few preferences now (I count three hard-wired ones), more will come.  The earlier a framework exists for editing them the better.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Keyboard shortcuts for standard/common actions</title><link href="https://sourceforge.net/p/heffalump/feature-requests/7/" rel="alternate"/><published>2007-10-30T11:32:15Z</published><updated>2007-10-30T11:32:15Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net06fc827a4f7684e23b3ab5648fe74639a912123f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Heffalump is almost completely unusable without a mouse at the moment.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Allow (de)activation of items</title><link href="https://sourceforge.net/p/heffalump/feature-requests/6/" rel="alternate"/><published>2007-10-30T11:17:54Z</published><updated>2007-10-30T11:17:54Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net6f61d3cb933b0780c529b29aed51c78d760cfb61</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;After a mass addition of items it would be convenient to be able to stagger the feed of those items into the learning process.  Items should carry a boolean flag indicating whether they're active or not.  An active item behaves as before; an inactive one is simply never eligible for review.  If an active item is deactivated it maintains its review scheduler info and is just treated like any other item when reactivated.&lt;/p&gt;
&lt;p&gt;Changes:&lt;br /&gt;
- new column in browser (or perhaps a second browser) to display state of inactive items; could also just render them grayed out in the JTable&lt;br /&gt;
- new checkbox in the add/edit item window; preferably sticky, so that it need only be checked/unchecked once during a mass add&lt;br /&gt;
- perhaps a button on the browser or a menu item to make activation of multiple items a quick job&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Schedule reviews for the middle of the night</title><link href="https://sourceforge.net/p/heffalump/feature-requests/5/" rel="alternate"/><published>2007-09-30T08:43:03Z</published><updated>2007-09-30T08:43:03Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net9e254adb7f3e8a3a53f9e20563c484010e704156</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Reviews are currently scheduled in whole days and the "next review due" times depend on the time an item was added or last reviewed.  As an item gets reviewed more, the time of day when it becomes eligible for review creeps forward, e.g. 10am (time it was added), 10:02, 10:05, 10:08 etc.  If the user reviews items at the same time every day then items will gently creep out of that window and get reviewed a day later than scheduled.  If the user reviews at arbitrary times of day then any number of items might be eligible.&lt;/p&gt;
&lt;p&gt;Reviews should instead be scheduled only down to the day, and the time of day that all items become eligible should be chosen by the user.  That way the user can pick a time when they're highly likely to be asleep (or to be doing some other non-review activity) and all items will be eligible for the whole day.&lt;/p&gt;
&lt;p&gt;This doesn't ensure item review schedules are honoured, of course.  An item might be reviewed at 9pm one night, scheduled for the next day, become eligible at 4am and get reviewed again at 10am, leaving only 13 hours between reviews instead of a day.  Similarly, an item reviewed at 10am, becoming eligible 4am the next day and being reviewed at 9pm has a review interval of 35 hours.  The best way to ensure that the schedule is followed closely is to carry out reviews at a similar time every day.  This doesn't really matter beyond the first couple of reviews though, because the deviation from the schedule becomes fairly insignificant once review intervals exceed one day.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>File-&gt;Open Recent-&gt;... should be there</title><link href="https://sourceforge.net/p/heffalump/feature-requests/4/" rel="alternate"/><published>2007-08-15T15:52:40Z</published><updated>2007-08-15T15:52:40Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.nete72facc74be6155585cf031e296933e797a5e7fd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;nuff said&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Reviews should be timed and pauseable</title><link href="https://sourceforge.net/p/heffalump/feature-requests/3/" rel="alternate"/><published>2007-08-15T15:39:30Z</published><updated>2007-08-15T15:39:30Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.netb2720e8fc53ac8a6850acdda7a8d7e47ea69cc4f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;So that statistics can be generated telling you how long you spent reviewing a given item, predicting future workload etc. etc. further down the line.  If reviews are timed they should also be pauseable.  And if they're timed, perhaps there's an argument for objectively determining the recall grade when it depends on hesitation.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should have undo in "Add Item" window</title><link href="https://sourceforge.net/p/heffalump/feature-requests/2/" rel="alternate"/><published>2007-08-15T15:21:26Z</published><updated>2007-08-15T15:21:26Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.netb3ee5ee5340743b891c3bf92b1c853d997163fdd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Nuff said, except that firstly there's no menubar on that frame yet (but eventually there probably will be), and secondly perhaps this is a micro-edit like bug #1774767.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should be possible to rename tags</title><link href="https://sourceforge.net/p/heffalump/feature-requests/1/" rel="alternate"/><published>2007-08-15T15:03:37Z</published><updated>2007-08-15T15:03:37Z</updated><author><name>zw</name><uri>https://sourceforge.net/u/iwilcox/</uri></author><id>https://sourceforge.net24262ace3b628390379ec3827db7f3d096f6cf13</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Tags should be shared so that a name change changes all others. Handle case of adding dupe, or renaming to cause dupe.&lt;/p&gt;
&lt;p&gt;Minor problem with fixing this: if a user edits a tag in the current tag editor it's not clear what he wants.  Maybe he's just trying to change the tags assigned to the item rather than trying to rename that tag on all existing items.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>