Create a sharing menu component

[RichardLitt]

Complete view:

User Bar with email:

Filled form:

Search Dropdown:

Share dropdown:

[RichardLitt]

Things to change:

• Gift icon should be something else.
• Fade out or push down background users when dropdown is open
• Make colors consistent
• Define default permissions and group UI. Enable multiple user selection if groups not possible.
• Keep Add button on the right, as in 'User bar with email'
• Permissions should be one icon without a dropdown notice, possibly.
• Put delete button in the permissions dropdown. Don't use a bin.
• Order by options: date added, or name.

[RichardLitt]

I'm not sure how well this design will work in the sidebar, itself. I think it will have to be a modal, or something different. Here's a screenshot:

It is really cramped - the input bar has almost no room. Alternatively, we should hide this bar as much as possible, and then give it full width and height whenever someone wants to add someone.

[RichardLitt]

Ah, GitHub naturally makes this too big. Here:

[RichardLitt]

I feel the + Add button is overkill. I think we can do this better with just Read being the standard share button, and then you can click on it to change to Write and Share. This gets rid of a button, and makes the space a lot cleaner. I think we can do the same for the buttons inside of the User Bar, on the right of each user.

I also think cutting out the Read, Write, Initiator, and Share for the buttons to the right is better, and we can show that text when they click on it and in a tooltip.

What do you think? @adammarblestone @jbenet

[adammarblestone-zz]

I can't quite visualize this...

Just remember that 1) controlling access quickly is key to user incentives, 2) we want to make it easy for people to get into bidirectional conversations so maybe write or share is a better default than read, 3) but if share is default we need to make sure the user cannot possibly not know that -- again because they need to feel they can safely and quickly control access.

Fine to start this way and change later though if needed, in the interests of getting to full functionality and integration with the database fast... we'll doubtless need to adjust this interface based on user feedback regardless.

[RichardLitt]

@jbenet I tried implementing this, but I'm not sure about how best to sort through the Google contacts. I'd like to just call an API on type, but I'm not sure there is an API call that works for that - I couldn't find one when searching for 'typeahead', 'query', or 'partial search' of the Google Contacts v3 API. What would you suggest here?

[RichardLitt]

Maybe use this to get contacts: https://github.com/stevelacy/google-contacts-oauth