[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform] Replacing the Project Explorer view's label provider (Common Navigator)?
|
I'd like to add custom support for *.abc files to the standard Project
Explorer view (that's based on the Common Navigator framework). This
includes custom icons based on file content, but also additional actions and
drop adapters etc.
The problem is that the *.abc files, since they are files, are already
provided by org.eclipse.ui.navigator.resources' navigatorContent extension
(org.eclipse.ui.navigator.resourceContent). I was hoping that if my own
navigatorContent extension was set to a higher priority, the *.abc files
would be provided by my navigatorContent instead, and therefore its label
provider etc. would be used. However, instead I see
org.eclipse.ui.navigator.resourceContent's label provider being invoked,
followed a couple of seconds later by my navigatorContent's.
I suspect I may be going about this all wrong, as I'm not very familiar with
the Common Navigator framework. Basically, is there a way of restricting the
output from an existing navigatorContent's contentProvider, or maybe some
completely different way of getting this to work (ideally by "extending"
rather than replacing the Project Explorer view)?
Thanks, John