Community
Participate
Working Groups
I've started working with the presentations API. The needs of my presentation are greater than what is currently specified as part of the default presentation. That is, I need more than the image, title, tooltip, etc. In my presentation, each editor/view must have a header image, a content description and more. In the current presentations API there is no way to manage any extra properties. If the IPresentablePart interface could expose the getAdapter() method of the underlying workbench part, then I could use that for any additional properties I need.
Created attachment 18468 [details] pic of presentation This picture shows my altered presentation and points out where/why I need an extra property. I need a 32x32 image that represents the object being edited. In the picture I am simply stretching the 16x16 default image to 32x32. I'm really hoping this change could be made for 3.1.
Implementing this enhancement as suggested would require eager activation of the part. IPresentablePart is created long before the actual IWorkbenchPart. If any method on IWorkbenchPart were exposed directly by the IPresentablePart, it would be necessary to force creation of the IWorkbenchPart... and that's bad. It may be possible to give IPresentablePart a more open-ended API, but it would be necessary to do so in a manner that did not force activation of the underlying part.
Added 89834
