Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LibFolks: Handle mutiple email ids for a eds contact #9

Open
khurshid-alam opened this issue Apr 10, 2017 · 5 comments
Open

LibFolks: Handle mutiple email ids for a eds contact #9

khurshid-alam opened this issue Apr 10, 2017 · 5 comments

Comments

@khurshid-alam
Copy link

khurshid-alam commented Apr 10, 2017

Workflow

  1. If a contact has more than 1 email-id, "compose email" will populate a third object pane in kupfer listing all the emails belong to that particular contact.

  2. User can then select a particular email to send a mail.

@khurshid-alam khurshid-alam changed the title LibFolks: Handle mutiple email for contacts LibFolks: Handle mutiple email ids for contacts Apr 10, 2017
@khurshid-alam khurshid-alam changed the title LibFolks: Handle mutiple email ids for contacts LibFolks: Handle mutiple email ids for a eds contact Apr 10, 2017
@hugosenari
Copy link
Owner

leaf.object['email_addresses'] has all emails but only first is set as leaf.object[EMAIL_KEY].

@khurshid-alam
Copy link
Author

khurshid-alam commented May 4, 2017

@hugosenari And what about id? How do I acces it from leaf? leaf.object itself should have individual id of the contact. No?

@hugosenari
Copy link
Owner

You can get it from leaf.folk.get_id()

@hugosenari
Copy link
Owner

What if instead of one Leaf per Folk, we yield one Leaf per Information and group them by name/id?

Ie Hugo Sena Ribeiro:

@khurshid-alam
Copy link
Author

Yes It can be done, but it has to be grouped by id.

But one leaf/information will results into too much leafs and may slow down the launcher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants