Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
- if ( i < 0 || (i+1) > m_ids.count() )
+ if ( i >= m_ids.count() )
-> fix warning and simplify :)
|
|
|
|
-OPimBase was added to be used as a default struct inside OPimResolver
and to work with DSOs
-TodoListXML backend now uses mmap and madvise to load data
-OContact added/changed rtti
-OTodo added changed rtti
OPimAccess* added stuff necessary for the Resolver and a 'state'/'hint'
on how to load data
OPimResolver which resolves uid + services to Records, rtti to QCOPChannels
loads arbitary Service backends ( will work with DSOs soon )
-OPimMainWindow added some setDocument scripting possibility and
internal marshalling and demarshalling of Records
-OPimRecord added loadDataFromm and saveDataTo for marshalling purposes
much more :)
|
|
|
|
|
|
|
|
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
|
|
|
|
add the MaintainerMode to OTodo
|
|
Add it to libopie.pro
Adjust OPimRecord to use the new manager
The backends do not support xref yet
|
|
look at them and comment
|
|
Simon if you read that feel free to do an API REVIEW
on libopie but leave out OFileSelector for now...
Stefan: added an explanation for you
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
first of all UID generation belongs to OPimRecord
and was removed from OContact
then setUid now actually calls OPimRecord::setUid instead
of Record::setUid
This finally fixes the problem with wrong uids
after beaming... At least locally on my machine
|
|
many thanks
|
|
cell phones do not set the UId property...
add some more states to otodo
|
|
|
|
|
|
|
|
|
|
Vcard now imports birthday..
|
|
some inline functions into the library
|
|
and a widget where you can set the Recurrance
This will be used at least in Todolist and Datebook and in the common
classes of OTodo and OEvent
Fixed the SQL in multiple ways it's summary not description for example
|
|
OTodoAccessSQL use the read ahead value
|
|
Now if one columns equals another we try harder to find a difference
Fixed DueDate sorting...
This makes the UI more appealing
|
|
Fix parsing of due Date
We can not rely that HasDate is past the dates..
do the final QDate generation just before adding
the OTodo
|
|
We currently check if the Record got a DueDate
and then do some calculations.
I added a check to see if the item isCompleted.
If it is completed it can not be overdue
Stefan: Only one item left which is overdue ;)
|
|
this commit should fix your problems...
The XML todo backend was doing some stuff wrong
with sorted Records.
I even have a Comment describing this behaviour which
is from the current POV wrong..
need to check my brain what I though this should do
|
|
zecke.. :)
|
|
|
|
|
|
Play a bit with cahce sizes
The idea is to have the current page
and the prior page cached... still looking how to do that
|
|
|
|
ORecordList uidAt(uint index ) added
Speed Improvements at the SQL backend
do not load the list of uids until it's really needed
do not reload the uid list until it's really needed
we got a bitfield m_dirty there...
|
|
Scrolling is now noticeable faster with 10.000 items
but not as fast the XML backend...
OPimCache can be tuned and Query->OTodo too
|
|
I tested it with my todolist and it 'works' for 10.000 todos the hits are awesome ;)
The read ahead functionality does not make sense for XMLs backends because most of the stuff is already in memory. While using readahead on SQL makes things a lot faster....
I still have to fully implement read ahead
This change is bic but sc
|
|
|
|
The SQL-Stuff is currently deactivated. Otherwise everyone who wants to
compile itself would need to install libsqlite, libopiesql...
Therefore, the backend currently uses XML only..
|
|
Case number 4 is still to go
|
|
|
|
|
|
|
|
|