Another way to solve the issue: not to contribute selector by the extension point, and hard code it in java, in the appropriate xxxExtensionManager class.
----- Original Message -----
From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Wednesday, February 3, 2010 9:47:00 PM GMT +06:00 Almaty, Novosibirsk
Subject: Re: [Dltk-dev] // XXX: what if multiple extensions define a selector
i realize i've been out of the game for a while, but if memory serves, the selector is what allows for the drop down list to occur and extensions are supposed to provide an implementation of the drop down item.
isn't this something that could just happen in general, where any extension could define an implementation and over write something that already exists in the 'core'? it seems this should be one of those 'design by contract' things, which means just don't do it. :)
On Wed, Feb 3, 2010 at 10:33 AM, Alex Panchenko
<alex@xxxxxxxxx> wrote:
Hi Gabriel,
I remember that discussion, but I am not sure what is the best choice here.
I can suggest logging extra selectors to the error log.
What do you think? Do you have any other ideas?
Regards,
Alex
--
-jae
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
