Feature Request: Send Clipboard Contents/Specify URL to Send to Phone

[GoogleCodeExporter]

Add the ability to Click the Extension Button and get a prompt to send 
Clipboard Contents, or textbox to specify a URL (which can be filled via the 
Paste functionality).

Original issue reported on code.google.com by joseph.c...@gmail.com on 12 Aug 2010 at 5:32

[GoogleCodeExporter]

Original comment by burke.da...@gmail.com on 20 Aug 2010 at 10:38

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm also interested in this feature and would be willing to give it a try 
myself, that is, create a patch for upstream consideration.

However, I am not certain on how the feature should be implemented the best 
way. As of now (correct me if anything I claim followingly is wrong), when you 
click the badge, the extension immediately parses the current web page 
URL/marked phone number and sends it to the phone right away. So even if one 
were to implement a small text box for receiving custom links, you'd still need 
to define what should be delivered to the phone. The current link or the 
entered text? Possibly both in sequence?

Currently, I do not see any other option but to change the default behavior 
from sending out links immediately to having the user specify what is to be 
delivered. He would be able to choose among the following three alternatives 
when clicking the badge:

- Send the current link (HTTP/Google Maps page; this is the current behavior 
except that the user will need to confirm explicitly).
- Enter data (URL, phone number) in a text box, have the extension parse and 
send it.
- Provide a "paste clipboard" button, have the extension parse the clipboard 
content and send it.

Parsing, of course, would comprise checking for validity of the link/number, 
just like the extension does already.

I'd be glad to get any feedback on my proposed approach. Some kind of 
acknowledgement/further directions from Google officials would be especially 
helpful.

Original comment by ttr...@googlemail.com on 25 Oct 2010 at 6:26

[GoogleCodeExporter]

Apologies, I meant to say "icon" instead of "badge" in my previous comment.

Original comment by ttr...@googlemail.com on 25 Oct 2010 at 7:26

[GoogleCodeExporter]

Yes this enhancement would be most welcome,
I could use it to transfer some text in my PC to my phone clipboard which would 
make composing mail and text messages easier

Original comment by edoco...@gmail.com on 7 Jan 2011 at 12:52

[GoogleCodeExporter]

I really would like this enhancement too. I think the implementation could be 
done by adding two icons to chrome, one for sending and opening URL's and one 
for popping up a textbox with an input. I don't know too much about Chrome 
extensions, but it might even be possible to add actions to the right mouse 
click?

I'm willing to give this a try (I have some knowledge about Chrome extentions 
and have also done quite some Android development).

Original comment by dfa...@gmail.com on 30 Mar 2012 at 10:01

[GoogleCodeExporter]

I fixed the issue (see attached patch file). Messages are hard coded in 
English, but that should be easy to fix. The 'send message' box is shown in the 
extension's 'options' page. I know it's not ideal, but it works for me. It will 
be automatically hidden when you're not logged in (yet). The phone will copy 
the text entered to the clipboard and generate a notification stating that a 
custom message has been copied to the clipboard.

I've also attached an image with the extension's options page.

Original comment by dfa...@gmail.com on 6 Apr 2012 at 9:25

Attachments:

• Issue162.patch
• ChromeToPhone.Issue162.png

[GoogleCodeExporter]

I want to install this patch, but i don´t know how to do it. Please can you 
explain me how to install it? 

Original comment by gabrielm...@gmail.com on 11 Jul 2012 at 12:10

[GoogleCodeExporter]

Simply apply the patch against the source code. I assume you're using Windows, 
so try a GUI-based merge tool like TortoiseMerge or WinMerge.

Original comment by ttr...@googlemail.com on 11 Jul 2012 at 1:09

[GoogleCodeExporter]

@gabrielm: For your (and others) convenience, I have uploaded the patched 
extension and app here:

Extension: http://www.tagpulse.nl/ctp/chrome_to_phone_extension.zip
APK: http://www.tagpulse.nl/ctp/chrometophone-android.apk

Step 1: Unzip the zip 'Extension' somewhere on your hard drive.
Step 2: Remove or disable the Chrome extension
Step 3: In the 'extensions' page of Chrome, enable 'Developer mode' (small 
checkbox on the top right).
Step 4: Click on 'Load unpacked extension...' and select the directory of the 
unpacked zip-file from Step 1.
Step 5: Uninstall ChromeToPhone on your phone (if installed)
Step 6: Browse to the 'APK' location (you could also download it on your pc and 
then e-mail it to your phone). Install the APK.
Step 7: Enjoy!

Original comment by dfa...@gmail.com on 16 Jul 2012 at 2:22

[GoogleCodeExporter]

dfa,

Seeing as you know more about this than we do, would it be possible to get this 
updated for manifest version 2?

Original comment by irow...@gmail.com on 8 Dec 2012 at 2:22

[GoogleCodeExporter]

I'd much rather see this feature finally become part of upstream C2P (which, by 
the way, happens to run on manifest version 2 already). Has anyone with commit 
privileges taken notice of this issue yet? 

If the design approach taken (sending messages via the options page) poses to 
be  an obstacle, we should simply try to go for a better solution if that helps 
with pushing the code into the mainline trunk. Keeping separate lines of 
developments is the least desirable solution in my opinion. 

Original comment by ttr...@googlemail.com on 8 Dec 2012 at 1:38

[GoogleCodeExporter]

The APK I uploaded to my domain seemed to not be working anymore, so I applied 
the patch against version 2.3.1 and the APK seems to be working again. The 
chrom extension, however, isn't working anymore with manifest version 2. I'm 
not sure what's wrong, but from what I understand it has something to do with 
that inline javascript is not allowed anymore and it should be in (a) separate 
file(s). I think I can manage that, but I was wondering what you meant with the 
'C2P upstream', ttr? I looked into the trunk of the extension, but that one 
still has manifest version 1.

Original comment by dfa...@gmail.com on 9 Dec 2012 at 9:28

[GoogleCodeExporter]

I've been trying to get it to work with manifest version 2, but since the 
extension relies heavily on in-page and in-line scripts, I can't get it to 
work. I got background.html to work (without translations), but now channel.js 
seems to suffer from the same security violations and I have no clue what kind 
of file that is (it's also minified). Furthermore there are also security 
issues with the oath code, so I actually think it will take quite some time to 
adapt this code to manifest version 2 and I don't have loads of time at the 
moment, so I will have to look into that later on.

Original comment by dfa...@gmail.com on 9 Dec 2012 at 9:57

[GoogleCodeExporter]

With C(hrome)2P(hone) upstream, I was referring to the official trunk line of 
development (as opposed to your private, non-merged patch). I must shamefully 
admit though that I didn't look too thoroughly at the manifest file, you are 
absolutely right that it's still on version 1.

I've recently gone through the process of updating an extension to version 2 so 
I'll take a look at it as well. If you say though that there are minified files 
(without the unpacked versions available) involved things will get ugly.

Either way, upgrading the manifest file warrants a separate ticket which I'll 
try to open today unless someone else jumps ahead of me. 

dfa, did you consider creating a Github repository so that we can 
collaboratively keep updating your patch from upstream until it gets merged 
into the official trunk? 

Original comment by ttr...@googlemail.com on 9 Dec 2012 at 11:09

[GoogleCodeExporter]

I just opened issue 472 (update the manifest file to version 2).

Original comment by ttr...@googlemail.com on 10 Dec 2012 at 12:17

[GoogleCodeExporter]

For those interested: I'm working on an alternative. It's called Message Beam 
and you can do everything Chrome to Phone does, but it adds custom messages, 
selection, encryption and it's also bi-directional (Send from Android to 
Chrome). You can also link more than one device (e.g. your phone and tablet) 
and will in the near future also have different end-points (not only Chrome, 
but also FF, executable and more). For more information check out the plugin 
at: 
https://chrome.google.com/webstore/detail/message-beam-for-android/mlndbhjjfllli
igpnpinfhmiaocogeba . The Android app is not released yet, but you can install 
the APK (just install the Extension, add a device and follow the instructions).

Original comment by dfa...@gmail.com on 19 Jan 2014 at 11:38

[GoogleCodeExporter]

@16: To me, it sounds like you're rebuilding the 2cloud project: 
http://www.2cloudproject.com/

I'd be interested to know what the differences are though, but the C2P issue 
tracker isn't the right place for that.

Original comment by ttr...@googlemail.com on 19 Jan 2014 at 12:16