Community
Participate
Working Groups
I realize that Mylyn isn't out there to make a really great generic tooltip class, but by making a couple of methods protected access I'm able to re-use a lot of the code, which saved me a bunch of time.
Created attachment 81281 [details] protected visibility patch
Created attachment 81282 [details] mylyn/context/zip
Nathan, could you describe your use-case for extending the tooltip? We can make these methods protected but please note that TaskListTooltip is an internal class that may (and is likely to) change in the future.
I've got a tree viewer like the tasklist with one level of categorization. I had copied TaskListTooltip initially, but then noticed that I wasn't making any changes to most of the methods I was copying. I realize it's internal.
Steffen: this patch looks fine to me, because it's internals, so the responsibility will be entirely on the extender in terms of maintaining their code.
Agreed. I can't commit to the task framework, over to you.
Just to clarify: the reason why I asked for a use case is that we have another request for making the tool tip more extensible (bug 197345). Apparently this use case is entirely different and is best addressed by making the methods protected.
Nathan, I have made the changes suggested in your patch. I only made a slight modification to the method name for creating the composite: it is called createToolTipContentAreaComposite() instead of createSurface(). Please verify that I didn't miss anything.
Created attachment 82278 [details] mylyn/context/zip
Verified. Thanks.
