| author | zecke <zecke> | 2002-11-30 11:28:47 (UTC) |
|---|---|---|
| committer | zecke <zecke> | 2002-11-30 11:28:47 (UTC) |
| commit | 9b8b30fa6cbdf1424b29cde21fae112e8bf96e6d (patch) (side-by-side diff) | |
| tree | 896dd858dc2ec2f0b7e1b265cae66ccceecc82da /libopie/pim/ABSTRACT | |
| parent | 599c58c6ab2ab936890cbbfa4e6299493c141f8a (diff) | |
| download | opie-9b8b30fa6cbdf1424b29cde21fae112e8bf96e6d.zip opie-9b8b30fa6cbdf1424b29cde21fae112e8bf96e6d.tar.gz opie-9b8b30fa6cbdf1424b29cde21fae112e8bf96e6d.tar.bz2 | |
More infrastructure
ORecur has now the nextOccurence function
exceptions
We've now Notifers like Alarms and DatebookEntries
we may add to execute applications...
AppName replaced with service cause it is a service
Add rtti to OPimRecord as a static function
This is used inside the BackEnd classes to static_cast...
added removeAllCompleted to the todobackends...
add a common Opie PIM mainwindow which takes care of some simple
scripting enchangements..
much more
| -rw-r--r-- | libopie/pim/ABSTRACT | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/libopie/pim/ABSTRACT b/libopie/pim/ABSTRACT new file mode 100644 index 0000000..5538d19 --- a/dev/null +++ b/libopie/pim/ABSTRACT @@ -0,0 +1,18 @@ +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 |