summaryrefslogtreecommitdiff
path: root/libopie/pim/ABSTRACT
Side-by-side diff
Diffstat (limited to 'libopie/pim/ABSTRACT') (more/less context) (ignore whitespace changes)
-rw-r--r--libopie/pim/ABSTRACT18
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