summaryrefslogtreecommitdiff
path: root/development
Unidiff
Diffstat (limited to 'development') (more/less context) (ignore whitespace changes)
-rw-r--r--development/feature_plan/README5
-rw-r--r--development/feature_plan/index.html25
-rw-r--r--development/feature_plan/kde-features.inc283
-rw-r--r--development/feature_plan/new-and-maintained.html47
-rw-r--r--development/feature_plan/opie-1.0-issues.html52
-rw-r--r--development/feature_plan/opie-1.2-features.html47
-rw-r--r--development/feature_plan/opie-1.3-features.html48
-rw-r--r--development/feature_plan/opie-big-screen.html47
-rw-r--r--development/feature_plan/opie-featurelist.xml261
-rw-r--r--development/feature_plan/opie-features.dtd24
-rw-r--r--development/host-tools/README3
-rw-r--r--development/host-tools/opie-featurelist.tar.bz2bin0 -> 11511 bytes
12 files changed, 841 insertions, 1 deletions
diff --git a/development/feature_plan/README b/development/feature_plan/README
new file mode 100644
index 0000000..5241aff
--- a/dev/null
+++ b/development/feature_plan/README
@@ -0,0 +1,5 @@
1the xml file contains the featurelist. It's based on the
2KDE version from Cornelius Schumacher
3
4
5I wrote a small gui for easily editing and adding features \ No newline at end of file
diff --git a/development/feature_plan/index.html b/development/feature_plan/index.html
new file mode 100644
index 0000000..4f25087
--- a/dev/null
+++ b/development/feature_plan/index.html
@@ -0,0 +1,25 @@
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html>
3 <head>
4 <title>Opie Development Features, Issues and Release schedules</title>
5 </head>
6
7 <body>
8 <h1>Opie Development Features, Issues and Release schedules and hide out</h1>
9
10 <ul>
11 <li><a href="opie-1.0-issues.html">Opie 1.0.x Issues and Todos</a></li>
12 <li><a href="opie-1.2-features.html">Opie 1.2. The next minor release</a></li>
13 <li><a href="opie-big-screen.html">Opie Big Screen changes for 1.2</a></li>
14 <li><a href="new-and-maintained.html">App Ideas and Maintaining apps. Interested?</a></li>
15 <li><a href="opie-1.3-features.html">Ideas and Issues for the next major release</a></li>
16 </ul>
17
18 <hr>
19 <address><a href="mailto:zecke@handhelds.org">hOlgAr</a></address>
20<!-- Created: Fri Aug 22 20:10:43 CEST 2003 -->
21<!-- hhmts start -->
22Last modified: Fri Aug 22 20:19:03 CEST 2003
23<!-- hhmts end -->
24 </body>
25</html>
diff --git a/development/feature_plan/kde-features.inc b/development/feature_plan/kde-features.inc
new file mode 100644
index 0000000..a1d9b51
--- a/dev/null
+++ b/development/feature_plan/kde-features.inc
@@ -0,0 +1,283 @@
1<?php
2
3/*
4 This file contains the code to generate the KDE feature list.
5
6 Copyright (c) 2003 Cornelius Schumacher <schumacher@kde.org>
7 Copyright (c) 2003 Mario Andres Yepes C <marioy@upb.edu.co>
8
9 This program is free software; you can redistribute it and/or modify
10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation; either version 2 of the License, or
12 (at your option) any later version.
13
14 This program is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 GNU General Public License for more details.
18
19 You should have received a copy of the GNU General Public License
20 along with this program; if not, write to the Free Software
21 Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
22*/
23
24class KFeatures
25{
26 var $type = 'kdefeatures';
27 var $parentID = null;
28 var $children = array();
29
30 function setParentID($id)
31 {
32 $this->parentID = $id;
33 }
34 function getParentID()
35 {
36 return $this->parentID;
37 }
38 function addChild(&$child)
39 {
40 $this->children[] = &$child;
41 }
42 function getHtml($target, $status)
43 {
44 $out = '';
45 foreach ($this->children as $child) {
46 $out .= $child->getHtml($target, $status);
47 }
48 return $out;
49 }
50
51}
52
53class KCategory extends KFeatures
54{
55
56 var $type = 'category';
57 var $name = '';
58 var $children = array();
59
60 function KCategory($name)
61 {
62 $this->name = $name;
63 }
64 function getHtml($target, $status)
65 {
66 $out = '';
67 foreach ($this->children as $child) {
68 $temp = $child->getHtml( $target, $status);
69 # don't display empty categories
70 if ($child->type == "category" && strlen($temp))
71 {
72 $out .= sprintf("\t<li>%s\t</li>\n", $temp);
73 } else {
74 $out .= $temp;
75 }
76 }
77 if (strlen($out)) {
78 return sprintf("<h2>%s</h2>\n\t<ul>\n%s\t</ul>\n\n",$this->name,$out);
79 }
80 return '';
81 }
82}
83
84class KFeature extends KFeatures
85{
86
87 var $resp_name = array();
88 var $resp_email = array();
89 var $summary = '';
90 var $status = '';
91 var $target = '';
92 var $type = 'feature';
93
94 function KFeature($status, $target)
95 {
96 $this->status = $status;
97 $this->target = $target;
98 }
99 function getStatus()
100 {
101 return $this->status;
102 }
103 function getTarget()
104 {
105 return $this->target;
106 }
107 function setResponsible($name = null, $email = null)
108 {
109 $this->resp_name[] = $name;
110 $this->resp_email[] = $email;
111 }
112 function getResponsible()
113 {
114 # Nobody responsible?
115 if (count($this->resp_name) == 0) return '';
116
117 $out = '<em>';
118 for ($i = 0; $i < count($this->resp_name); $i++) {
119 if ($i > 0) $out .= ', ';
120 if ($this->resp_name[$i]) {
121 $out .= $this->resp_name[$i];
122 }
123 if ($this->resp_name[$i] && $this->resp_email[$i]) $out .= " ";
124 if ($this->resp_email[$i]) {
125 $out .= '&lt;'.$this->resp_email[$i].'&gt;';
126 }
127 }
128 $out .= '</em>';
129 return $out;
130 }
131 function setSummary($summary)
132 {
133 $this->summary .= $summary.' ';
134 }
135 function getHtml($target, $status){
136 if ($this->target == $target && $this->status == $status) {
137 return sprintf("\t\t<li>%s%s</li>\n",$this->summary,$this->getResponsible());
138 }
139 return '';
140 }
141
142}
143
144function startElement($parser, $name, $attrs) {
145 global $tags;
146 global $parentID;
147
148 global $insummary;
149 global $pcdata;
150 global $curtag;
151
152 switch ($name) {
153 case 'FEATURES':
154 $parentID = 0;
155 $obj = new KFeatures();
156 $tags = array($obj);
157
158 $insummary = false;
159 $pcdata = '';
160 $curtag = '';
161 break;
162 case 'CATEGORY':
163 $obj = new KCategory($attrs['NAME']);
164 $obj->setParentID($parentID);
165 $tags[] = $obj;
166 $currentID = count($tags) - 1;
167 $tags[$parentID]->addChild($tags[$currentID]);
168 $parentID = $currentID;
169
170 break;
171 case 'FEATURE':
172 $obj = new KFeature($attrs['STATUS'], $attrs['TARGET']);
173 $obj->setParentID($parentID);
174 $tags[] = $obj;
175 $currentID = count($tags) - 1;
176 $tags[$parentID]->addChild($tags[$currentID]);
177 $parentID = $currentID;
178 break;
179 case 'RESPONSIBLE':
180 $n = count($tags) - 1;
181 $tags[$n]->setResponsible(@$attrs['NAME'], @$attrs['EMAIL']);
182 break;
183 case 'SUMMARY':
184 $insummary = true;
185 $pcdata = '';
186 break;
187 default:
188 if (!$insummary) {
189 break;
190 }
191 $curtag = strtolower($name);
192 $att = '';
193 foreach ($attrs as $k => $v) {
194 $att .= ' '.strtolower($k).'="'.$v.'"';
195 }
196
197 $pcdata .= '<'.$curtag.$att.'>';
198 break;
199 }
200}
201
202function endElement($parser, $name) {
203 global $parentID;
204 global $tags;
205
206 global $curtag;
207 global $pcdata;
208 global $insummary;
209
210 switch ($name) {
211 case "FEATURE":
212 $n = count($tags) - 1;
213 $parentID = $tags[$n]->getParentID();
214 break;
215 case "CATEGORY":
216 $parentID = $tags[$parentID]->getParentID();
217 break;
218 case "SUMMARY":
219 $n = count($tags) - 1;
220 $tags[$n]->setSummary($pcdata);
221
222 $insummary = false;
223 $pcdata = '';
224 break;
225 default:
226 if ($insummary) {
227 $pcdata .= '</'.$curtag.'>';
228 }
229 break;
230 }
231}
232
233function characterData($parser, $data) {
234 global $htmltag;
235 global $tags;
236
237 global $pcdata;
238 global $curtag;
239 global $insummary;
240
241 if (!$insummary) {
242 return;
243 }
244 $pcdata .= htmlspecialchars($data);
245}
246
247function parse( $file ) {
248
249 $xml_parser = xml_parser_create();
250
251 xml_parser_set_option($xml_parser, XML_OPTION_CASE_FOLDING, true);
252 xml_set_element_handler($xml_parser, "startElement", "endElement");
253 xml_set_character_data_handler($xml_parser, "characterData");
254
255 if (!($fp = fopen($file, "r"))) {
256 die("could not open XML input");
257 }
258
259
260 while ($data = fread($fp, 4096)) {
261 if (!xml_parse($xml_parser, $data, feof($fp))) {
262 die(sprintf("XML error: %s at line %d",
263 xml_error_string(xml_get_error_code($xml_parser)),
264 xml_get_current_line_number($xml_parser)));
265 }
266 }
267
268 xml_parser_free($xml_parser);
269}
270
271
272
273function printHtml($target, $status)
274{
275 global $tags;
276 if (!is_array($tags)) {
277 die('You must parse the xml file first with parse("filename.xml");');
278 }
279 print($tags[0]->getHtml($target,$status));
280}
281
282
283?>
diff --git a/development/feature_plan/new-and-maintained.html b/development/feature_plan/new-and-maintained.html
new file mode 100644
index 0000000..045f5da
--- a/dev/null
+++ b/development/feature_plan/new-and-maintained.html
@@ -0,0 +1,47 @@
1<p>
2Opie needs <b>YOUR help</b>. Below is a list of application ideas, existing
3unmaintained software and a list of application we would like to port.
4So if you've interest feel free to help us. We would really appreciate it.
5</p>
6
7
8<?php
9
10$version = "NewApps";
11$version2 = "Unmaintained";
12
13require_once "kde-features.inc";
14
15parse("opie-featurelist.xml");
16?>
17
18
19<table width="100%" border="0">
20 <tr><td bgcolor="red"><div align="center">TODO</div></td><td bgcolor="#ffeeee">
21
22<?php echo printHtml($version,'todo') ?>
23<?php echo printHtml($version2,'todo') ?>
24 </td></tr>
25
26 <tr><td bgcolor="yellow"><div align="center">In Progress</div></td><td bgcolor="#ffffee">
27
28<?php echo printHtml($version,'inprogress') ?>
29<?php echo printHtml($version2,'inprogress') ?>
30
31 </td></tr>
32
33<tr><td bgcolor="green"><div align="center">Finished</div></td><td bgcolor="#eeffee">
34
35<?php echo printHtml($version,'done') ?>
36<?php echo printHtml($version2,'done') ?>
37
38</td></tr>
39</table>
40
41
42 <hr>
43 <address><a href="mailto:zecke@handhelds.org">zecke/hOlgAr</a></address>
44<!-- Created: Fri Aug 22 20:00:19 CEST 2003 -->
45<!-- hhmts start -->
46Last modified: Fri Aug 22 20:29:56 CEST 2003
47<!-- hhmts end -->
diff --git a/development/feature_plan/opie-1.0-issues.html b/development/feature_plan/opie-1.0-issues.html
new file mode 100644
index 0000000..dc241f2
--- a/dev/null
+++ b/development/feature_plan/opie-1.0-issues.html
@@ -0,0 +1,52 @@
1
2<p>
3This page contains Issues to be fixed and 'features' we want to implement
4for the Opie 1.0.x release. If you've an issue which needs attention please
5send me the Bug Nr or description and I'll be happy to add it.
6Open tasks are ready to be taken by you. Mail me or opie-devel what you
7want to do and I'll update the site.
8This site also contains completely new apps we would like to implemented or
9ported.
10</p>
11
12<?php
13
14$version = "1.0.2";
15$version2 = "NewApps";
16
17require_once "kde-features.inc";
18
19parse("opie-featurelist.xml");
20?>
21
22
23<table width="100%" border="0">
24 <tr><td bgcolor="red"><div align="center">TODO</div></td><td bgcolor="#ffeeee">
25
26<?php echo printHtml($version,'todo') ?>
27<?php echo printHtml($version2,'todo') ?>
28
29 </td></tr>
30
31 <tr><td bgcolor="yellow"><div align="center">In Progress</div></td><td bgcolor="#ffffee">
32
33<?php echo printHtml($version,'inprogress') ?>
34<?php echo printHtml($version2,'inprogress') ?>
35
36 </td></tr>
37
38<tr><td bgcolor="green"><div align="center">Finished</div></td><td bgcolor="#eeffee">
39
40<?php echo printHtml($version,'done') ?>
41<?php echo printHtml($version2,'done') ?>
42
43</td></tr>
44</table>
45
46
47 <hr>
48 <address><a href="mailto:zecke@handhelds.org">zecke/hOlgAr</a></address>
49<!-- Created: Fri Aug 22 20:00:19 CEST 2003 -->
50<!-- hhmts start -->
51Last modified: Fri Aug 22 20:14:40 CEST 2003
52<!-- hhmts end -->
diff --git a/development/feature_plan/opie-1.2-features.html b/development/feature_plan/opie-1.2-features.html
new file mode 100644
index 0000000..4478bf6
--- a/dev/null
+++ b/development/feature_plan/opie-1.2-features.html
@@ -0,0 +1,47 @@
1<p>
2Opie 1.2 will be the next minor release based on the Opie 1.0 libraries and will
3be compatible to 1.0.x before we will create a new major release. On the way to
4ODP1.0 we will keep on improving Opie, identifying bottlenecks and keep on
5writing new features. This pages contains ideas we've in mind we want to develop
6for Opie 1.2 which is scheduled to be released roughly in January/February 2004.
7If you've your own ideas mail me and if you want to take a feature and
8implement mail me as well. So pick features implement it pick the next one.
9</p>
10
11<?php
12
13$version = "1.2";
14
15require_once "kde-features.inc";
16
17parse("opie-featurelist.xml");
18?>
19
20
21<table width="100%" border="0">
22 <tr><td bgcolor="red"><div align="center">TODO</div></td><td bgcolor="#ffeeee">
23
24<?php echo printHtml($version,'todo') ?>
25
26 </td></tr>
27
28 <tr><td bgcolor="yellow"><div align="center">In Progress</div></td><td bgcolor="#ffffee">
29
30<?php echo printHtml($version,'inprogress') ?>
31
32 </td></tr>
33
34<tr><td bgcolor="green"><div align="center">Finished</div></td><td bgcolor="#eeffee">
35
36<?php echo printHtml($version,'done') ?>
37
38</td></tr>
39</table>
40
41
42 <hr>
43 <address><a href="mailto:zecke@handhelds.org">zecke/hOlgAr</a></address>
44<!-- Created: Fri Aug 22 20:00:19 CEST 2003 -->
45<!-- hhmts start -->
46Last modified: Fri Aug 22 20:22:29 CEST 2003
47<!-- hhmts end -->
diff --git a/development/feature_plan/opie-1.3-features.html b/development/feature_plan/opie-1.3-features.html
new file mode 100644
index 0000000..99dff80
--- a/dev/null
+++ b/development/feature_plan/opie-1.3-features.html
@@ -0,0 +1,48 @@
1<p>
2ODP Opie Development Platform 1.0
3Currently only ideas exist, a wiki page and our experience with the existing
4APIs. The goal is to create for users and developers full featured, extendable,
5fast, effective and runtime efficent Platform. Currently we're collecting issues
6and bottleneck with the existing platform before we start the great overhaul.
7The PIM API, BigScreen Extension, Parts of libopie2 will surely be found inside
8this new API.
9Again if you're developer mail me your problems with the existing framework.
10</p>
11
12<?php
13
14$version = "1.3";
15
16require_once "kde-features.inc";
17
18parse("opie-featurelist.xml");
19?>
20
21
22<table width="100%" border="0">
23 <tr><td bgcolor="red"><div align="center">TODO</div></td><td bgcolor="#ffeeee">
24
25<?php echo printHtml($version,'todo') ?>
26
27 </td></tr>
28
29 <tr><td bgcolor="yellow"><div align="center">In Progress</div></td><td bgcolor="#ffffee">
30
31<?php echo printHtml($version,'inprogress') ?>
32
33 </td></tr>
34
35<tr><td bgcolor="green"><div align="center">Finished</div></td><td bgcolor="#eeffee">
36
37<?php echo printHtml($version,'done') ?>
38
39</td></tr>
40</table>
41
42
43 <hr>
44 <address><a href="mailto:zecke@handhelds.org">zecke/hOlgAr</a></address>
45<!-- Created: Fri Aug 22 20:00:19 CEST 2003 -->
46<!-- hhmts start -->
47Last modified: Fri Aug 22 20:34:13 CEST 2003
48<!-- hhmts end -->
diff --git a/development/feature_plan/opie-big-screen.html b/development/feature_plan/opie-big-screen.html
new file mode 100644
index 0000000..fce258c
--- a/dev/null
+++ b/development/feature_plan/opie-big-screen.html
@@ -0,0 +1,47 @@
1
2<p>
3People started to use Opie on bigger screens. Some design decisions made don't apply
4to bigger screen resolutions. The Opie big screen extension classes are aimed to fill
5this gap. With little modification of the application Opie will get a consitent look
6and feel on small devices to desktop computers.
7Again. Add tasks/features. pick tasks and features mail me.
8</p>
9
10
11<?php
12
13$version = "BigScreen";
14
15require_once "kde-features.inc";
16
17parse("opie-featurelist.xml");
18?>
19
20
21<table width="100%" border="0">
22 <tr><td bgcolor="red"><div align="center">TODO</div></td><td bgcolor="#ffeeee">
23
24<?php echo printHtml($version,'todo') ?>
25
26 </td></tr>
27
28 <tr><td bgcolor="yellow"><div align="center">In Progress</div></td><td bgcolor="#ffffee">
29
30<?php echo printHtml($version,'inprogress') ?>
31
32 </td></tr>
33
34<tr><td bgcolor="green"><div align="center">Finished</div></td><td bgcolor="#eeffee">
35
36<?php echo printHtml($version,'done') ?>
37
38</td></tr>
39</table>
40
41
42 <hr>
43 <address><a href="mailto:zecke@handhelds.org">zecke/hOlgAr</a></address>
44<!-- Created: Fri Aug 22 20:00:19 CEST 2003 -->
45<!-- hhmts start -->
46Last modified: Fri Aug 22 20:27:16 CEST 2003
47<!-- hhmts end -->
diff --git a/development/feature_plan/opie-featurelist.xml b/development/feature_plan/opie-featurelist.xml
new file mode 100644
index 0000000..43f2c77
--- a/dev/null
+++ b/development/feature_plan/opie-featurelist.xml
@@ -0,0 +1,261 @@
1<?xml version = '1.0' encoding = 'iso-8859-1'?>
2<!DOCTYPE features SYSTEM "opie-features.dtd">
3<!--
4
5Copied from KDE and (C) by Cornelius Schumacher
6
7This file serves as central repository of planned KDE features. It's parsed by
8the PHP scripts in "opie-features.inc" which are used by "kde-3.2-features.html" to
9generate HTML versions for the web.
10
11If you plan to add a feature to KDE please add it to this file. A feature can
12have one of three status types: "todo", "inprogress", "done". Please update
13the status from time to time. For a release there shouldn't be any features
14with other states than "done". If you can't complete a feature for a release
15please move the feature to the next release. The "target" attribute specifies
16for which release the feature should be finished. At the moment only the value
17"3.2" is evaluated, but we will add pages showing the features for later
18versions as needed.
19
20Each feature consists of a summary giving a short description what the feature is
21about and one or more responsible persons.
22
23A draft for a DTD of the features file can be found in "kde-features.dtd". Use
24"xmllint -valid -noout kde-features.xml" to validate the xml file against the
25DTD. If there are errors in the XML document they will be shown, if not the
26command will not output anything.
27
28if you have questions or comments please post them to the mailing list or contact
29Cornelius Schumacher <schumacher@kde.org>.
30
31--><features>
32 <category name="Library" >
33 <feature status="todo" target="1.2" >
34 <summary>merge with Qtopia 1.7 library if possible</summary>
35 <responsible email="opie-devel@handhelds.org" name="Open" />
36 </feature>
37 <feature status="todo" target="BigScreen" >
38 <summary>Add show which performs window manager tasks. Places the window right and
39and with the right size for big screens.</summary>
40 <responsible email="opie-devel@handhelds.org" name="Open" />
41 </feature>
42 <feature status="todo" target="1.2" >
43 <summary>Icon Themes</summary>
44 <responsible email="opie-devel@handhelds.org" name="Open" />
45 </feature>
46 </category>
47 <category name="Launcher" >
48 <feature status="todo" target="BigScreen" >
49 <summary>Background picture displayed in different modes</summary>
50 <responsible email="opie-devel@handhelds.org" name="Open" />
51 </feature>
52 </category>
53 <category name="Addressbook" />
54 <category name="All" >
55 <feature status="todo" target="1.2" >
56 <summary>Make all applications use more from libopie and see what is commonly used and create a common implementation if necessary.</summary>
57 <responsible email="opie-devel@handhelds.org" name="Open" />
58 </feature>
59 <feature status="todo" target="BigScreen" >
60 <summary>Kill showMaximized and use QPEApplication function to show the widget. This allows
61both X11 and BigScreen Qt/E to look and behave better on bigger screens</summary>
62 <responsible email="opie-devel@handhelds.org" name="Open" />
63 </feature>
64 <feature status="todo" target="1.2" >
65 <summary>security considerations and flaw search
66
67-Search for memcopies, printf, snprinft, strcat, and replace with their n functions
68-Search for misuse and unguarded usage of system
69-Kiosk mode?</summary>
70 <responsible email="opie-devel@handhelds.org" name="Open" />
71 </feature>
72 </category>
73 <category name="libopie" >
74 <feature status="todo" target="BigScreen" >
75 <summary>Write OSplitter.
76OSplitter 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
77or QHBoxLayout. Currently only horizontal mode is planed.
78
79Primary use: AdvancedFm</summary>
80 <responsible email="opie-devel@handhelds.org" name="Open" />
81 </feature>
82 <feature status="todo" target="BigScreen" >
83 <summary>class OWidgetStack.
84depending on a setting in ODevice it will either be a normal QWidgetStack
85and only one window will be shown.
86Or in big screen mode instead of an embedded window a toplevel window will
87be shown.
88
89Primary use: Todolist View, Addressbook view, Datebook</summary>
90 <responsible email="opie-devel@handhelds.org" name="Open" />
91 </feature>
92 <feature status="todo" target="BigScreen" >
93 <summary>classes OAction/OMenuBar/OToolBar if necessary
94
95
96OAction is a normal QAction but has a priority of the item. Items often accessed
97will have OAction::Always and the least used will have OAction::Seldom. Depending
98on the size of QApplication::Desktop OMenuBar/ToolBar and Popup Menus will
99be adjusted.
100The goal is to have an automatically adjusting menubar. On a desktop Opie apps will
101look like any other desktop app and on a pda we will take care of the space.
102
103On big apps we can make a submenu a new top level menu and provide more toolbars
104and on a small display we can if necessary group all menus into one.
105Still need to figure out how to the Child relation best
106</summary>
107 <responsible email="opie-devel@handhelds.org" name="Open" />
108 </feature>
109 <feature status="todo" target="1.2" >
110 <summary>Rewrite ODevice
111
112Add 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
113add new 'virtual' functions without sacrifing BC and not using the ugly virtual hack</summary>
114 <responsible email="opie-devel@handhelds.org" name="Open" />
115 </feature>
116 <category name="PIM" >
117 <feature status="todo" target="1.2" >
118 <summary>Database switch.
119Rewrite Categories, AppLnk, DocLnk to use a database backend. </summary>
120 <responsible email="opie-devel@handhelds.org" name="Open" />
121 </feature>
122 <feature status="todo" target="1.2" >
123 <summary>Create import and export application for PIM data
124
125Allow easy exporting of all contacts to mobile phone using obex/obexftp</summary>
126 <responsible email="opie-devel@handhelds.org" name="Open" />
127 </feature>
128 <feature status="todo" target="1.2" >
129 <summary>Implement a peer to peer backend locking and communication
130and export a QSignal* to the user of the api to inform for update.
131
132Communicate internal about QCOP on XML send record additionaly
133QPE/PIM/xyz added(backend-name, uid, optional data )
134QPE/PIM/xyz removed(backend-name, uid )
135QPE/PIM/xyz modified(backend-name, uid, optional data )</summary>
136 <responsible email="opie-devel@handhelds.org" name="Open" />
137 </feature>
138 <feature status="todo" target="1.2" >
139 <summary>X-Ref and selection widgets for Database
140
141Connection between address book &amp; calendar, so you can set a calendar
142event location as an address book entry.</summary>
143 <responsible email="opie-devel@handhelds.org" name="Open" />
144 </feature>
145 <feature status="todo" target="1.2" >
146 <summary>Datebook2 based on the ODatebookAccess</summary>
147 <responsible email="opie-devel@handhelds.org" name="Open" />
148 </feature>
149 <feature status="todo" target="1.2" >
150 <summary>Evaluate the Qtopia PIM like painting and attributes in Records. better have the
151attribute inside the access frontend
152
153 access()->property( uid, OTodo::Summary )
154
155</summary>
156 <responsible email="opie-devel@handhelds.org" name="Open" />
157 </feature>
158 <feature status="todo" target="1.2" >
159 <summary>Faster drawing and loading. Common XML mmaped loading
160Custom drawing and only if necessary</summary>
161 <responsible email="opie-devel@handhelds.org" name="Open" />
162 </feature>
163 <feature status="todo" target="1.2" >
164 <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
165backends</summary>
166 <responsible email="opie-devel@handhelds.org" name="Open" />
167 </feature>
168 <feature status="todo" target="NewApps" >
169 <summary>Opie Outliner based on the OTodoAccess backend</summary>
170 <responsible email="opie-devel@handhelds.org" name="Open" />
171 </feature>
172 <feature status="todo" target="1.2" >
173 <summary>Notes API</summary>
174 <responsible email="opie-devel@handhelds.org" name="Open" />
175 </feature>
176 <feature status="todo" target="1.2" >
177 <summary>better sync applications</summary>
178 <responsible email="opie-devel@handhelds.org" name="Open" />
179 </feature>
180 <feature status="todo" target="1.2" >
181 <summary>more addressbook attributes
182
183Latitude &amp; longitude fields in addressbook entries. (Which could then be
184displayed by GPS/Map programs).
185
186Photos or Icons for address book entries (And calendar entries?).</summary>
187 <responsible email="opie-devel@handhelds.org" name="Open" />
188 </feature>
189 </category>
190 <feature status="todo" target="1.2" >
191 <summary>- reworking personal settings: eg. mail, proxies and other personal settings
192should go to the settings tab and access methods for them to libopie(2)</summary>
193 <responsible email="opie-devel@handhelds.org" name="Open" />
194 </feature>
195 </category>
196 <category name="Qt" >
197 <feature status="todo" target="1.2" >
198 <summary>Move to tslib?</summary>
199 <responsible email="opie-devel@handhelds.org" name="Open" />
200 </feature>
201 <feature status="todo" target="1.2" >
202 <summary>Implement Linux Input API devices for Linux2.6</summary>
203 <responsible email="opie-devel@handhelds.org" name="Open" />
204 </feature>
205 <category name="X11" />
206 </category>
207 <category name="X11" >
208 <feature status="todo" target="1.2" >
209 <summary>Finish the port of Opie/X11 together with big screen extensions and evaluate the usage of d-bus</summary>
210 <responsible email="opie-devel@handhelds.org" name="Open" />
211 </feature>
212 </category>
213 <category name="Development" >
214 <feature status="todo" target="1.0.2" >
215 <summary>Create a Knoppix development CD</summary>
216 <responsible email="opie-devel@handhelds.org" name="Open" />
217 </feature>
218 </category>
219 <category name="OpieOffice" >
220 <feature status="todo" target="NewApps" >
221 <summary>Create a Office Suite with PocketPCs native format for opie-sheet and the new opie-write.
222Opie presentation maybe a svg capable viewer?</summary>
223 <responsible email="opie-devel@handhelds.org" name="Open" />
224 </feature>
225 </category>
226 <category name="Porting" >
227 <feature status="todo" target="NewApps" >
228 <summary>New lightweight minikde with only defines so that no increase of the binary size occurs</summary>
229 <responsible email="opie-devel@handhelds.org" name="Open" />
230 </feature>
231 <feature status="todo" target="NewApps" >
232 <summary>port more apps</summary>
233 <responsible email="opie-devel@handhelds.org" name="Open" />
234 </feature>
235 </category>
236 <category name="Website" >
237 <feature status="todo" target="1.0.2" >
238 <summary>Ideas?</summary>
239 <responsible email="opie-devel@handhelds.org" name="Open" />
240 </feature>
241 </category>
242 <category name="Mail" >
243 <feature status="todo" target="1.2" >
244 <summary>improving/consolidating the mail clients</summary>
245 <responsible email="opie-devel@handhelds.org" name="Open" />
246 </feature>
247 </category>
248 <category name="Bluetooth" >
249 <feature status="todo" target="1.2" >
250 <summary>consolidate Bluetooth apps allow more gui operations</summary>
251 <responsible email="opie-devel@handhelds.org" name="Open" />
252 </feature>
253 </category>
254 <category name="Todolist" />
255 <category name="Datebook" >
256 <feature status="todo" target="1.0.2" >
257 <summary>Fix problems with events prior to 1. January 1970 aka negative unix time. Don't interpret it as -1</summary>
258 <responsible email="opie-devel@handhelds.org" name="Open" />
259 </feature>
260 </category>
261</features>
diff --git a/development/feature_plan/opie-features.dtd b/development/feature_plan/opie-features.dtd
new file mode 100644
index 0000000..3ed436b
--- a/dev/null
+++ b/development/feature_plan/opie-features.dtd
@@ -0,0 +1,24 @@
1
2<!ELEMENT features (category+)>
3
4<!ELEMENT category (feature|category)*>
5<!ATTLIST category name CDATA #REQUIRED >
6
7<!ELEMENT feature (summary?,responsible*)>
8<!ATTLIST feature status (inprogress|todo|done) "todo"
9 target CDATA #REQUIRED>
10
11<!ELEMENT responsible EMPTY>
12<!ATTLIST responsible name CDATA #IMPLIED
13 email CDATA #IMPLIED>
14
15<!ELEMENT summary (#PCDATA|i|a|b|em|strong)*>
16
17<!ELEMENT i (#PCDATA)>
18<!ELEMENT b (#PCDATA)>
19<!ELEMENT em (#PCDATA)>
20<!ELEMENT strong (#PCDATA)>
21
22<!ELEMENT a (#PCDATA)>
23<!ATTLIST a href CDATA #IMPLIED>
24<!ATTLIST a title CDATA #IMPLIED>
diff --git a/development/host-tools/README b/development/host-tools/README
index c9901e6..be7b161 100644
--- a/development/host-tools/README
+++ b/development/host-tools/README
@@ -1,22 +1,23 @@
1A collection of useful Opie related software running with Qt/X11 1A collection of useful Opie related software running with Qt/X11
2version 3.0 and sometimes KDE as well 2version 3.0 and sometimes KDE as well
3 3
4 opie-langchecker.tar.gz -with make messages and make all-messages 4 opie-langchecker.tar.gz -with make messages and make all-messages
5 you generate for each application two 5 you generate for each application two
6 .po files. One file with all strings 6 .po files. One file with all strings
7 included in your program and one file 7 included in your program and one file
8 with strings from tr() and the NOOP. 8 with strings from tr() and the NOOP.
9 Langchecker is a KParts KDE application 9 Langchecker is a KParts KDE application
10 which lets you first spell check the strings 10 which lets you first spell check the strings
11 and seconldy shows you on a per file/line 11 and seconldy shows you on a per file/line
12 basis which strings are not available as tr. 12 basis which strings are not available as tr.
13 This helps you to find application 13 This helps you to find application
14 14
15 opie-featurelist.tar.gz -Is currently just a small hack application 15 opie-featurelist.tar.bz2-Is currently just a small hack application
16 to create feature lists conforming to 16 to create feature lists conforming to
17 Cornelius Schumachers XML features file. 17 Cornelius Schumachers XML features file.
18 Maybe it'll turn into a full blown 18 Maybe it'll turn into a full blown
19 Project management tool with Opie clients... 19 Project management tool with Opie clients...
20 ( kmaschru ) or one simply writes a new 20 ( kmaschru ) or one simply writes a new
21 TODO view + backend or changes the file 21 TODO view + backend or changes the file
22 format... 22 format...
23 BUILD: qmake -o Makefile opie-featurelist.pro \ No newline at end of file
diff --git a/development/host-tools/opie-featurelist.tar.bz2 b/development/host-tools/opie-featurelist.tar.bz2
new file mode 100644
index 0000000..4ca6d8a
--- a/dev/null
+++ b/development/host-tools/opie-featurelist.tar.bz2
Binary files differ