Community
Participate
Working Groups
It would help to remove the explicit dependence on TabbedPropertySheetWidgetFactory. That means: (a) typing params as something more general (FormToolkit or maybe making an ITabbedPropertySheetWidgetFactory??), and (b) maybe factoring out widget-related initialization from TabbedPropertySheetPage.createControl() into a separate method so the factory can be replaced with a different one (a subclass? whatever) and the initialization of that composite etc. can be overridden
Do these belong to you? Forward as necessary. Thanks,
Can you explain in more detail what you want to accomplish? What exact UI / Composite creation are you proposing to use? Likely you just want to override some of the details in TabbedPropertySheetWidgetFactory.
Right, I want to be able to provide my own widget factory to the details framework. So if I want to change its look and feel I just need to provide my custom factory. Basically I want a getter and a setter and to be able to change the factory early in the life cycle.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
