This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 35027 - Review explorer D&D system for portability, JDK 1.4 compliance
Summary: Review explorer D&D system for portability, JDK 1.4 compliance
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: UI
Depends on:
Blocks: 70468
  Show dependency tree
 
Reported: 2003-07-21 18:16 UTC by Jesse Glick
Modified: 2008-12-22 23:58 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2003-07-21 18:16:42 UTC
The code to support explorer D&D was written to
support JDK 1.3. JDK 1.4 introduces much
simplified D&D APIs which may behave better. The
current system also is said to have problems on
Mac OS X.

Request a full code review of this system to see
if it can be simplified and brought more into line
with Swing recommendations for D&D implementation,
hopefully reducing (1) code complexity, (2) bugs,
(3) mismatches with platform-specific behaviors.
Comment 1 Jiri Rechtacek 2003-08-01 14:50:19 UTC
Some ideas from Chris Morley
http://openide.netbeans.org/servlets/ReadMsg?msgId=548997&listName=dev
about default drag actions. There is also UI spec about DnD:
http://ui.netbeans.org/docs/dnd/dnddo_uispec.html.
Comment 2 Jiri Rechtacek 2004-04-23 10:45:36 UTC
Assigned to new owner.
Comment 3 Stanislav Aubrecht 2006-02-10 11:20:37 UTC
i did some investigation of the new drag and drop support in jdk 1.4 and it's
almost unusable. the new TransferHandler class does simplify d'n'd
implementation but for simple components only. explorer views in netbeans need
to know the cursor location when something is being dragged over them to find
the appropriate drop Node. the TransferHandler class does not provide such
information therefore it can allow/reject drop operation for the whole component
only.
so the explorer views still need to register droptarget listeners and dropsource
listener to allow/reject the drop depending on the current node under the cursor.
Comment 4 Torbjorn Norbye 2006-02-10 16:46:27 UTC
A lot of this is getting fixed in Mustang...

http://weblogs.java.net/blog/shan_man/archive/2006/01/

Comment 5 Torbjorn Norbye 2006-02-10 16:46:28 UTC
A lot of this is getting fixed in Mustang...

http://weblogs.java.net/blog/shan_man/archive/2006/01/

Comment 6 Stanislav Aubrecht 2006-05-23 15:07:46 UTC
closig as per my previous comment.

please reopen if necessary.