OpenClip.org Offers Copy and Paste for iPhone Across Apps

[TsuaSai]

http://www.geekbrief.tv/copy-and-paste-for-iphone

[mcdj]

I hate to see all that effort go to waste. Either Apple will do C&P themselves, or will continue to ignore it. Either way, 3rd party cut and paste will remain isolated from Safari, Mail, Notes and SMS...the places we all want it the most...and thereby, as proven by the relatively low interest in MagicPad (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8), will remain for the most part, useless.

[Ntombi]

That's a cool idea, and better than nothing, but I won't be satisfied until Apple implements it across all the platforms. The apps I use C/P the most are native: Mail, Contacts, Safari, and SMS, which means this won't help me much. :(

[TsuaSai]

That's a cool idea, and better than nothing, but I won't be satisfied until Apple implements it across all the platforms. The apps I use C/P the most are native: Mail, Contacts, Safari, and SMS, which means this won't help me much. :(

Yeah i feel the same way. Like you said better than nothing for now.

[wronski]

Very good idea. Pretty much as Apple should have done it, just with support for selections.

[Mr. Giver '94]

I hate to see all that effort go to waste. Either Apple will do C&P themselves, or will continue to ignore it. Either way, 3rd party cut and paste will remain isolated from Safari, Mail, Notes and SMS...the places we all want it the most...and thereby, as proven by the relatively low interest in MagicPad (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8), will remain for the most part, useless.

+1 Since apps can't affect the core applications, these apps are basically a substitute for Notes. Pointless.

[MacRumors]

http://www.macrumors.com/images/macrumorsthreadlogo.gif (http://www.macrumors.com)

Many will remember Proximi's (http://magicpad.proximi.com/) MagicPad (http://www.macrumors.com/iphone/2008/08/04/magicpad-with-copy-and-paste-and-proposal-for-system-wide-copy-and-paste/) [App Store (http://www.macrumors.com/link/http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8)] iPhone application which was the first to offer a 3rd party notepad application for the iPhone with copy and paste functionality. Of course, due to the constraints of the iPhone SDK, Promixi was only able to provide copy and paste functionality within their own application.

Promixi, however, took it a step further and proposed an interface (http://magicpad.proximi.com/video.php) for system-wide copy and paste on the iPhone. While Apple has acknowledged that iPhone copy and paste is in their plans, it has simply not been a high enough priority for them.

Student developer Zac White (http://zacwhite.com/) has since taken matters in his own hands and founded a non-profit, open source, community project called OpenClip (http://www.openclip.org) which is offering iPhone developers a free Copy and Paste framework that will add this functionality to their applications. This will allow copy and paste functionality between supported applications.

OpenClip accomplishes this feat while still following the rules of Apple's SDK. iPhone applications are allowed to read from other application's files but only write to their own. By creating a standard location for each application's "clipboard", applications can "copy" by simply saving data locally and "paste" by pulling the most recently saved data across all applications.

A demonstration of the OpenClip is shown in GeekBrief.tv video (http://openclip.org/) with early versions of Twittelator [App Store (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=284698706&mt=8)], WordPress [App Store (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=285073074&mt=8)], and MagicPad [App Store (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8)].

These same developers have OpenClip-supported versions coming soon with others (http://www.openclip.org/apps.php) pledging support. Developers and users can find more information at OpenClip.org (http://www.openclip.org/main.php).

Article Link (http://www.macrumors.com/2008/08/20/openclip-org-offers-copy-and-paste-for-iphone-across-apps/)

[amusiccale]

I think this is really quite wonderful news. I'm definitely glad someone's stepping up, and the fact that it lies within the SDK rules shows their inventiveness. We will have to wait and see if other developers get on board. It's a shame Apple couldn't make it a priority, though.

[geerlingguy]

...And this is reason #193 why I like owning Apple products—Developer initiative. If Apple doesn't do it, but people want it, it will happen!

I just hope that either (A) Apple supports this in Safari and Mail, or (B) Apple finally gets on the ball and adds Copy/Paste on their own!

[superstrikertwo]

Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)

so sick of iPhone news

So sick of useless posts.

This is a great idea if they can pull it off even better I would definitely use the apps if they were useful of course.

[Eduardo1971]

Cali Lewis is hyperverbal. She needs to slow down.:D

[gibbz]

Very clever method. Hope this gets implemented soon.

[a1016neo]

Meh... I will just wait until the official copy/paste from Apple... Hopefully it's on the short list...

[MacTheSpoon]

Brilliant! Apple devs are so cool. :)

[orbitaldesign]

As exciting as this is, I think it only provides a bandage solution that some developers will use, some won't and then Apple will come up with their own system that may or may not be compatible with this one. Best case Apple's system would override this and basically just work everywhere, worst case you won't be able to copy and paste from an app using this framework to one that uses the Apple solution and vice versa.

Just my two cents.

orbital

[plumbingandtech]

net result. next to worthless.

this will be forgotten right apple ships the official version.

[arn]

net result. next to worthless.

this will be forgotten right apple ships the official version.

Which could be June 2009. No copy/paste in 2.1. and that's not even out yet.

arn

[TheIguana]

Gross that a 3rd party dev seems to be able to find that time to implement this, yet Apple has the snobby attitude of just shrugging it off as something they will get to in a few years. Gosh Apple just hire a developer to implement feature and get it over with, or open up your SDK terms and let a 3rd party implement this fully.

[nagromme]

Nice!

It won't always be needed, but in the meantime even just having it for one or two apps could be VERY welcome.

And it's a reminder to help Apple bump this up the priority list :) (Though I suspect it has long been near the top of what they WANT, just not at the top of stuff they could easily get working in the best way.)

[RobbRock]

looks great hope this comes out soon

[solipsism]

Don't get me wrong, this is nice and clever to use a framework to copy paste to a shared area but it's hardly the cut/copy/paste that people have been crying for.

There is no way to dynamically choose specific text that doesn't the developer didn't account for or include as option. It's clever, but if Apple had given that out people would have been crying that Apple is once again trying to control what and how you do things on their devices.

This video while compelling, does prove that the issues for copy and paste are more complex than simply adding a clipboard to store the data.

PS: Cali looks cute there.

[arn]

There is no way to dynamically choose specific text that doesn't the developer didn't account for or include as option. It's clever, but if Apple had given that out people would have been crying that Apple is once again trying to control what and how you do things on their devices.

This video while compelling, does prove that the issues for copy and paste are more complex than simply adding a clipboard to store the data.

While I think the video doesnt demo it, I believe the copy/paste functionality is more complex than shown. See the UI proposal video.

MagicPad offers discrete copy/paste for any span of text.

arn

[therevolution]

I agree it's not really useful, but maybe it will help light a fire under Apple to ship their implementation. Hopefully that fire doesn't burn down any more buildings. :D

[solipsism]

While I think the video doesnt demo it, I believe the copy/paste functionality is more complex than shown. See the UI proposal video.

MagicPad offers discrete copy/paste for any span of text.

Thanks. i will check out MagicPad.

[TalkAboutApple]

I agree it's not really useful, but maybe it will help light a fire under Apple to ship their implementation. Hopefully that fire doesn't burn down any more buildings. :D

Or any gen 1 Nanos. ;)

I assume the OpenClip works by writing a temp file of a predefined structure. That's pretty clever thinking, in fact not a bad way to implement the "real" one.

[k'five]

Awesome. Thank you dev's, for picking up the slack, while Apple happily ignores what their users want.

Oh, but "we're going to clean up in the Enterprise market"... without copy & paste... right.

Perhaps in Apples indifference, they'll simply go along with the open source version of C&P. If they ever get a programmer off trying to stop the phone from hanging and crashing like nuts.

Grumblegrumblegrumble....

[Ntombi]

Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)

so sick of iPhone newsDid you miss the prominent use of the word iPhone in the title? :rolleyes:


I do like that the developer can choose whether to support HTML or plain text too; that's a cool add-on.

I'm going to be interested to see which developers/apps sign on with this "solution."

[solipsism]

While I think the video doesnt demo it, I believe the copy/paste functionality is more complex than shown. See the UI proposal video.

MagicPad offers discrete copy/paste for any span of text.

Just went to their site and watched the video. I was so impressed that they realise the implementation Apple needs has to be more thought out for future usage and their ideas as to how to best implement it correctly that I bought their app even though I really don't think I'll be using it.

[deannnnn]

I hate to see all that effort go to waste. Either Apple will do C&P themselves, or will continue to ignore it. Either way, 3rd party cut and paste will remain isolated from Safari, Mail, Notes and SMS...the places we all want it the most...and thereby, as proven by the relatively low interest in MagicPad (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8), will remain for the most part, useless.

YEah I agree with you.
It really is a great idea... but wouldn't it be easier if Apple just implemented it themselves?!

coughmmswouldbegreattoocough

[jbernie]

Sad that an indi developer can come up with something this respectable while Apple twiddles thumbs and can't introduce something this simple after so long.

Though to be fair, as i found out the other day, there is no undo function in email on a Blackerry 8700 which would be viewed as very useful when you accidentally select the wrong command.

[solipsism]

...Apple ... can't introduce something this simple...

Even the creators of OpenClip and MagicPad acknowledge that it's not simple.• http://magicpad.proximi.com/video.php

[ivladster]

i think apple feels pretty dumb now, that people are doing this on their own. C'mon Apple. I am sure its not that hard. If Zack can do it, you can perfect it.

But, I would love seeing iPhone running smoothly before Copy&Paste though.:)

[DipDog3]

I glad they decided to go with the tap and hold instead of the stupid double tap. It looks pretty good and at the rate Apple is moving, this might be our best solution.

Just need a Safari app that takes advantage of it.

So where is this info being copied to a pic, a contact??

[koobcamuk]

I glad they decided to go with the tap and hold instead of the stupid double tap.

How doesn't tap and hold conflict with the magnifier? :confused:

[solipsism]

I glad they decided to go with the tap and hold instead of the stupid double tap. It looks pretty good and at the rate Apple is moving, this might be our best solution.
They only show tap and hold because it's not copying from an text input field where the Magnifier is used. I'm betting that doublet-tap for text input fields is still in place.


How doesn't tap and hold conflict with the magnifier? :confused:
It would conflict unless there was another action involved or an additional time delay.

[hirshnoc]

....I actually know and have met Paul Colligan too.

[ppc_michael]

Wait, I went to college with that girl. Weeeird.

[Trajectory]

Only Apple will be able to enable the kind of copy and paste we all want, across all applications. But I'm sure that's not easy and could be a security issue.

[Juo100]

This is an ok alternative I suppose. It still wont integrate with Safari, Mail or Contacts and those are the places Im most likely to want to copy / paste content.

dude, is it me, or is cali lewis pretty hot?
She looks awkward to me

[daneoni]

Did anyone else notice that lag when she was scrolling through her 'tweets'?. Anyway, it seems like a good idea but i just dont think it'll take off...but...we'll see

[MacBoobsPro]

What I dont get here is when she 'held' her finger on the screen the C&P window popped up. Doesnt that clash with the magnifying glass? What if you wanted to get the magnifying glass instead of C&P?

I still think the way I mentioned before is a much more elegant way of implementing cut and paste.

Just tap and hold (to get around bringing up the magnifier) at the start or end of the text you wish to copy or cut. Then while still holding drag (highlight) over the text you wish to copy, when you release your finger a menu could pop up with 3 options 'cut, copy or paste'. Select what you want. Go to where you require the new text to be pasted then tap hold and release and the same menu pops up so you can now choose 'paste' from the menu.

When highlighting the text accuracy maybe a little bit of a problem so to improve it you move the cursor before hand to the start of the text you wish to copy to help the phone select the correct starting point.

EDIT: HOLY CRAP they nicked my idea! I just watched the other video. Good job I submitted it to Apple ages ago. My way also doesnt require the extra tap. :D At least what these guys have done shows it can be done and will hopefully push Apple into implementing it.

[bobbleheadbob]

This is nice, but I'm waiting for it to become part of the basic iPhone OS. Hopefully, :apple: will get around to supporting something like this officially soon. It's overdue.

[Scott Ott]

These developers will spur Apple on to release a native version of copy-and-paste. Therefore, this is good work.

For several weeks, my WordPress app icon has languished on my homescreen untouched because I do not blog without posting links, and I can't post links without copy-and-paste.

At this point, the trick is to get a URL from Safari to the WordPress app. Oddly enough, there is a snippet of Javascript that already does this within Safari, creating a blog post in the web-based version of WP, but not with the new WordPress app.

A potential, partial, solution would be for Google Reader to join OpenClip so we could save a story in Google Reader, then copy the URL from there to the WordPress app. However, since the Google Reader is a web-based app that runs in Safari, perhaps that could not work under Apple's iPhone SDK.

Think with me now...

Another possibility would be for the WordPress app to let you email a new blog post to the app. This way, you could email it from Google Reader, which would initiate a new blog post.

Some days, I wish I had fewer ideas, and more coding skill.

Thanks to all those doing this good work...including Cali for bringing it to my attention.

Scott Ott, editor
ScrappleFace.com

[n8236]

I hate to see all that effort go to waste. Either Apple will do C&P themselves, or will continue to ignore it. Either way, 3rd party cut and paste will remain isolated from Safari, Mail, Notes and SMS...the places we all want it the most...and thereby, as proven by the relatively low interest in MagicPad (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=286616920&mt=8), will remain for the most part, useless.

God damn it! It's so true!! I hate you for pointing that out! :D

I'm so glad the guy is doing this though! I hope iPhone lovers out there embrace his efforts and give him a ton of props for what he's doing for the Apple community. Apple is snoozing on this and I hope this guy gets something out of this, actually a lot!!

[blakespot]

Despite how great copy and paste is for the iPhone, I've still gotta say that the coolest thing about Cali's story is that my daughter (http://flickr.com/photos/blakespot/2755871565/in/set-72157606687263493/) was pictured at the end. :-)

(Like daddy, she digs the Drobo too!)




blakespot

[Ludde]

Maybe this is how Apple recruits new people ;D
They used copy&paste instead of an interview...or something.

[Hattig]

Implementing data sharing isn't the complex part of the CnP issue on the iPhone.

It's providing system-wide support at the UI level, i.e., no coding required for applications using system UI components. Implementing cut and paste for each UI component in a consistent and natural manner is probably what is taking Apple time.

But once it is done, then any system text area, image, etc, will be cut and pasteable.

However for custom UI components you would have to implement your own cut and paste anyway, and in the absence of a system CnP framework this one makes sense. I guess it's just a file or SQLite entry that records the mime-type of the data, the data (possibly base64 encoded for binary), a plaintext representation, and the time it was copied/cut. This could logically be extended to provide a clipboard history quite easily, so I presume this code can do that.

And it is rather appalling that Apple have taken so long to get an implementation of cut and paste, and it could be even longer before one appears. Still, I guess if they're doing it the 'right way' ...

[Jelite]

I've no use for c&p but i enjoyed Cali "C.A.L.I" Lewis explaining the program to me.

[andiwm2003]

it's unlikely that apple apps will support this. the most likely use would be copying part of a text and past it into an email or copying a number and past it in the phone app. since that won't be possible whats the use of this app? and in a few month apple will introduce their own copy paste that will work systemwide anyway. so it's a nice feat and accomplishment but all the work will unfortunately go to waste.:( well i still hope they get some decent money out of this!

[TheSpaz]

How is "OpenClip" not breaking the Apple SDK NDA? I thought developers were not allowed to discuss the SDK. Hmmm... I smell something bad here.

[Rot'nApple]

Cali Lewis is hyperverbal. She needs to slow down.:D

Cali Lewis is just like the iPhone 2.0.2 software release. She's, dare I say it, "snappier"! :rolleyes:

[martijn.s]

Or any gen 1 Nanos. ;)

I assume the OpenClip works by writing a temp file of a predefined structure. That's pretty clever thinking, in fact not a bad way to implement the "real" one.


clever ?

that's how copy paste has worked since 1982 (lisa)

no, the problem is not how to share the data, but how to handle selection with a device that has no mousedown.

OpenClip is a great initiative, and, once Apple has figured out how to do Copy and Paste right OpenClip can be updated to use Apple's API.

don't believe their excuse about priority, it is one, but it's very complex.

their number one priority is usability, and, think about it, is it really possible to have an intuitive version of copy paste for a pointing (no click) device ?

i don't think so, it will always involve some acrobatic use of two fingers, it might be easy to use, but will never be easy to learn, or remember,or elegant.

(ease of use = easy to learn, remember, use, elegant and productive)

[martijn.s]

net result. next to worthless.

this will be forgotten right apple ships the official version.

no, see above.

[martijn.s]

i think apple feels pretty dumb now, that people are doing this on their own. C'mon Apple. I am sure its not that hard. If Zack can do it, you can perfect it.

But, I would love seeing iPhone running smoothly before Copy&Paste though.:)

it is VERY VERY hard !

[Scooterman1]

We definitely need the Copy & Paste from Apple themselves. This way, it should work on everything that we need it for. Email, etc.

[Mal]

Unlike some of the doubters here, I can readily see Apple hiring this developer or purchasing their software from them to integrate it into their own software. They've been trying to figure out a good way to make it work: this is it. And we've seen from previous examples that Apple's not afraid to buy up something and integrate it into their own products or build it up to a whole new product (SoundJam, anyone?)

jW

[bytethese]

Cali Lewis is hyperverbal. She needs to slow down.:D

That I don't mind, I hate when people talk slow. It's how cute she was that really distracted me. :)

[bytethese]

This is pretty neat and I figured that this shouldn't be hard to implement given 3rd party apps use the same structure. The real "meat and potatoes" if you will is being able to copy from web pages into emails, Twitter to Facebook, Contacts to a LJ post, etc.

Please Apple, PLEASE. Elevate the priority on this one. Sheesh. :)

[Kwill]

1. My prediction is that Apple will surprise everyone and implement C&P in September.

2. Cali needs to slow down her intake of caffeine.

[sonicwind]

What's not going to workout about this is Apple will release a much more elegant cross app cut, copy, paste, shortly.

[Col127]

awesome! hope this picks up with developers.

[squeller]

OpenClip is a great initiative, and, once Apple has figured out how to do Copy and Paste right OpenClip can be updated to use Apple's API.

don't believe their excuse about priority, it is one, but it's very complex.
Are you suggesting that Apple designed the iPhone's UI without having support for copy&paste in mind, and thus need to "figure out" how to retrofit it into the UI? That's hilarious.

[SpinThis!]

I would guess Apple has half a dozen implementations of copy/paste cooked up in the lab right now, 3 of which are probably up for consideration, and 1 is so radical that we all didn't think of it before (but may not be ready for prime time).

The only thing Apple is "figuring out" is which one to use. Jobs and company like to use things before they go into any product—I would guess even more so with such an integral feature like copy/paste—so what better test than to try each out for awhile and decide if it's worth keeping?

These 3rd party developers may have stumbled upon gum but is it worth chewing on forever? That's what Apple has to kick around now. And it has to be intuitive enough that developers and everyone else is like "OK, that's it. I couldn't have done it any better."

So it's not just copy/paste... it's getting the paradigm to work well so they don't have to change it up. What Apple implements is likely going to be there 10 years from now just like the cut/copy/paste commands in the menu bar today.

[trever.mendez]

The more serious this gets the more likely Apple will seriously look into it. IF some serious developers, say AOL & Facebook, jump on board can you imagine Apple's reaction. It would be serious to say the least. Proximi made good strides with MagicPad and their demo video, but now thanks to Zac White's addition, we have a seriously viable solution. Let's seriously support every developer to add this framework to their app. By the way, I AM SERIOUS!

[Sean Dempsey]

I have never once needed to copy or paste on my iphone.

[slapppy]

Wow, I can't believe an outside developer is providing copy and paste. Beats Apple to the punch. Good job dev, bad job Apple.

[sleepingworker]

While Apple has acknowledged that iPhone copy and paste is in their plans, it has simply not been a high enough priority for them.


Unbelievable. One of the most used set of commands in any program and Apple doesn't consider it a priority for their iPT or iP.

[ThunderSkunk]

I have never once needed to copy or paste on my iphone.

Well, someday, when you actually want to start using your device for more than "OMG, Liz, I'm at the mall and like, you've got to see Jenny's shoes, LOL, you'll be able to, thanks to these guys.

[bretm]

Sad that an indi developer can come up with something this respectable while Apple twiddles thumbs and can't introduce something this simple after so long.

Though to be fair, as i found out the other day, there is no undo function in email on a Blackerry 8700 which would be viewed as very useful when you accidentally select the wrong command.

My guess - apple has already created and is testing 4 or 5 different ways. Apple knows where they're going more than most and they know if a cerain function or gesture is going to interfere with future incarnations of the iphone or os. This is a big deal and they only get one shot to get it right. They shoul've done it right the first time.

I think they dug a hole that was deeper than they realized with the first version without copy/paste. They used all the most intuitive gestures and furnctions for things like the loop. Thinking they'll just come out with another way soon. I think they've painted themselves in a corner and they really have to fix the problem right. The right way would probably be to change the loop function somewhat. Other methods are bandaids.

Should've been done before the original release. That's the bottom line.

[WoFat]

Crap or get off the pot, Apple. How difficult can this be if some clod found a work around to do what the masses demand? Once again shoe horning users into doing things their way.

[sleepingworker]

I have never once needed to copy or paste on my iphone.

How about on your PC? Many of us use the iPhone like a mini PC that happens to also be a phone.

[bretm]

I have never once needed to copy or paste on my iphone.

Email: here's your ups tracking number... x83q90djkjadle98390q0e9tqtet89

Address: Here's an address to get directions for 61897 Opelikiea Sausageway Ave, Boomerstown, ST, 30987

Web: the website is somethingsomethingjewelryandbridalcakestoday.com

Edit a post: Gosh I'd like to reply to just that one little sentence on my iphone without having to quote the entire 2 page diatribe! Or without holding down the delete key for 3 minutes and hoping I don't delete too much and have to retype it!

How many more do you need? I've said it before. The number one reason the computer word processor was better than a typewriter was the ability the rearrange. To copy and paste. Typing anything, that is, communicating, on the iphone is akin to a typewriter. And isn't the iphone supposed to be a communication device? Not a typewriter.

[mrgreen4242]

If Apple doesn't add a CnP system before the end of the year they are going to end up losing out on implementing their own method. Here's why: people will replace the core applications with ones that are OpenCopy compatible. The big issue is that you can't caopy text from an email or webpage as those are the two most used apps.

There's really no incentive for someone to create and sell/give away a new mail application or web browser because Apple's "free" solution works quite well (or at least well enough). But, if someone created a mobile Mozilla, or if Opera ported Opera mini to the iPhone and supported OpenClip people would buy it. Same goes for a web browser that worked more or less like Safari but supported OpenClip.

Once people start moving away from Apple's bundled software for a "superior" solution it's going to end up costing Apple in the end; on the other hand Apple with take 30% cut of those sales, so maybe it'll be in their best interest.

Either way, if Apple wants to do something they need to do it now or risk being left behind. Semi-related note, why are there no other companies releasing web browsers for the iPhone? Mobile Safari laid a great framework for how handheld web apps should work, but there's lots of room for improvement, both in features and in stability. Seems like Opera or Mozzila would be all over the platform as a way to "get in early" and avoid an IE like situation.

[GQB]

What I love about this is that it finally presents a complete visual discussion of the problem space.
Wonderful piece of work, and I have to think that having it out there could influence the direction.

One criticism...
Why the extra step to copy? (click-hold on a selected block.)
Most Unix terminals have long supported the idea that simply selecting text immediately puts it onto the clipboard. This is a widely used standard and works really well.
Why not just immediately put selected text on a clipboard?

[Cleverboy]

It occured to me that Apple already supports client-side databases in Safari, and that Google Translate puts this feature to good use. For instance, put a few translations through Google Translate for the iPhone, and then go to your "Settings" for Safari. You'll see Google has created a database capable of holding up to 5MB of data.

The only limitation to using this is presumeably a "domain" restriction, like the one used with "cookies" in Javascript. If however, the domain is the localhost/nothing (or the client's machine itself, however referenced), theoretically all apps could create a temporary HTML page, and run some Javascript to get access to a common database. This not only opens the door to a CLIPBOARD, but to a MULTI-CLIPBOARD (if one wanted, although I HATE multi-clipboard systems with a vengeance).

The reason why this seems very doable, is that there is already a "bookmarklet" that allows Safari to have a "clipboard" feature, simply by running the bookmark. That someone is able to post clippings of text between different websites speaks to there being NO security restriction in this area.

Without looking into the OpenClip code, I'd imagine its based off of this concept, or something potentially similar. In anycase, good job. Someone's been thinkin'.

~ CB

[martijn.s]

Unlike some of the doubters here, I can readily see Apple hiring this developer or purchasing their software from them to integrate it into their own software. They've been trying to figure out a good way to make it work: this is it. And we've seen from previous examples that Apple's not afraid to buy up something and integrate it into their own products or build it up to a whole new product (SoundJam, anyone?)

jW

they don't need him.

this isn't a lot of code at all.

[martijn.s]

Are you suggesting that Apple designed the iPhone's UI without having support for copy&paste in mind, and thus need to "figure out" how to retrofit it into the UI? That's hilarious.


no, i'm saying that a hand held device that u use with a finger just can't have a good copy paste.

it's not something they forgot to implement, it's just impossible to do in an intuitive/mode-less way if u also want to allow scrolling, inserting with a finger.

i'm also saying that the excuse of "not being a priority" is BS, they are probably still looking for a way to do it without making any compromises.

what's hilarious exactly ?

[martijn.s]

Wow, I can't believe an outside developer is providing copy and paste. Beats Apple to the punch. Good job dev, bad job Apple.

i doubt that Openclip is good enough for a mainstream product.

[Cleverboy]

they don't need him.
this isn't a lot of code at all. Agreed. The credit is in taking the initiative and in seeing a possibility. If the implementation of the framework is of sufficient sophistication however, I can't imagine they wouldn't considering evaluating the hire however.

Regarding the idea above... if this has nothing to do with the implementation, OpenClip should consider it as a bridge to PASTING to and COPYING from Safari. Worth a thought.

~ CB

[Mal]

they don't need him.

this isn't a lot of code at all.

Doesn't have anything to do with the amount of code, it's about who owns the technology (in this case, the implementation of copy and paste) and gaining the rights to use it.

jW

[Cleverboy]

Doesn't have anything to do with the amount of code, it's about who owns the technology (in this case, the implementation of copy and paste) and gaining the rights to use it.
jW So... you're thinking that Zac White "owns" the OpenClip framework, and that it is his technology that Apple would need to pay him for, if the solution they've been working on turns out to be similar when finally implemented? Yeah, I disagree completely. With due respect to Zac, I believe what he's done, is more akin to the HTML specification as an open standard. People "support" open standards. They don't need to license them. That said, people certainly pay for talent.

~ CB

[Mal]

So... you're thinking that Zac White "owns" the OpenClip framework, and that it is his technology that Apple would need to pay him for, if the solution they've been working on turns out to be similar when finally implemented? Yeah, I disagree completely. With due respect to Zac, I believe what he's done, is more akin to the HTML specification as an open standard. People "support" open standards. They don't need to license them. That said, people certainly pay for talent.

~ CB

I didn't necessarily say he owns it. If he chooses to patent his method, however, he would have full rights to it and could then license it as he chooses.

At this point, since that's not the case so far as we know, it would be more about paying for the talent, and Apple doing the right thing in crediting him for his work.

jW

[dejo]

How is "OpenClip" not breaking the Apple SDK NDA? I thought developers were not allowed to discuss the SDK. Hmmm... I smell something bad here.
I, too, think that this OpenClip framework violates the SDK, but in my opinion, a specific section of the SDK Agreement. But because I am also bound by the NDA, I cannot reveal the specific section I have in mind.

[bpl323]

Hope this lights a fire under Apple's bottom.

[TheSpaz]

Everybody wants, wants, wants, wants new features and then when we get the new features we're like: It lagggsss! I hope the next update fixes it. Why is Safari crashing when I try to paste? I keep on getting the magnifying glass. I need a video walkthrough on how to copy and paste. Blah blah blah. Let's have Apple FIX what we have now and let them sneak copy and paste when we're not all expecting it (like saving images in Safari).

[Cleverboy]

I didn't necessarily say he owns it. If he chooses to patent his method, however, he would have full rights to it and could then license it as he chooses.

At this point, since that's not the case so far as we know, it would be more about paying for the talent, and Apple doing the right thing in crediting him for his work.

jWBy calling it "openclip", labelling it "open source (http://www.openclip.org/faq.php)" and omitting any form of licensing documentation with the package, patent rights could more than plausibly be seen as the antithesis of what he has in mind. So, I get what you're saying, but I'm thinking its a moot point.As an open-source, non-profit project, OpenClip is completely free.
~ CB

[RedTomato]

I can see a possible security hole in this.

Suppose:

1. Evil app (which is a free download from the Apple store) contains some specially crafted code in its default clipboard storage location.

2. Second app polls the default clipboard location in the evil app, and loads the contents into its own clipboard location.

3. Code is somehow run (maybe through buffer overflow) and creates some unintended consequences (screen corruption, password grabbing or something else).

Does this make sense?

[Stewie]

...And this is reason #193 why I like owning Apple products—Developer initiative. If Apple doesn't do it, but people want it, it will happen!

I just hope that either (A) Apple supports this in Safari and Mail, or (B) Apple finally gets on the ball and adds Copy/Paste on their own!

Are you saying that Developers for other platforms don't step up and provide missing functionality? I am a little confused as I thought that was the sole purpose of developers.

[squeller]

no, i'm saying that a hand held device that u use with a finger just can't have a good copy paste.

it's not something they forgot to implement, it's just impossible to do in an intuitive/mode-less way if u also want to allow scrolling, inserting with a finger.

i'm also saying that the excuse of "not being a priority" is BS, they are probably still looking for a way to do it without making any compromises.

what's hilarious exactly ?
What's hilarious? The thought that they still need to figure out a proper way to do it. You can't be serious.

You're basically saying that Apple thought "Gee, that's hard to implement in an intuitive way, let's work on that later". Do you really think something like that would happen on a project like the iPhone?

Or to put it differently: the touch interaction on the iPhone surely was one of the biggest design obstacles they had. They'd be nuts to have no up-front design on basic features that they might want to implement later.

[johnlandis]

Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)

I wonder how much this will cost?

[Dudeman486]

I can see a possible security hole in this.

Suppose an evil app puts some specially crafted code into its default clipboard storage location, then when that clipboard is loaded by another app, somehow it may have unintended consequences (buffer overflow, screen corruption, or something else).

that is a very good observation. and it appears that apple is not going over apps too thoroughly before launching them in the app store, so they might not catch a malicious intent in an app. and if this happens, it's only a matter of time until people's iphones start bricking/malfunctioning, and the pundits rejoice with headlines such as "iPhone Hacked!" "Apple fails at security!" and then all the blame will go on apple INSTEAD of the openclip founders, because that's just how media works.

I'd be wary of openclip.

[overcast]

This isn't rocket science.

Use the existing magnifying glass positioning system, except when you slide over text it highlights and automatically copies. Just like from within a shell in Unix. To paste, simply use the magnify bubble to position and either tap a new "paste" key, or simply have a persistent bubble that asks you if you wish to paste or clear clipboard. DONE.

[Trajectory]

This isn't rocket science.

Use the existing magnifying glass positioning system, except when you slide over text it highlights and automatically copies.

Then how will you just move the cursor without highlighting the text and copying it?

They'll need a new gesture to do this. A double tap where you keep your finger down on the second tap might work. Then you just drag your finger to highlight the text you want. When you remove your finger, a clipboard app pops up giving you the option to copy or cut the selected text. A tiny clipboard icon can appear in the system bar next to the battery indicator. When you tap on it, it will pop open the clipboard asking to paste the contents at the cursor location.

[jbernie]

i doubt that Openclip is good enough for a mainstream product.

Given every single post of yours in this thread is very negative about the product and/or the developers is there something you need to share with us? Like a conflict of interest in relation to a different product that isn't available?

[Cleverboy]

I can see a possible security hole in this.

Suppose:

1. Evil app (which is a free download from the Apple store) contains some specially crafted code in its default clipboard storage location.

2. Second app polls the default clipboard location in the evil app, and loads the contents into its own clipboard location.

3. Code is somehow run (maybe through buffer overflow) and creates some unintended consequences (screen corruption, password grabbing or something else).

Does this make sense? One somewhat obvious problem with your "security flaw". Once the "evil app" as you say, has been installed on the machine, it can generate this "buffer overrun" on its own.

The only possible advantage, is the narrow possibility that an inter-app copy/paste flaw might unintentionally expose the private data of an app with sensitive information in it to a malicious app looking to exploit it. The steps needed to even arrive at the "exposure" point of an attack would be so unlikely, even in the event that the mythical "buffer overrun" flaw even existed in the code in question.

Just saying.

~ CB

[bj3949]

No matter what any developers try, they won't be able to do a REAL Copy and Paste like Apple will introduce shortly. That's the truth RUTH!!

Simply because Apple won't allow it to happen :)

[overcast]

Then how will you just move the cursor without highlighting the text and copying it?

They'll need a new gesture to do this. A double tap where you keep your finger down on the second tap might work. Then you just drag your finger to highlight the text you want. When you remove your finger, a clipboard app pops up giving you the option to copy or cut the selected text. A tiny clipboard icon can appear in the system bar next to the battery indicator. When you tap on it, it will pop open the clipboard asking to paste the contents at the cursor location.
Keep it even easier. Double tap drag and highlight, double tap paste.

[sushi]

Everybody wants, wants, wants, wants new features and then when we get the new features we're like: It lagggsss! I hope the next update fixes it. Why is Safari crashing when I try to paste? I keep on getting the magnifying glass. I need a video walkthrough on how to copy and paste. Blah blah blah. Let's have Apple FIX what we have now and let them sneak copy and paste when we're not all expecting it (like saving images in Safari).
Well said.

Nothing would be worse than for Apple to implement a flawed copy and paste feature.

What's hilarious? The thought that they still need to figure out a proper way to do it. You can't be serious.
This may not be as easy as one would think considering the variety of applications and data will be able to be copied and pasted.

I can see a possible security hole in this.
<snip>
Plausible perhaps.

Depends on how the data is shared.

The only possible advantage, is the narrow possibility that an inter-app copy/paste flaw might unintentionally expose the private data of an app with sensitive information in it to a malicious app looking to exploit it. The steps needed to even arrive at the "exposure" point of an attack would be so unlikely, even in the event that the mythical "buffer overrun" flaw even existed in the code in question.
No so quick.

How will the app store and protect the data?

If it is a specific location in memory, that is protected from being moved, deleted, overwritten, then it would be possible for another app to find this location.

Getting back to the copy and paste feature. Comparing adding this feature verses fixing updating the OS, it's obvious which one Apple is going to focus on. I understand completely why Apple does not want app generated background tasks and won't allow apps to do this -- at least for now.

[RedTomato]

The only possible advantage, is the narrow possibility that an inter-app copy/paste flaw might unintentionally expose the private data of an app with sensitive information in it to a malicious app looking to exploit it.

Thanks for giving this some consideration. That's an interesting point. What kind of data is likely to be cut and pasted?

I would suggest strong passwords or credit card numbers as example of things that are hard to remember and might be cut and pasted from one place into another.

An evil app that is often run, e.g. a screensaver (I don't know if the iPhone even *has* screensavers) could then regularly poll the clipboard locations of other apps and store any info it finds.

[Cleverboy]

No so quick.
How will the app store and protect the data? The "app store" doesn't have to protect anything. There is simply a protected nature to the way 3rd party native applications exist on the iPhone.
If it is a specific location in memory, that is protected from being moved, deleted, overwritten, then it would be possible for another app to find this location. Seems like that's the technique being discussed. I can't quite tell what you're implying though.
I understand completely why Apple does not want app generated background tasks and won't allow apps to do this -- at least for now. Copy & Paste has nothing to do with background tasks. Apple hasn't implemented this due to time constraints, and moreover, the sticking point isn't simply the amount of time it would take to implement it, but agreement on what the best method would be for the feature moving forward into the future AND the documentation and QA related to perfecting that method (security being just one of many issues). Once Apple has determined what the method will be, they'll need to coordinate that vision to everyone involved and there won't be much room for changing your mind later.
An evil app that is often run, e.g. a screensaver (I don't know if the iPhone even *has* screensavers) could then regularly poll the clipboard locations of other apps and store any info it finds.This is another reason why the iPhone isn't allowed to have *3rd party* background applications. Each application must QUIT before another is launched. There is no "polling" because at the time the application is run, no other 3rd party app is running. I think this was a very shrewd move on Apple's part.

My vision of Apple's "copy & paste" would also include a "timeout" on the clipboard, whereby the clipboard can be manually cleared from the "Settings" area, and also set to auto-erase after a particular time-out period. I don't think the iPhone should suffer an indefinite clipboard that only erases on reboots. It would be great to know that the clipboard does its own housekeeping after you're done with the data (or if you liked, you could set it to never auto-erase, and even survive reboots). I think any iPhone "clipboard" should not exist in "memory". In my opinion, that would be a mistake in resource utilization.

~ CB

[happydude]

nice how apple hasn't done it yet but a student developer with free time could. common, apple!!

[kjs862]

Saw this earlier today, but just getting to it now. That chick reads too quick, but shes cute so its ok.

The copy and paste seems good and all, but I think I'm just going to wait until Apple officially releases their own.

[alchemistmuffin]

This is the perfect concept, except that one thing....

Apple has a KILL SWITCH....

Even if the product is launched, Apple might pull the KILL SWITCH on the program, and send cease and desist to the OpenClip.org group, since it's a violation of terms of agreement....

Copy and Paste requires a background process, which Apple won't allow... Even if the copy and paste works with individual code, the copied text end up being on the background process, which by the way, a signal for Apple to turn on the KILL SWITCH....

[mashkina]

I would guess Apple has half a dozen implementations of copy/paste cooked up in the lab right now, 3 of which are probably up for consideration, and 1 is so radical that we all didn't think of it before (but may not be ready for prime time).

The only thing Apple is "figuring out" is which one to use. Jobs and company like to use things before they go into any product—I would guess even more so with such an integral feature like copy/paste—so what better test than to try each out for awhile and decide if it's worth keeping?

These 3rd party developers may have stumbled upon gum but is it worth chewing on forever? That's what Apple has to kick around now. And it has to be intuitive enough that developers and everyone else is like "OK, that's it. I couldn't have done it any better."

So it's not just copy/paste... it's getting the paradigm to work well so they don't have to change it up. What Apple implements is likely going to be there 10 years from now just like the cut/copy/paste commands in the menu bar today.

I agree completely. Apple's implementation will be the simplest for the user. I don't like to use sliding menus for every action you want to perform on the iPhone. I bet, cut&paste will be based on multitouch gestures: double tap while holding on the second tap, immediately sliding to select the text, and finally some gesture to do the copy (no sliding menus whatsoever).

[arn]

This is the perfect concept, except that one thing....

Apple has a KILL SWITCH....

Even if the product is launched, Apple might pull the KILL SWITCH on the program, and send cease and desist to the OpenClip.org group, since it's a violation of terms of agreement....

Copy and Paste requires a background process, which Apple won't allow... Even if the copy and paste works with individual code, the copied text end up being on the background process, which by the way, a signal for Apple to turn on the KILL SWITCH....

You should re-read the main article. There is no background process required.

arn

[TheSpaz]

This is the perfect concept, except that one thing....

Apple has a KILL SWITCH....

Even if the product is launched, Apple might pull the KILL SWITCH on the program, and send cease and desist to the OpenClip.org group, since it's a violation of terms of agreement....

Copy and Paste requires a background process, which Apple won't allow... Even if the copy and paste works with individual code, the copied text end up being on the background process, which by the way, a signal for Apple to turn on the KILL SWITCH....

It's not a background process. It stores the data in a universally accessable folder (possibly in the Media folder) that other apps have access to. All the other developers have to do is read or write to that folder.

[Cleverboy]

You should re-read the main article. There is no background process required.
arn And moreover, the "kill switch" so often bandied about is to be used on "malware" not apps Apple simply doesn't like (it is a "nuclear option" that remains generally undefined). As well, copy/paste is not it's own application... It is an agreed upon framework that numerous developers would incorporate into their code. Worse than any "kill switch" Apple could simply choose to make participating apps vanish from the store if they are engaged in behavior inappropriate to Apple's guidelines.

People need to keep the "kill switch" in perspective.

~ CB

[domness]

First of all, the presenter in the video clip is hot! :)

Second, this is such a good idea, however, for those who like to post notes and emails etc from a clipboard will be stuck until apple release an official version of copy and paste for the iphone.

[ldkaplan]

There's really no incentive for someone to create and sell/give away a new mail application or web browser because Apple's "free" solution works quite well (or at least well enough). But, if someone created a mobile Mozilla, or if Opera ported Opera mini to the iPhone and supported OpenClip people would buy it. Same goes for a web browser that worked more or less like Safari but supported OpenClip.


I would pay for a new mail app...this one stinks. There is no search or sort off messages. Who gives a hoot about enterprise Outlook if you can't search your email.

And Safari? I'd like to have a browser that let me add in different searches like Firefox...we need Mozilla for iPhone. And since FF is free...I hope it's them!

[ldkaplan]

I agree completely. Apple's implementation will be the simplest for the user. I don't like to use sliding menus for every action you want to perform on the iPhone. I bet, cut&paste will be based on multitouch gestures: double tap while holding on the second tap, immediately sliding to select the text, and finally some gesture to do the copy (no sliding menus whatsoever).

I'm thinking it will be a second tap, not a double tap. A finger is not detailed enough to hit the right spot so magnifying glass is still need to find the exact start and stop spots.

So right thumb down for magnifying glass and getting to the start spot. Left thumb down for starting the highlight while you slide right thumb (Selecting). Left thumb up to copy.

For paste, right thumb down where you want to paste. Left thumb double tap to paste.

[VforVelveta]

Looks like it won't be around for long, Gruber's got a nice piece on it. Apparently it'll be broken come 2.1...

http://daringfireball.net/2008/08/raining_on_the_openclip_parade

[alchemistmuffin]

It's not a background process. It stores the data in a universally accessable folder (possibly in the Media folder) that other apps have access to. All the other developers have to do is read or write to that folder.


Have you READ the SDK agreement MORE CLOSELY? I am a developer, and from what I have read in the agreement, I think what the OpenClip.org is doing is a violation of the SDK agreement, and also for Apple's perspective, considered a Malware in some way, and could end up enabling the KILL SWITCH....

Also, the framework the OpenClip.org is using is 2.0, NOT THE 2.1 beta that Apple STRONGLY recommended users to use in developing a MAJOR NEW VERSION of the app....

2.1 has A LOT OF difference from 2.0. I can't tell you a lot about framework, but the framework that OpenClip is planning to use will enable the KILL SWITCH function in the iPhone OS.....

[k'five]

Have you READ the SDK agreement MORE CLOSELY? I am a developer, and from what I have read in the agreement, I think what the OpenClip.org is doing is a violation of the SDK agreement, and also for Apple's perspective, considered a Malware in some way, and could end up enabling the KILL SWITCH....

Also, the framework the OpenClip.org is using is 2.0, NOT THE 2.1 beta that Apple STRONGLY recommended users to use in developing a MAJOR NEW VERSION of the app....

2.1 has A LOT OF difference from 2.0. I can't tell you a lot about framework, but the framework that OpenClip is planning to use will enable the KILL SWITCH function in the iPhone OS.....

MORE CLOSELY? More closely than what?
KILL SWITCH KILL SWITCH KILL SWITCH!!! Jeez kid, put THAT speedball down AND RELAX.

If Apple doesn't like it, they're not going TO ALLOW it in the appstore to begin with, since IT'S already getting this MUCH exposure going in. But I hear ya, you like saying KILL SWITCH.

Looking forward to more randomly capitalized words from you soon.

KILL SWITCH!!!

[alchemistmuffin]

MORE CLOSELY? More closely than what?
KILL SWITCH KILL SWITCH KILL SWITCH!!! Jeez kid, put THAT speedball down AND RELAX.

If Apple doesn't like it, they're not going TO ALLOW it in the appstore to begin with, since IT'S already getting this MUCH exposure going in. But I hear ya, you like saying KILL SWITCH.

Looking forward to more randomly capitalized words from you soon.

KILL SWITCH!!!

Look, I am also scared of the KILL SWITCH...

So, as a Apple fanboy, the SWITCH should be capitilized so I can reference to the specific kill switch I am talking about....

the Kill Switch in italics represent the switch for ending certain action not pertaining to software. The Kill Switch in bold represent killing certain apps not related to iPhone. KILL SWITCH in bold caps represent Apple killing the apps on iPhone without no notice, followed by at&t terminating your contract without your notice for installing unauthorized app.

Also, note, when I mean read closley, I meant READ THE SDK agreement WORD FOR WORD....

I am a developer, and I had to read the whole document and agreement, then talking to my lawyer before starting to create the apps, so I don't violate the agreement.

[Cleverboy]

Look, I am also scared of the **** ******... So, as a Apple fanboy, the SWITCH should be capitilized so I can reference to the specific kill switch I am talking about... Please stop. PLEASE stop it. Stop talking about the supposed "KS". It's stupid. No... its MINDLESS to talk about it the way its being talked about. :mad:

#1.) The core location related code, and the "lever" mentioned by Steve Jobs are not necessarily related. One is a blacklist of programs (http://daringfireball.net/2008/08/core_location_blacklist) not allowed to continue requesting the use of "core location" services, like GPS... and the other (http://daringfireball.net/linked/2008/08/11/wsj-jobs-app-store) is the knowledge that Apple has a method for disabling iPhone apps already deployed (whether it means deactivated remotely or when the phone is next synced with iTunes).

#2.) Pure logic. In the event of disabling applications remotely, Apple needs to be clear that the application has malicious intentions toward its users. Why? From a legal perspective. Disabling an application on a user's device is an extreme act that Apple will have to defend in the court of public opinion (as well as possibly a court of law). As a point of FACT there are a myriad apps running on "jail broken" iPhones that Apple would never intentionally or implicitly allow. These apps will NEVER be simply "shut off", because any solution would never, ever be perfect, people would find a way around it, and it will generally end up simply enraging Apple's customer base. Lose, Lose, Lose. There is no "win" here. Moreover, Apple generally speaking, doesn't even get into "refunds" for electronic purchases (http://gizmodo.com/5035646/getting-a-refund-from-the-app-store-is-basically-impossible). Imagine the nightmare with be to shut off a 99 cent app on 200,000 phones and coordinate automatic refunds to all those customer accounts. Not something to be regarded lightly.

#3.) Guess what? Removing your app from the App Store is a much more plausible consequence of implementing bad code than any perceived remote deactivation. This has been happening on a regular basis. We have "NetShare" and "BoxOffice" as two examples. One, clearly a violating AT&T policies and the other removed for much more nebulous reasons (http://www.macworld.com/article/135001/2008/08/boxoffice.html).

So, to review:
1.) We don't know much about it.
2.) It is the "option of last resort" of what Apple would do.
3.) Better options are being used to discourage policy-based objections by Apple to applications being sold it its store.

I am a developer, and I had to read the whole document and agreement, then talking to my lawyer before starting to create the apps, so I don't violate the agreement. Having a broken application is a much more terrible curse on an app than anything else. Crashing every time a function fails to work (like PASTING) or simply not working as advertised (just look at the "reviews" section in the App Store for buggy applications). Being removed for App Store and not knowing why and wasting a significant amount of development time to implement something that doesn't actually work... these are reasons that are REAL and PRESENT.

No one has to even begin to discuss any resembling a Sword of Damocles. Hey, actually, that doesn't bug me half as much. I think I'll start referring to the KS as the SoD. Brings a literary dynamic to the whole thing and spells "DoS" backwards (the method of flooding a service with bogus traffic until it can't be accessed, instead the SoD simply "kills" the service at the root). :p

~ CB

[Cleverboy]

Looks like it won't be around for long, Gruber's got a nice piece on it. Apparently it'll be broken come 2.1...

http://daringfireball.net/2008/08/raining_on_the_openclip_parade Yeah, I liked the piece as well. In fact, there was one part of it that really shot home, because... without looking at the OpenClip code, I thought the exact same thing. In a word "disingenuous".
That struck me as curious, as I wasn’t aware of any inter-application “shared space” on the iPhone. White’s own description of how it works and the OpenClip source code itself show that such a description is disingenuous. The “How does it work?” section of their regular (i.e. non-developer) FAQ is more technically accurate: In fact, I found that wording of "shared space" to be SO curious, as to come up with a method of "sharing" space (http://forums.macrumors.com/showpost.php?p=6076542&postcount=75), that, to my knowledge... would clearly work NOW, and continuing working into the future... whereas the current OpenClip implementation will NOT be working. Moreover, my idea would even be compatible with copy & pasting from Safari with the simple use of a special bookmark. --And ALSO, users would be able to see their clipboard usage in their Safari settings under "Databases".

Maybe they need to rearchitect OpenClip to use this (http://forums.macrumors.com/showpost.php?p=6076542&postcount=75), and NOT to rely on a security oversight by Apple. But, for all I know, my discovery is a security oversight as well. :p

~ CB

[mashkina]

I'm thinking it will be a second tap, not a double tap. A finger is not detailed enough to hit the right spot so magnifying glass is still need to find the exact start and stop spots.

So right thumb down for magnifying glass and getting to the start spot. Left thumb down for starting the highlight while you slide right thumb (Selecting). Left thumb up to copy.

For paste, right thumb down where you want to paste. Left thumb double tap to paste.

Interesting point. However, the lens zoom can be used after pasting instead of before copying. For copying you do not want to waste so much time, trying to select exactly the text/things you want to. Better a smart copy that gets more or less what you mean. It is by pasting when you can use the lens-zoom to delete/correct the copy. Just an idea.

[decksnap]

According to Gruber, 2.1 not only stops this from working, but was in development before this came out. Just getting that out before people say Apple 'killed' it.

Apps will no longer be able to read other apps sandboxes, and I don't think they were ever supposed to be able to.

[Cleverboy]

According to Gruber, 2.1 not only stops this from working, but was in development before this came out. Just getting that out before people say Apple 'killed' it. Apps will no longer be able to read other apps sandboxes, and I don't think they were ever supposed to be able to. You honestly think anything will stop people from saying Apple killed it? Ignorance is bliss.

~ CB