kpilot/lib

kpilot/lib Class List

Here are the classes, structs, unions and interfaces with brief descriptions:
ConduitActionThe SyncActions created by the factory should obey at least the argument test, indicating a dry run
ConduitConfigBaseThe first classe here: ConduitConfigBase is for configuration purposes
ConduitFactory< Widget, Action >Template class that defines a conduit's factory
DatabaseInterpreter< kdetype, pilottype, mapper >A template class for reading and interpreting a database
dbThe struct db is a description class for Pilot databases by Kenneth Albanowski
NullMapper< T >NULL mapper class; the conversions here don't do anything, so you can use this when you only need 1 conversion step (from PilotRecord to PilotDatebookEntry, for instance) instead of 2
PilotAppCategoryBase class for interpretations of the binary blobs
PilotAppInfo< appinfo, unpack, pack >A template class for reading and interpreting AppInfo blocks; the idea is that it handles all the boilerplate code for reading the app block, converting it to the right kind, and then unpacking it
PilotAppInfoBaseBase class for all specific kinds of AppInfo
PilotDatabaseMethods to access a database on the pilot
PilotDateEntryThis class is a wrapper for pilot-link's datebook entries (struct Appointment)
KPilotDeviceLinkA class that handles some aspects of communication with the Handheld
PilotRecordAn "uninterpreted" representation of the bits comprising a HH record
PilotRecordBaseAll entries in the Handheld -- whether interpreted or binary blobs -- have some common characteristics, viz
PilotTodoEntryA decoded ToDo item
PluginUtilityA class containing only static helper methods
RecordConduitBaseAn intermediate class that introduces the slots we need for our sync implementation
SyncAction::SyncModeThis class encapsulates the different sync modes that can be used, and enforces a little discipline in changing the mode and messing around in general
UIDialogThis class should really be a namespace, since it contains only a pair of static methods, and they are not all that interesting anyway (I can imagine them living in factories, or even in libs somewhere as a AboutDataWidget)
KDE Home | KDE Accessibility Home | Description of Access Keys