libopie

• PIM

  • Database switch. Rewrite Categories, AppLnk, DocLnk to use a database backend. Open <opie-devel@handhelds.org>
  • Create import and export application for PIM data Allow easy exporting of all contacts to mobile phone using obex/obexftp Open <opie-devel@handhelds.org>
  • Implement a peer to peer backend locking and communication and export a QSignal* to the user of the api to inform for update. Communicate internal about QCOP on XML send record additionaly QPE/PIM/xyz added(backend-name, uid, optional data ) QPE/PIM/xyz removed(backend-name, uid ) QPE/PIM/xyz modified(backend-name, uid, optional data ) Open <opie-devel@handhelds.org>
  • X-Ref and selection widgets for Database Connection between address book & calendar, so you can set a calendar event location as an address book entry. Open <opie-devel@handhelds.org>
  • Datebook2 based on the ODatebookAccess Open <opie-devel@handhelds.org>
  • Evaluate the Qtopia PIM like painting and attributes in Records. better have the attribute inside the access frontend access()->property( uid, OTodo::Summary ) Open <opie-devel@handhelds.org>
  • Faster drawing and loading. Common XML mmaped loading Custom drawing and only if necessary Open <opie-devel@handhelds.org>
  • Allow multiple backends and split private/public into the backends. Have app for configuring it. WHat is private and what public. Allow moving records between the backends Open <opie-devel@handhelds.org>
  • Notes API Open <opie-devel@handhelds.org>
  • better sync applications Open <opie-devel@handhelds.org>
  • more addressbook attributes Latitude & longitude fields in addressbook entries. (Which could then be displayed by GPS/Map programs). Photos or Icons for address book entries (And calendar entries?). Open <opie-devel@handhelds.org>