User contributions for Cmollekopf

21:0021:00, 1 December 2014 diff hist −1,926 KDE PIM/Akonadi Next/Client API No edit summary
20:3220:32, 1 December 2014 diff hist +3,100 N KDE PIM/Akonadi Next/Store Created page with "== Store access == Access to the entities happens through a well defined interface that defines a property-map for each supported domain type. A property map could look like: ..."
20:3120:31, 1 December 2014 diff hist +39 KDE PIM/Akonadi Next →Design
20:2920:29, 1 December 2014 diff hist +526 N KDE PIM/Akonadi Next/Legacy Akonadi Compatibility Layer Created page with "A compatibility layer is required in order to keep the current API working. This includes the Akonadi:: jobs and Akonadi::Monitor. * akonadi provided a stable id for each ent..."
20:2820:28, 1 December 2014 diff hist +97 KDE PIM/Akonadi Next →Design
20:2720:27, 1 December 2014 diff hist +2,008 N KDE PIM/Akonadi Next/Current Akonadi Created page with "== Original Akonadi Design == Reasons for akonadi: * commond database for applications (interaction) * separation from service access to data-access (shared backends between ..." current
20:2720:27, 1 December 2014 diff hist +63 KDE PIM/Akonadi Next →Design
20:2520:25, 1 December 2014 diff hist +11,701 N KDE PIM/Akonadi Next/Design Created page with " == Axioms == # Personal information is stored in multiple sources (address books, email stores, calendar files, ...) # These sources may local, remote or a mix of local and r..."
20:2520:25, 1 December 2014 diff hist +39 KDE PIM/Akonadi Next →Design
20:2320:23, 1 December 2014 diff hist +62 KDE PIM/Akonadi Next No edit summary
20:1720:17, 1 December 2014 diff hist +2,893 N KDE PIM/Akonadi Next/Client API Created page with " Loading: * Set load(Query) => A query is executed and a reactive set is returned. * TreeSet loadTree(Query) => Additionally to the query a tree structure is available in the ..."
20:1620:16, 1 December 2014 diff hist +4,725 N KDE PIM/Akonadi Next Created page with "'''This is WIP! ''' == Comments/Thoughts/Questions == Comments/Thoughts: * Incremental changes can be recorded by message buffer => resource can replay incremental changes * ..."