summaryrefslogtreecommitdiff
path: root/libopie2/STATUS
authormickeyl <mickeyl>2004-04-06 12:30:37 (UTC)
committer mickeyl <mickeyl>2004-04-06 12:30:37 (UTC)
commit601c352dd956c9736fb4e3881cd7e60c504d007a (patch) (unidiff)
tree674d6c6abd83a39828a9309c23613ee5f6f900c9 /libopie2/STATUS
parentc76e3909e30af84830c0269b68f60d727717f2f9 (diff)
downloadopie-601c352dd956c9736fb4e3881cd7e60c504d007a.zip
opie-601c352dd956c9736fb4e3881cd7e60c504d007a.tar.gz
opie-601c352dd956c9736fb4e3881cd7e60c504d007a.tar.bz2
upgrade descriptions and synchronize readme and roadmap
Diffstat (limited to 'libopie2/STATUS') (more/less context) (ignore whitespace changes)
-rw-r--r--libopie2/STATUS68
1 files changed, 0 insertions, 68 deletions
diff --git a/libopie2/STATUS b/libopie2/STATUS
deleted file mode 100644
index eb3442c..0000000
--- a/libopie2/STATUS
+++ b/dev/null
@@ -1,68 +0,0 @@
1
2==================================================================
3March 2003 - Initial checkin into the Opie CVS:
4==================================================================
5
6So, this is what I have been working on over the last months.
7It's a part of what I think could migrate into our next generation
8opielibs.
9Of course this won't happen after we released Opie 1.0 and switched
10to Qt3-Embedded and gcc 3.
11
12Right now, there is content only in opiecore, opienet and opieui.
13A good part of code has been adapted from the kdelibs, which overall
14are pretty good however in details of heterogenous quality. I'm also
15not sure if all I ported should be kept, e.g. the pixmapeffect stuff
16seems unnecesary to me. However, we should not forget that Opie will
17make its debut on more powerful devices with greater display
18resolution, e.g. the Sharp C700, so we shouldn't limit ourselves in
19what should go into the libraries.
20
21Generally spoken, a lot of things are still very rough and messy,
22but I will keep improving this. Some details about what is usable
23and what is not follows:
24(everything compiles of course, otherwise I wouldn't have checked in :-)
25
26[-----------]
27[ opiecore ]
28[-----------]
29oapplication, oconfig, oglobal seem to be usable yet, oglobalsettings
30is still very messy and should be revised. A lot more thinking about how
31we should keep opie preferences, especially when moving to multi-user, has to be made.
32This will affect what goes into oglobalsettings and what configuration data
33format we will use. If we switch to Qt3 we will have to decide if we stay
34with OConfig deriving from Config or rewrite it using QSettings.
35
36[-----------]
37[ opiedb ]
38[-----------]
39There is nothing here yet. The sqlite stuff should be here.
40
41[-----------]
42[ opienet ]
43[-----------]
44onetwork*, omonitoring* and the opacket stuff are pretty usable and not
45very far from being complete. documentation for these will come...
46Over the next days, opie-wellenreiter, opie-wirelessapplet and the
47forthcoming new opie-networkapplet will be using the
48new network classes.
49I think all the other network libraries spread throught opie, e.g.
50libbend, libmail, ftplib should be revised and become part of
51opienet eventually.
52
53[-----------]
54[ opiepim ]
55[-----------]
56Nothing here yet. The stuff currently in libopie/pim should be here.
57
58[-----------]
59[ opieui ]
60[-----------]
61Pretty messy yet, but some things are usable. Unfortunately, the UI
62stuff is very hard to backport to Qt2, so some things only work
63if compiled against Qt3, especially all the popupcompletion stuff.
64OListView however works nice and is currently used in opie-wellenreiter.
65
66==================================================================
67October 2002 - Started work on cornucopia aka opielib2
68================================================================== \ No newline at end of file