Data transfer refers to how a user manipulates data, including:
This section describes these data transfer interactions. "Using Transfer Techniques" describes the transfer techniques.
A user moves elements to change their location. For example, the user can move a file to a new directory, move a graphic to a different position in a piece of artwork, or move text to a different section in a letter.
The user moves an object by pressing the SELECT button, dragging the object under the pointer, and releasing the SELECT button as shown in Figure 34.
Figure 34. Moving an Element.
A user copies an element in order to work with a duplicate while keeping the original element intact. For example, the user might copy a file into a different directory (or folder) as a backup of the original, copy a graphic from one piece of art into another as a logo, or copy text from one letter into another letter.
Figure 35 illustrates copying an object from one folder to another folder.
Figure 35. Copying an Element.
A user can create new elements from existing elements. This is different from copying elements in that new information is generated at the time of creation. For example, a user can create a new memo from an existing memo and use new, system-generated information, such as the time and date, or add a name and address to the heading of the memo. A user can create an object by using the original object as a template or by requesting a new object from an application.
Figure 36 illustrates creating a new folder element.
Figure 36. Creating a New Element.
Deleting elements removes unwanted elements. For example, a user can drag a document to a trash can icon to delete it or press the Delete key to delete a character in the text of the document.
Figure 37 illustrates deleting an element.
Figure 37. Deleting an Element.
A user can share an element to make it accessible from multiple locations. For example, the user can share a spreadsheet in a composite document. When the user simply copies the spreadsheet, any changes to the original are not reflected in the copy. When the user specifies the spreadsheet as a shared element, any changes in the original are reflected in the shared version.
Linked elements have established relationships between them. The exact functions of the links can vary. For example, your application may let the user create a link in the target element to a selected source object or to a region of selected data in the source. Within the target, you can represent the link as an icon. The user can then use the link to view the current contents of the source object or the selected region. Alternately, the application can immediately display the link in the target element as a shared view of the object contents or the selected region.
You should associate selected data in the source object with related data (which is often of a different type) in the target data. Changes to the source data are reflected in the target data (and possibly vice versa). For example, when the user links a graph object to a spreadsheet object, any changes made to the graph will cause changes to the spreadsheet data.
Create a hypertext link in the target to information selected in the source. This link will allow the user to navigate from one to the other. For example, a user might create a link within a letter to a graph that is in a different file. Any changes made to the graph within the letter are also made to the graph at its source.