Re: [e4-dev] Drop Adapters in Resource Viewers

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

The original effort to solve this problem
of navigator-like views is the common navigator framework. The CNF is the
replacement for the Navigator view already, and could possibly replace
some of the other navigator-like views with a little effort. I would suggest
minimally adding your DND support in the CNF, since ideally the Navigator
will cease to exist even in the 3.x stream (see [1]). We can add the CNF
bundles to the e4 repository if needed, it may even give Francis a useful
place to work on more ambitious CNF changes that would be disruptive in
the 3.x stream.

It's possible the declarative UI can
help with this, but I'm not optimistic it can be solved generically. Having
worked on drag and drop in the past, I know every view likes to stream-line
DND behaviour in a way that makes sense in their particular view. The appropriate
behaviour when an IFile is dropped into a view can vary greatly depending
on the kind of view and the particular drop position in the view. Maybe
there is a way to model this but I'll defer to the UI-model folks to answer
in more detail.

John

[1] - http://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg04053.html

Serge Beauchamp <serge@xxxxxxxxxxxxx>
Sent by: e4-dev-bounces@xxxxxxxxxxx

03/05/2009 06:24 AM

Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>

To	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
cc
Subject	[e4-dev] Drop Adapters in Resource Viewers

Hi all,

With the e4 resource improvements effort, changes have been made to the
way dropping resources is handled in the navigator view. 
The user can now choose to automatically create groups and linked 
resources simply by dragging files in the resource viewer (see a 
demonstration of this feature at 
http://www.youtube.com/watch?v=ej-diQ9ClV0).

Unfortunately, since those UI changes required code change in the 
org.eclipse.ui.ide plugin, and every resource navigator (the Package 
Explorer, Project Explorer, the CDT CView, etc...) use their own 
implementation that does not share the org.eclipse.ui.ide 
NavigatorDropAdapter.

Ideally, those views will be refactored into using all a common 
component that is full featured and easily maintainable.  Since only
the 
org.eclipse.ui.ide plugin is part of the e4 resource plugin, I'm not 
sure what's the best way to go about that, or how to coordinate such an
effort.

Also I have been told that maybe the "Modelled UI" may have some
idea on 
the way to do with this general feature.

Any comments would be appreciated, thanks,

Serge Beauchamp
Software Engineer
Freescale Semiconductor
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev