Summary: | A button to share images in the conversation, like the Hangouts one. | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | mgonzlezgmz |
Component: | text-ui | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED LATER | ||
Severity: | wishlist | CC: | kde, mklapetek, s.suther |
Priority: | NOR | ||
Version: | 0.6.3 | ||
Target Milestone: | Future | ||
Platform: | Chakra | ||
OS: | Linux | ||
URL: | http://i.imgur.com/FsP5aep.png | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Image button in Hangout |
Description
mgonzlezgmz
2013-10-12 16:18:44 UTC
Created attachment 82800 [details]
Image button in Hangout
What advantage would this have over drag & drop that we have now. Plus we have a send file button in the toolbar which equates to the same thing, right? If you can provide the information requested in comment #2, please add it. I did not even know about the drag&drop feature. You're right, if we have a "Send File" button that covers all, it makes no sense to have a "Send image" button too that covers the same funcionality. Instead, we could have a webcam integration (having a button that launches the webcam app -kamoso?-, you take the picture, and voilĂ , it's shared). it's even possible? Yes, it would be somewhat possible, but would require changes on both sides (Kamoso and Telepathy). Best would be if Kamoso was either a KPart which we could embed or if it supported kipi plugins (I see some kipi commits in the log, however don't see any in the UI). Other possible solution could be to make the images from Kamoso picture bar draggable, that way you could take a picture and drag it to text-ui and send the file. With Kamoso being a KPart, we could even upload the picture somewhere behind the scenes and paste a link in case direct file transfer is not feasible. However that requires some changes in Kamoso code, so it should be taken there first. Once it has a proper support, we can easily add it on our side. *** Bug 327875 has been marked as a duplicate of this bug. *** |