| author | mickeyl <mickeyl> | 2004-11-16 19:14:18 (UTC) |
|---|---|---|
| committer | mickeyl <mickeyl> | 2004-11-16 19:14:18 (UTC) |
| commit | ea3945a9bd8f9830f70b1efa133f9df13b19362f (patch) (side-by-side diff) | |
| tree | f2ea22cc50e9aa8aa73ee7dea148f41c563c9666 /libopie/pim/ABSTRACT | |
| parent | 1c6f490e8541626f68422e0a3a7c7281d7f5b7d3 (diff) | |
| download | opie-ea3945a9bd8f9830f70b1efa133f9df13b19362f.zip opie-ea3945a9bd8f9830f70b1efa133f9df13b19362f.tar.gz opie-ea3945a9bd8f9830f70b1efa133f9df13b19362f.tar.bz2 | |
libopie1 goes into unsupported
| -rw-r--r-- | libopie/pim/ABSTRACT | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/libopie/pim/ABSTRACT b/libopie/pim/ABSTRACT deleted file mode 100644 index 5538d19..0000000 --- a/libopie/pim/ABSTRACT +++ b/dev/null @@ -1,18 +0,0 @@ -What is Opie PIM? Why is it special? -Why do we need Opie PIM? - -The goal of OpiePIM is to be first of all -extendable, light weight, scalable and fast. -For the programmer we try to add a nice but -powerful API to all classes. - -Memory is a costy resource on small and embedded -devices. So we try to keep the memory usage as -low as possible. Never the less we won't use structs -and Pointers in the public API. -The whole pim framework is value based. Internally we try -to use implicit sharing as found in other Qt classes as well. -This makes it possible to give 3rd party devels a nice -API while keeping the memory usage as low as possible. - -We use C++ Templates |