<?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/jpreference/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/jpreference/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 29 Feb 2004 20:07:56 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jpreference/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>JPreference architecture, are we going the right way?</title><link>https://sourceforge.net/p/jpreference/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Presently Jpreference is unable to load any preferences &lt;br /&gt;
from flat files, unless we initiate default preferences in &lt;br /&gt;
PreferenceManager. &lt;br /&gt;
Problem domain: &lt;br /&gt;
We cannot load any preferences until unless we define &lt;br /&gt;
them before calling load method. This is quite painful, as &lt;br /&gt;
the application developer should code lots of code to &lt;br /&gt;
initiate all the default preferences. &lt;br /&gt;
It also raises other concerns apart from coding, why we &lt;br /&gt;
need to initalize preference objects without knowing &lt;br /&gt;
whether we need them really?&lt;br /&gt;
Basic idea behind preference: It is to give more power &lt;br /&gt;
to the user, so that he can save his setting for his next &lt;br /&gt;
uses. (This is just my idea)&lt;br /&gt;
So if the user really didn't use the default initalized &lt;br /&gt;
preference objects then they are eating memory without &lt;br /&gt;
reason.&lt;/p&gt;
&lt;p&gt;Could be solution:&lt;br /&gt;
load method loads all preferences as String values.&lt;br /&gt;
What does that really mean? &lt;br /&gt;
So load method does 2 jobs:&lt;br /&gt;
1. Creates new preference objects when they are not &lt;br /&gt;
created by application.&lt;br /&gt;
2. If preference object already created by application, &lt;br /&gt;
then replaces the old value with newly read value.&lt;/p&gt;
&lt;p&gt;The next question, What will happen to Object types?&lt;br /&gt;
Preferences are specific to the components which use &lt;br /&gt;
them, then let them try to cast them to their required &lt;br /&gt;
types. (As any type values should be written to a file as &lt;br /&gt;
a String)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gudapati Praveen Kumar</dc:creator><pubDate>Sun, 29 Feb 2004 20:07:56 -0000</pubDate><guid>https://sourceforge.net75c3e1a1c8ae61c78ceee36e9f77e2a616c94725</guid></item><item><title>Convert Vector preference type to List type</title><link>https://sourceforge.net/p/jpreference/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;You should abstract away from Vector, and use the List&lt;br /&gt;
interface... most people prefer a more generic way of&lt;br /&gt;
accessing a list of values.&lt;/p&gt;
&lt;p&gt;Especially since preferences are typically&lt;br /&gt;
low-bandwidth calls during execution (no tight loops&lt;br /&gt;
typically).. and whatever specified type they use to&lt;br /&gt;
initialize their list preference, it will continue to&lt;br /&gt;
be that type throughout the system, if you use clone to&lt;br /&gt;
reinitialize a List.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Dearman</dc:creator><pubDate>Tue, 10 Feb 2004 01:08:11 -0000</pubDate><guid>https://sourceforge.netf392acc780574bd70a743f774584d30f956a3fa3</guid></item></channel></rss>