author | eilers <eilers> | 2002-09-25 15:53:30 (UTC) |
---|---|---|
committer | eilers <eilers> | 2002-09-25 15:53:30 (UTC) |
commit | 5b7e930de7cc42f14b078072b8d23b977001e7b6 (patch) (side-by-side diff) | |
tree | 328e7f5a860e98ba1d1b0c2df456f05baa278209 | |
parent | 38240090027bd68d8dd15d7d46ecf17792edb732 (diff) | |
download | opie-5b7e930de7cc42f14b078072b8d23b977001e7b6.zip opie-5b7e930de7cc42f14b078072b8d23b977001e7b6.tar.gz opie-5b7e930de7cc42f14b078072b8d23b977001e7b6.tar.bz2 |
a small comment be me...
-rw-r--r-- | libopie/pim/DESIGN | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/libopie/pim/DESIGN b/libopie/pim/DESIGN index d878f45..4def7b9 100644 --- a/libopie/pim/DESIGN +++ b/libopie/pim/DESIGN @@ -34,17 +34,29 @@ not to use simple inheretance is that we can specialise quite easy. For example we have OTodoAccess : public OPimAccessTemplate<OTodo>; the we would do OTodoAccess::List list = otodoAccess.all(); OTodoAccess::List::Iterator it; for( it = list.begin(); it != list.end(); ++it ); as you can see from here it just behaves like you expect from Qt or STL. The kewlest thing is that List and List::Iterator is free to use if you want to implement your own OPimAccessTemplate. You just have to sub class it and voila you're done Hope you enjoy using OPIE PIM -regards Holger 'zecke' Freyther
\ No newline at end of file +regards Holger 'zecke' Freyther + + +Comment by Stefan Eilers: + +The opimaccesstemplate defines "SortOrder": +I think sortorder is the wrong name for the meaning of it and +it should be defined by the childs of opimaccesstemplate (every +implementation may use different values for this..) + + + + |