Sure, CNF itself does not need much, but there is a separate bundle
that provides the support for resources, which of course depends on
more.
What's the e4 story for keeping the source in sync?
There continues to be quite a bit of bug fixing work on CNF, do we just
periodically port that to e4 (hopefully by just replacing the source
from the 3.x line), or is there something different.
Francis
Oberhuber, Martin wrote:
Hi John, Francis,
We just discussed this in the e4
resources call, and agreed that we'd like to have the CNF bundles in
the e4 / resources repository for working on them, especially in order
to make the CDT interoperable with the e4 changes.
Unfortunately I don't know
excactly what bundles the CNF needs... could you move forward
identifying those bundles and cloning them over into e4?
Thanks a lot!
Cheers,
--
Martin Oberhuber,
Senior Member of Technical Staff, Wind
River
Target
Management Project Lead, DSDP PMC Member
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
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
--
You have brains in your head.
You have feet in your shoes.
- Dr Seuss, Oh the Places You'll Go
Francis Upton IV
francis@xxxxxxxxxxxxxxxx
Tel 510 835 3123
Fax 510 779 5226
Cell 510 432 1589
Skype francisupton
|
