Re: [platform-ui-dev] Re: VOTE: Cut, Copy, Paste

[Mike_Wilson@xxxxxxx]

From my point of view, those are perfect examples of why "Cut" is a bad paradigm for file level operations.

McQ.

"Jay Cagle" <jcagle@xxxxxxxxxx> Sent by: platform-ui-dev-admin@xxxxxxxxxxx 03/22/2002 10:59 AM Please respond to platform-ui-dev

To:        platform-ui-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-ui-dev] Re: VOTE: Cut, Copy, Paste

Bummer.  You might want to change the Move menu item to "Move..." to indicate that Move prompts while Copy doesn't.  Mixing the two paradigms is a little confusing. 

What about the case where you cut a file from the Navigator and then paste into a text editor?  (Or in general where the pasted representation doesn't contain all the information of the original.) 

-- Delete the file.  (A Cut is always a Cut.) 
-- Don't delete the file.  (A Cut is a Copy in cases where information is lost.) 
-- Don't allow Paste.  When doing a Cut only use FileTranfer and ResourceTransfer -- representations where information isn't lost.  Although, this doesn't address the case of a resourceful text editor that uses a FileTransfer to paste the file name. 

In Windows Explorer you can Cut a file and Paste it into Wordpad (but not NotePad).  In this case, the file and its contents are placed in the WordPad document, however, the file is not deleted from the file system.  In fact, you can paste multiple times. 

Jay

_____________________________________
Jay Cagle
WebSphere Studio Web Tooling Development
(919) 254-6906, jcagle@xxxxxxxxxx

Randy_Giffen@xxxxxxx Sent by: platform-ui-dev-admin@xxxxxxxxxxx 03/21/2002 04:59 PM Please respond to platform-ui-dev

To:        platform-ui-dev@xxxxxxxxxxx        cc:                Subject:        Re: [platform-ui-dev] Re: VOTE: Cut, Copy, Paste

Cut is not planned for 2.0 
Some issues came up with requiring Clipboard support for notification of a successful Paste and visual indication of the "cut" state.