Talk via website to work as a side panel, floating panel, pop-out panel, or separate web page.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Is your feature request related to a problem? Please describe.
I feel like Talk would be more useful if I could side-panel access it while I have the cloud document I'm working on open in the same view. Some of the core functionality would be nice to have working this way too, like Calendar and Contacts.
Describe the solution you'd like
I'm working on a spreadsheet. I want to message something to somebody about it, so I have to open the Talk in a new tab or a new window and do the switching back and forth to message to the person with the info I need. A side panel seems like it would be a better way to go about this.
If a stay-in-front pop-out window is possible, it could hover over a Wikipedia article while a chat discussion was going on related to that content.
I often find myself right-clicking the Calendar and Contacts icons to open them in another window because I need to transfer info from them to somebody else or to some other medium, like documents or emails. It would be super-clutch if a Calendar side panel showed calendar events that could be dragged into an email and result in an attached calendar event export as an ICS file. Same for a Contacts.
It would also be handy if I could look at the email and copy info into a sidepanel for a calendar event or a contact in my list.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Talk website entry point and how the Calendar and Contacts icons currently open. Define the scope among a side panel, floating panel, pop-out window, or separate page, including the proposed calendar and contact integrations. Done should be a decided, testable interaction design rather than the several alternatives listed here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100