Browse Prior Art Database

Defining Usability Rules for Text Drag-Drop Operations

IP.com Disclosure Number: IPCOM000114773D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 93K

Publishing Venue

IBM

Related People

Morgan, SA: AUTHOR [+2]

Abstract

Disclosed is a list of usability guidelines specifically oriented toward enhancing the usability of text drag-drop operations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Defining Usability Rules for Text Drag-Drop Operations

      Disclosed is a list of usability guidelines specifically
oriented toward enhancing the usability of text drag-drop operations.

      The IBM* Operating System/2* (OS/2) program provides API
interfaces that enable an application to implement drag-drop
operations within and between applications.  This has been primarily
implemented for the dragging of icons within containers.  An IBM
internal user interface development tool, however, has also
implemented
the dragging of text within and between entry fields and lists.

      The Common User Access* (CUA) standards as applied to
Presentation Manager* (PM) applications address drag-drop operations
of icons within containers, but pay little attention to drag-drop
operations involving object types such as text.  Drag-drop operations
of text, however, have their own unique requirements.

      Dragging and dropping text between entry fields and lists
involves situations that are different from those found when dragging
icons within containers.  These differences are inherent in the
unique functionality that entry fields and lists have when compared
to containers.  A listing of usability guidelines that should be
adopted by all applications that implement drag-drop support for text
between these control types is as follows:
  o  When text is dropped on a list, the insertion point within the
      list depends on the nature of the list.  If the list is a
sorted
      list (for example, ascending or descending based on text), the
      new list item should be inserted in the proper sort order
      regardless of where the mouse was within the list when the drop
      was made.  If the list is an unsorted list, then the new list
      item should be inserted following the list item the mouse was
      over when the drop was made.  If the mouse is beyond the end of
      the list, the new list item should be inserted at the end of
the
      unsorted list.
  o  Since each list item within a list must have a unique ID, the
IDs
      assigned by the application for the original list items need to
      be limited to a maximum value.  Those IDs above this value are
      reserved for list items inserted by drag-drop techniques.  When
a
      drop occurs on a list, the new list item is assigned the next
      available ID that is beyond the range reserved for the
      application.  The list needs to keep track of the next
available
      ID for a dropped list item.
  o  Multicolumn lists have text from each column specified between
      tabular characters.  Whe...