5 commits

Author	SHA1	Message	Date
ylecollen	5371dcea35	1 - The contacts are now cached in the filesystem : it should improve the behaviour at could start ... 2 - the contact updates are now managed since the last sync so it should also improve the contact book	2015-01-28 17:37:51 +01:00
ylecollen	c16028d633	-> the contacts list are sectioned in 2 lists ... 1 - matrix users 2 - local contacts The user must validate the local contacts sync to trigger them.	2015-01-26 18:06:13 +01:00
ylecollen	bbd890780e	The contactManager has now two matrix user check mode ... 1 - when CONTACTS_3PIDS_SYNC is set the client looks up for ALL the known 3PIDs even if the linked contacts are not displayed 2 - when CONTACTS_3PIDS_SYNC is NOT set the client looks up to the PIDS on demand i.e. the displayed contacts request their PIDs refresh.	2015-01-26 11:05:53 +01:00
ylecollen	92f1e2f602	-> use the new MXRestClient::lookup3pids method ... The matrix IDs are retrieved in one time instead of getting them one by one -> ConsoleEmail and ConsolePhoneNumber inherit of ConsoleContactField. ConsoleContactField manages the matrix part (id + thumbnail download...) -> the unknown room members are added into the contacts list. Thus, it would easier to start a chat.	2015-01-22 12:01:12 +01:00
ylecollen	c9f8958d5a	Add a 4th sections : contacts ... The contacts are displayed in a list. There is no check if one of the field is a matrix identifier.	2015-01-20 13:33:01 +01:00