Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Clarifying some problems in salvo UI

About HookedNewsGroupProvider: The extension point is now geared towards NNTP obviously. I think we should move this stuff to the NNTP specific part? what doe you think?



On Tue, Jul 31, 2012 at 11:15 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:

About the extension point:

This is a really cool extension point [1]. Projects can use this extension point to point at their newsgroups. When the user selects "ask a question" and the current perspective is for example the ECF perspective then the newsgroup will be suggested as a place to drop the question



On Tue, Jul 31, 2012 at 10:52 AM, tishan pubudu kanishka dahanayakage <dtishanpubudu@xxxxxxxxx> wrote:
Hi wim,
In the current implementation SelectNewsGroupWizardPage uses a HookedNewsGroupProvider go get a list of NewsGroup(MessageSource) providers. Inside HookedNewsGroupProvide it uses a extension point  defined by org.eclipse.ecf.salvo.ui.newsgroupProvider.

IConfigurationElement[] config = Platform.getExtensionRegistry()

    for (final IConfigurationElement newsgroup : config) {

            IConfigurationElement enablement = newsgroup

I also checked the Still could not get clear idea of what is happening. Can you please clarify on this more.

Also inside HookedNewsGroupProvider ServerStoreFacade instance is used every where. As far as I understand we have to use protocol specific serverStoreFacade inside HookedNewsGroupProvider. But In my solution each protocol specific ServerStoreFacade resides inside protocol specific container. So should we pass that instance to HookedNewsGroupProvider or create new serverStoreFacade differentiating by protocol using the lame logic to create different containers and use them.

Back to the top