Community
Participate
Working Groups
When trying to make a connector to the Builds view, it is convenient to see most of the attributes in the properties view. Just as developing a Tasks connector is made easier by displaying info from the items in the Task List and Task Repositories view. I have created a contribution that consist of: - a "Show in Properties View" Action that allows the selected item in Builds view to be shown in Properties View - an adapter factory for all Builds Property Source - an IPropetySource implementation for BuildElement, BuildPlan and BuildServer - changes to plugin.xml - refactoring out of some code in AbstractMylynPropertySource Please assign to me to complete.
Created attachment 191989 [details] Hudson Builds showing properties Showing peperties in prpoerties views can be useful during developing and debugging Mylyn Builds connectors
Created attachment 191990 [details] Patch to add these Builds IPropertySource implementations to sandbox.dev BuildElement BuildPlan BuildServer Factory AbstractMylynPropertySource + manifest/plugin.xml changes
Created attachment 191991 [details] mylyn/context/zip
The builds model is based on EMF. As far as I know EMF comes with integration for the properties view and it's probably just a matter of generating the corresponding classes? I would prefer that over maintaining a hand crafted solution.
I understand your point. I think EMF only generates PropertySources for Editors so maybe wit will not work. Time to read up on modelling with EMF then!
I looked it up in the EMF book and property source generators work only in combination with Editors, not with other views. Maybe we want to show more than the modeled object, for example also linked information. I'm willing to take on maintenance of these, a well as the Task and Repository property sources, after all I created them. Please accept patch.
(In reply to comment #6) > I looked it up in the EMF book and property source generators work only in > combination with Editors, not with other views. If I look at the generated code ExtendedPropertySheetPage only seems to require an EditingDomain which should not depend on an actual editor implementation. I don't how difficult it would be to implement this for the Builds model but I would assume that you can create the necessary glue if you generate code the org.eclipse.mylyn.builds.edit plug-in. If there is use for it we could maintain that in the Builds project.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
