1 This file contains tasks that need to be done for future versions of Xestia Address Book.
3 - Split big C++ files down into smaller files to make the project more manageable.
4 - vcard/vcard34conv.cpp (6,017 lines)
5 - frmMain.cpp (2,823 lines)
6 - frmContactEditor-Save.cpp (2,304 lines)
7 - frmActivityMgr.cpp (1,627 lines)
8 - common/getcontactinfo.cpp (1,710 lines)
9 - Implement unit testing for main features.
11 - Add support for other file formats when importing and exporting (and configure setting).
12 - OpenDocument Spreadsheet Format (ODS) (--enable-ods)
13 - OpenDocument Database Format (ODB) (--enable-odb)
14 - XLS format (--enable-xls)
15 - Add support for managing other user's address books if the user has been granted permission
16 to do it (indicate this via a different icon). Also display associated groups with it.
17 - Add tab within account settings to display which address books the user wants.
18 - Add support for using the data within other applications (email clients for example).
19 - Do a detailed check that CardDAV support between the other popular address book client is
20 working and no data loss or data duplication occurs.
21 - Check when changing servers when updating account settings:
22 - If the server being switched to is empty, ask if the contacts stored locally should be uploaded.
23 - If the server being switched to isn't empty, ask if the server contents should be kept, the local
24 contents should be kept or merge the contacts.
25 - After importing, check that the imported contacts are added to the server properly.
26 - Add support for adding the picture with the highest priority to the icon for the contact editor.
27 - Add icons (within frmContactEditor, search and preferences window) to make the
28 application stand out better.
29 - Move the saving data process in frmContactEditor to ContactDataObject. This process will
30 also need to be refactored so less code is used.
31 - Check that all text that can be used to translate is setup so that a "catalog editor" can be
33 - Take syncronisation code out of frmActivityMgr, place into a new "framework"
34 and make it easily to test against through the unit testing application.
35 - Implement the quit application function properly.