From 9b8b30fa6cbdf1424b29cde21fae112e8bf96e6d Mon Sep 17 00:00:00 2001
From: zecke <zecke>
Date: Sat, 30 Nov 2002 11:28:47 +0000
Subject: 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
---
(limited to 'libopie/pim/ABSTRACT')

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
--
cgit v0.9.0.2