What the iPhone OS 3.0 update might really mean
#3
Posted 13 March 2009 - 12:58 PM
Copy and paste....hmmm...
I do not understand why it seems so hard to implement.
If some text is hi-lighted, a button appears on the left corner with copy on it. Just press it.
If you are in a text/input field, the paste button appears on the bottom right if there is some data in the clipboard.
Please treat this post as copyrighted...you never know.
I do not understand why it seems so hard to implement.
If some text is hi-lighted, a button appears on the left corner with copy on it. Just press it.
If you are in a text/input field, the paste button appears on the bottom right if there is some data in the clipboard.
Please treat this post as copyrighted...you never know.
#4
Posted 13 March 2009 - 01:06 PM
eteen said:
Copy and paste....hmmm...
I do not understand why it seems so hard to implement.
If some text is hi-lighted, a button appears on the left corner with copy on it. Just press it.
If you are in a text/input field, the paste button appears on the bottom right if there is some data in the clipboard.
I do not understand why it seems so hard to implement.
If some text is hi-lighted, a button appears on the left corner with copy on it. Just press it.
If you are in a text/input field, the paste button appears on the bottom right if there is some data in the clipboard.
I suspect the problem has a lot more to do with each application being in it's own sandbox, and not playing well with others. For copy paste to work in the OS X sense it needs to be universal. The UI is only one small part of the puzzle.
#6
Posted 13 March 2009 - 01:16 PM
What I hope to see for iPhone 3.0. I hope to see Landscape text messaging, and E-Mail. Spoken directions in maps, and the feature I want the most is Background processes so you can get notifications.I really want to see some really cool things for the 3.0 software and like i said iPhone 1st generation compatible.
#7
Posted 13 March 2009 - 01:18 PM
Since we're extrapolating here, have you ever stopped to think that Apple has not implemented cut & paste in the iPhone exactly because it has been working on the iNet or iBook or ibBooken or whatever name they do decide on, where it will be a small part of the OS amongst a multiplicity of of new features.
#8
Posted 13 March 2009 - 01:24 PM
Actually I know how to make copy and paste work without breaking any rules laid down by Apple. SQLLite.
Within the iPhone OS is a database called SQLLite. All that would need to be done is to access this database from any app and paste the resulting entry. The next time data is copied it overwrites the existing entry.
Something tells me that that is how Apple would implement it but on having said that I have yet to have found a need for copy and paste. I guess once apps like Documents To Go come along this will change but so far not a single reason have I had for copy and paste.
Within the iPhone OS is a database called SQLLite. All that would need to be done is to access this database from any app and paste the resulting entry. The next time data is copied it overwrites the existing entry.
Something tells me that that is how Apple would implement it but on having said that I have yet to have found a need for copy and paste. I guess once apps like Documents To Go come along this will change but so far not a single reason have I had for copy and paste.
#11
Posted 13 March 2009 - 01:49 PM
I don't think the Copy/Cut/Paste is the hard part.
It's the interface to actually select the text in the first place.
Touch and drag already have well defined behaviours in most cases, so how does one select a range of text?
If you think about it it's a very tricky thing to implement in any kind of consistent and elegant way, two requirements I'm sure Apple will impose.
It's the interface to actually select the text in the first place.
Touch and drag already have well defined behaviours in most cases, so how does one select a range of text?
If you think about it it's a very tricky thing to implement in any kind of consistent and elegant way, two requirements I'm sure Apple will impose.
#12
Posted 13 March 2009 - 01:57 PM
@LowededWookie
Your SQLLite solution to be a system-wide repository for copy-paste will not work. In order for an app to write to an SQL database, the app must first copy the database from within the app (or create a database) and store in the app's Documents directory. The app's Documents directory is within the app's "Sandbox' and is not accessible by other apps.
Dick
Your SQLLite solution to be a system-wide repository for copy-paste will not work. In order for an app to write to an SQL database, the app must first copy the database from within the app (or create a database) and store in the app's Documents directory. The app's Documents directory is within the app's "Sandbox' and is not accessible by other apps.
Dick
#13
Posted 13 March 2009 - 02:00 PM
@eteen
the problem is not the mechanics of cutting/pasting. the problem is a universal, system wide implementation. it has to work the same way in every application that was ever written and ever will be written (where you might want to cut paste). you also need to maintan backwards compatability. how'd you like to wake up one morning and find that the latest OS broke every single one of your apps?
the problem is not the mechanics of cutting/pasting. the problem is a universal, system wide implementation. it has to work the same way in every application that was ever written and ever will be written (where you might want to cut paste). you also need to maintan backwards compatability. how'd you like to wake up one morning and find that the latest OS broke every single one of your apps?



Sign In
Register
Help

MultiQuote