Re: [Dltk-dev] // XXX: what if multiple extensions define a selector

[Alex Panchenko <alex@xxxxxxxxx>]

Hi Gabriel,

"selector" is an implementation to read what is selected by the user.
There is an abstract class to create selector implementations reading workspace/project preference: org.eclipse.dltk.core.DLTKIdContributionSelector.

For example:
public class RubyDebuggingEngineSelector extends DLTKIdContributionSelector {
	protected String getSavedContributionId(PreferencesLookupDelegate delegate) {
		return delegate.getString(RubyDebugPlugin.PLUGIN_ID,
				RubyDebugConstants.DEBUGGING_ENGINE_ID_KEY);
	}
}

Regards,
Alex

----- Original Message -----
From: "Gabriel Petrovay" <gabipetrovay@xxxxxxxxx>
To: "dltk-dev" <dltk-dev@xxxxxxxxxxx>
Sent: Thursday, September 17, 2009 9:01:58 PM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] // XXX: what if multiple extensions define a selector

Hi all,

There is still this unsolved problem in the
DLTKContributionExtensionManager.addSelector(...). What are the plans
for this since, this architecture is now very limiting.

Moreover, projects have their debugging engine set (either through the
default workspace debugging engine or through the project specific
properties). Why using a selector when DLTK provides the means to be
selected by the user?

Thanks!

Gabriel


-- 
MSc Gabriel Petrovay
Mobile: +41(0)787978034
www.28msec.com
www.xqdt.org
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev