1 files changed, 63 insertions, 0 deletions

diff --git a/development/feature_plan/opie-featurelist.xml b/development/feature_plan/opie-featurelist.xml
index 43f2c77..2e9e3d2 100644
--- a/development/feature_plan/opie-featurelist.xml
+++ b/development/feature_plan/opie-featurelist.xml
@@ -1,261 +1,324 @@
 <?xml version = '1.0' encoding = 'iso-8859-1'?>
 <!DOCTYPE features SYSTEM "opie-features.dtd">
 <!--
 
 Copied from KDE and (C) by Cornelius Schumacher
 
 This file serves as central repository of planned KDE features. It's parsed by
 the PHP scripts in "opie-features.inc" which are used by "kde-3.2-features.html" to
 generate HTML versions for the web.
 
 If you plan to add a feature to KDE please add it to this file. A feature can
 have one of three status types: "todo", "inprogress", "done". Please update
 the status from time to time. For a release there shouldn't be any features
 with other states than "done". If you can't complete a feature for a release
 please move the feature to the next release. The "target" attribute specifies
 for which release the feature should be finished. At the moment only the value
 "3.2" is evaluated, but we will add pages showing the features for later
 versions as needed.
 
 Each feature consists of a summary giving a short description what the feature is
 about and one or more responsible persons.
 
 A draft for a DTD of the features file can be found in "kde-features.dtd". Use
 "xmllint -valid -noout kde-features.xml" to validate the xml file against the
 DTD. If there are errors in the XML document they will be shown, if not the
 command will not output anything.
 
 if you have questions or comments please post them to the mailing list or contact
 Cornelius Schumacher <schumacher@kde.org>.
 
 --><features>
  <category name="Library" >
   <feature status="todo" target="1.2" >
    <summary>merge with Qtopia 1.7 library if possible</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="BigScreen" >
    <summary>Add show which performs window manager tasks. Places the window right and
 and with the right size for big screens.</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="1.2" >
    <summary>Icon Themes</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Launcher" >
   <feature status="todo" target="BigScreen" >
    <summary>Background picture displayed in different modes</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Implement a launcher (and/or application class) which is able to auto-position and -resize a fixed number of concurrent application windows (e.g. 4 apps per screen)</summary>
+   <responsible email="" name="" />
+  </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Add width- and height-customizability for 
+
+ * window titlebar
+ * window borders
+ * taskbar
+
+
+</summary>
+   <responsible email="" name="" />
+  </feature>
  </category>
  <category name="Addressbook" />
  <category name="All" >
   <feature status="todo" target="1.2" >
    <summary>Make all applications use more from libopie and see what is commonly used and create a common implementation if necessary.</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="BigScreen" >
    <summary>Kill showMaximized and use QPEApplication function to show the widget. This allows
 both X11 and BigScreen Qt/E to look and behave better on bigger screens</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="1.2" >
    <summary>security considerations and flaw search
 
 -Search for memcopies, printf, snprinft, strcat, and replace with their n functions
 -Search for misuse and unguarded usage of system
 -Kiosk mode?</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Toolbuttons are too big and have too much spacing.</summary>
+   <responsible email="" name="" />
+  </feature>
  </category>
  <category name="libopie" >
   <feature status="todo" target="BigScreen" >
    <summary>Write OSplitter.
 OSplitter is a widget that adjusts itself to the screen size. On small handheld displays it's a OTabWidget and on bigger screen and on resize it will be a real QSplitter if available
 or QHBoxLayout. Currently only horizontal mode is planed.
 
 Primary use: AdvancedFm</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="BigScreen" >
    <summary>class OWidgetStack.
 depending on a setting in ODevice it will either be a normal QWidgetStack
 and only one window will be shown.
 Or in big screen mode instead of an embedded window a toplevel window will
 be shown.
 
 Primary use: Todolist View, Addressbook view, Datebook</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="BigScreen" >
    <summary>classes OAction/OMenuBar/OToolBar if necessary
 
 
 OAction is a normal QAction but has a  priority of the item. Items often accessed
 will have OAction::Always and the least used will have OAction::Seldom. Depending 
 on the size of QApplication::Desktop OMenuBar/ToolBar and Popup Menus will
 be adjusted.
 The goal is to have an automatically adjusting menubar. On a desktop Opie apps will
 look like any other desktop app and on a pda we will take care of the space.
 
 On big apps we can make a submenu a new top level menu and provide more toolbars
 and on a small display we can if necessary group all menus into one.
 Still need to figure out how to the Child relation best
 </summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="1.2" >
    <summary>Rewrite ODevice
 
 Add a level inbetween ODevice public interface and implementation. ODevice is the only who will access ODevicePrivate and we will call into it. This way we can
 add new 'virtual' functions without sacrifing BC and not using the ugly virtual hack</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <category name="PIM" >
    <feature status="todo" target="1.2" >
     <summary>Database switch.
 Rewrite Categories, AppLnk, DocLnk to use a database backend. </summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Create import and export application for PIM data
 
 Allow easy exporting of all contacts to mobile phone using obex/obexftp</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Implement a peer to peer backend locking and communication
 and export a QSignal* to the user of the api to inform for update.
 
 Communicate internal about QCOP on XML send record additionaly
 QPE/PIM/xyz added(backend-name, uid, optional data )
 QPE/PIM/xyz removed(backend-name, uid )
 QPE/PIM/xyz modified(backend-name, uid, optional data )</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>X-Ref and selection widgets for Database
 
 Connection between address book &amp; calendar, so you can set a calendar 
 event location as an address book entry.</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Datebook2 based on the ODatebookAccess</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Evaluate the Qtopia PIM like painting and attributes in Records. better have the
 attribute inside the access frontend
 
  access()->property( uid, OTodo::Summary )
 
 </summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Faster drawing and loading. Common XML mmaped loading
 Custom drawing and only if necessary</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Allow multiple backends and split private/public into the backends. Have app for configuring it. WHat is private and what public. Allow moving records between the
 backends</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="NewApps" >
     <summary>Opie Outliner based on the OTodoAccess backend</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>Notes API</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>better sync applications</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
    <feature status="todo" target="1.2" >
     <summary>more addressbook attributes
 
 Latitude &amp; longitude fields in addressbook entries. (Which could then be 
 displayed by GPS/Map programs).
  
 Photos or Icons for address book entries (And calendar entries?).</summary>
     <responsible email="opie-devel@handhelds.org" name="Open" />
    </feature>
   </category>
   <feature status="todo" target="1.2" >
    <summary>- reworking personal settings: eg. mail, proxies and other personal settings 
 should go to the settings tab and access methods for them to libopie(2)</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Qt" >
   <feature status="todo" target="1.2" >
    <summary>Move to tslib?</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="1.2" >
    <summary>Implement Linux Input API devices for Linux2.6</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <category name="X11" />
  </category>
  <category name="X11" >
   <feature status="todo" target="1.2" >
    <summary>Finish the port of Opie/X11 together with big screen extensions and evaluate the usage of d-bus</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Development" >
   <feature status="todo" target="1.0.2" >
    <summary>Create a Knoppix development CD</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
+  <feature status="todo" target="1.0.2" >
+   <summary>Create more example applications</summary>
+   <responsible email="" name="" />
+  </feature>
  </category>
  <category name="OpieOffice" >
   <feature status="todo" target="NewApps" >
    <summary>Create a Office Suite with PocketPCs native format for opie-sheet and the new opie-write.
 Opie presentation maybe a svg capable viewer?</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Porting" >
   <feature status="todo" target="NewApps" >
    <summary>New lightweight minikde with only defines so that no increase of the binary size occurs</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
   <feature status="todo" target="NewApps" >
    <summary>port more apps</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Website" >
   <feature status="todo" target="1.0.2" >
    <summary>Ideas?</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Mail" >
   <feature status="todo" target="1.2" >
    <summary>improving/consolidating the mail clients</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Bluetooth" >
   <feature status="todo" target="1.2" >
    <summary>consolidate Bluetooth apps allow more gui operations</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
  </category>
  <category name="Todolist" />
  <category name="Datebook" >
   <feature status="todo" target="1.0.2" >
    <summary>Fix problems with events prior to 1. January 1970 aka negative unix time. Don't interpret it as -1</summary>
    <responsible email="opie-devel@handhelds.org" name="Open" />
   </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Modify layout, i.e. text in the time row is truncated w/ Verdana-12</summary>
+   <responsible email="" name="" />
+  </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Implement a Year view</summary>
+   <responsible email="" name="" />
+  </feature>
+ </category>
+ <category name="Applets" >
+  <feature status="todo" target="1.2" >
+   <summary>Write a decent applet container which shows only &quot;modified&quot; applets (look e.g. at Windows here :)</summary>
+   <responsible email="" name="" />
+  </feature>
+  <feature status="todo" target="BigScreen" >
+   <summary>Rework all applets to honor something like Taskbar::appletWidth and Taskbar::appletHeight</summary>
+   <responsible email="" name="" />
+  </feature>
+ </category>
+ <category name="OSearch" >
+  <feature status="todo" target="1.0.2" >
+   <summary>Scale icons</summary>
+   <responsible email="" name="" />
+  </feature>
+  <feature status="todo" target="1.0.2" >
+   <summary>Use less ui spacing in the upper half of the screen</summary>
+   <responsible email="" name="" />
+  </feature>
+ </category>
+ <category name="Opie-Console" >
+  <feature status="todo" target="BigScreen" >
+   <summary>Add customization for terminal font</summary>
+   <responsible email="" name="" />
+  </feature>
+ </category>
+ <category name="Clock" >
+  <feature status="todo" target="BigScreen" >
+   <summary>Make it less ugly</summary>
+   <responsible email="" name="" />
+  </feature>
  </category>
 </features>