Community
Participate
Working Groups
Since Eclipse 3.6, there is a Display#getSystemTaskBar method in SWT. It returns the single instance of the system taskBar or null when there is no system taskBar available for the platform. We could consider to implement this by always returning null but at the 'cost' of providing empty implementations for Task and TaskItem.
Fixed in CVS HEAD. Display#getSystemTaskBar always returns null. Added empty implementations for TaskBar and TaskItem.
Wouldn't it be good to have tests for all those methods on TaskBar and TaskItem?
As these classes will never been instantiated (without a real TaskBar support), I don't think that we need to test them now. These methods are provided only for single-sourcing compatibility and are copies (with code formating only) from SWT. Do you think, that classes with only *public* empty (without any code) methods fits better in this case?
After discussion with Ralf, we decided to cleanup both classes (TaskBar and TaskItem) from the original SWT code and leave only empty public methods. Same will be done with Tray and TrayItem. Changes are in CVS HEAD.