RE: [mylyn-integrators] Task repository design enforces one client?

[Brandon White <brandonjacob@xxxxxxx>]

Thanks for the information Eugene. I suppose I'll have to look at the
createAdditionalControls() method when I'm working on the UI.

Thanks also for referring me to the WebRepositorySettingsPage, which
eventually led me to the WebRepositoryConnector. One of the issues I was
concerned with was how to get the settings from the task repositories for
use in client connections. 

It appears the WebRepositoryConnector depends on the
org.eclipse.mylyn.tasks.ui plugin so that it can access the TasksUIPlugin,
fetch the task repository manager, and thus get access to the collection of
repositories. The only downside is having core connector code depend on a
UI-oriented plugin. Not that big of a deal.

Thanks,
Brandon

-----Original Message-----
From: mylyn-integrators-bounces@xxxxxxxxxxx
[mailto:mylyn-integrators-bounces@xxxxxxxxxxx] On Behalf Of Eugene Kuleshov
Sent: January 24, 2008 12:33 AM
To: Mylyn Integrators list
Subject: Re: [mylyn-integrators] Task repository design enforces one client?

Brandon,

  Currently you can't add additional pages to the task repository 
wizard. So the only option is to use createAdditionalControls() method. 
See for example WebRepositorySettingsPage in org.eclipse.mylyn.web.tasks

  Basically you can create custom UI and store arbitrary settings 
(string based) in the task repository instance managed by Mylyn. Then 
your repository client code could use these settings to establish 
required connections.

  regards,
  Eugene


Brandon White wrote:
> Thank you for your response Steffen. I have some comments.
>
> I think there's a misunderstanding here. I probably didn't state my
question
> clearly.
>
> I agree with you that the TaskRepository is meant to store configuration
> settings and I wasn't suggesting that it be extended to provide logic for
> connecting to a repository. The TaskRepository stores properties for _one_
> url, _one_ set of authorization tokens, _one_ proxy, etc.
>
> My question is/was: what do these properties represent? Do they refer to
the
> task repository server or an interface/service on that repository? 
>
> I think you answer this question later on when you say I should settle on
> one location (web client url) to uniquely identify the repository. So,
those
> properties represent the "main" interface/service. Is that a correct
> assertion?
>
> Furthermore, you suggest storing other parameters for alternate
> interfaces/services in the same task repository instance. Fair enough.
> However, it means storing more information than just the url for the
> alternate client. The alternate client(s) may have different proxy or
> authentication information.
>
> Based on my quick read of the AbstractRepositorySettingsPage class, it
looks
> like I could use its existing functionality for entering configuration
> information for the "main" interface/service. But I would have to either
> override the createAdditionalControls method to allow users to enter
> additional interfaces/services; or add new pages to the Wizard.
>
> Thanks,
> Brandon
>
>
> _______________________________________________
> mylyn-integrators mailing list
> mylyn-integrators@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>   

_______________________________________________
mylyn-integrators mailing list
mylyn-integrators@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-integrators