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