<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/dvorcode/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/dvorcode/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 30 Jun 2010 01:28:02 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/dvorcode/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Make Jar Apple-compliant</title><link>https://sourceforge.net/p/dvorcode/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When running under MacOS X in GUI mode, the application menu is named after the main class name "net.sf.dvorcode.Main". The Jar should be packaged such that MacOS gives it a proper name, as explained in Apple's Java developer guidelines. An Icon would be nice too.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Wed, 30 Jun 2010 01:28:02 -0000</pubDate><guid>https://sourceforge.net66c92bf9f4732b21c7387d4486f94bc5be18d6cb</guid></item><item><title>Package libs in same Jar</title><link>https://sourceforge.net/p/dvorcode/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if the included libraries were incorporated into the one dvorcode.jar file. This would make distribution and installation even more trivial, since there would not be a need to keep 3 files in a special directory relationship.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Wed, 17 Sep 2008 04:13:04 -0000</pubDate><guid>https://sourceforge.net573a7d93d2f3dd0dc45569a612ae9eaab8698fee</guid></item><item><title>Use Factory pattern to decouple transcoder from UI</title><link>https://sourceforge.net/p/dvorcode/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The GUI/CLI are fairly tightly coupled to the Dvorcode encoder. This is fine because the program is only supposed to handle one type of encoding. However it would probably make a better design to use a trans-coder interface and a factory pattern to decouple the user-interface classes from the Dvorcode class. That way, the UI stuff could be re-used for different trans-coder projects (just slot in a replacement class that implements the trans-coder interface).&lt;/p&gt;
&lt;p&gt;This should be a low-priority code-improvement exercise, as it will add zero features to the program as well as introduce some complexity.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Wed, 17 Sep 2008 02:08:01 -0000</pubDate><guid>https://sourceforge.net42ecb3d65f42e940bda0dbf3725d608a88b4024b</guid></item><item><title>Highlight the latest transcoded entry in the answerArea </title><link>https://sourceforge.net/p/dvorcode/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The newest (top) entry should be highlighted without the text scroller being the active GUI element, if this is possible in Swing? This will make it more clear which answer was newest.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Tue, 09 Sep 2008 05:03:23 -0000</pubDate><guid>https://sourceforge.net2d23f4a6fa119772362eba86990742d984d870d3</guid></item><item><title>Make the actionListener functions into Swing Actions</title><link>https://sourceforge.net/p/dvorcode/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;To facilitate item #2101401 the GUI event handling code needs to abstract the actions from the events. Then menu items and button actions can both be pointed at the same Actions, and extra features such as action enable/disablement and keyboard bindings can be added.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Tue, 09 Sep 2008 05:01:51 -0000</pubDate><guid>https://sourceforge.net636fcb68479d41c62e0d3387d4d9465dc2f4beff</guid></item><item><title>Add pull-down menus to be Apple HCI compliant</title><link>https://sourceforge.net/p/dvorcode/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Need at minimum File -&amp;gt; Quit and also Help.&lt;/p&gt;
&lt;p&gt;It would probably be wise to test this code out on an actual Mac, but can start by reading Apple's Java guidlines.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Tue, 09 Sep 2008 04:59:23 -0000</pubDate><guid>https://sourceforge.netbba47cf1d63dfeb5d05499252810b719109f9363</guid></item><item><title>Get rid of code smells</title><link>https://sourceforge.net/p/dvorcode/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The Main.main() method still has some code smells, mainly due to the way that the command-line options have been parsed. It needs cleaning up possibly breaking down into subroutines to reduce the repeated code as well.&lt;/p&gt;
&lt;p&gt;Probably research how other people have tackled this problem, surely someone's done a much more elegant job?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lockhart</dc:creator><pubDate>Tue, 09 Sep 2008 04:57:34 -0000</pubDate><guid>https://sourceforge.neta73f7650ef1217f7de99acf7000db6567558785e</guid></item></channel></rss>