Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-5102113

More concise relevant documentation on clipboard support implemented by swing.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 6u15
    • 5.0
    • docs
    • a
    • x86
    • windows_xp
    • Not verified

      Name: rmT116609 Date: 09/14/2004


      A DESCRIPTION OF THE REQUEST :
      There is a lot of documentation on the datatransfer subsystem from the drag & drop perspective -- see: http://java.sun.com/j2se/1.5.0/docs/guide/dragndrop/spec/dnd1.html There is other documentation on DnD including a referenced tutorial trail. That trail and this document: http://java.sun.com/j2se/1.5.0/docs/guide/swing/1.4/dnd.html#ClipboardTransferSupport do include information on the clipboard (cut copy and paste); however, this information is small compared to the drag and drop documentation, and seems to lack a needed piece.

      The subject of this request is for a more concise overview documenting specifically how swing classes implement thier default support for cut copy and paste. An overview of how handlers are hooked up and how messages flow is not really provided in the existing documentation, leaving gaps in the methods outlined in the tutorial.

      Specifically, the logical link between the following instantiation: new JMenuItem(new DefaultEditorKit.CopyAction()); and the resulting connections made within the swing framework are ill-understood. In other words, it is not really possible to see what makes the mentioned code "work"; and therefore how to properly utilize the default clipboard support implemented by swing components and how to expand that.

      I believe it is a rather simple matter of some illustration of the structure implemented for the cut copy and paste support -- a graphic -- that would just make this comprehensible. But right now it is hard to grasp -- the fact that the DnD documentation is so large seems to excacerbate the problem since you seem to just run off on a series of links looking for this structural overview and wind up lost.

      Anyhow, hopefully this is something you can provide because the core library is quite a functional framework -- there's no need to run off developing such frameworks on your own (as might happen if you aren't aware of these types of things)!


      (Incident Review ID: 310700)
      ======================================================================

            sharonz Sharon Zakhour (Inactive)
            rmandalasunw Ranjith Mandala (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: