The behaviour and the API of the Eclipse UI is highly constrained. In order to relax these constraints, we have introduced the notion of Tweaklets which provides external plug-ins access to internals of the UI in a controlled way. However, we do not consider this API, and will very likely change it as we learn more.
We have introduced a non-API extension point org.eclipse.ui.internalTweaklets.
Each tweakable behaviour is represented by an abstract class, for which tweaklet plug-ins
can provide a concrete subclass. This mechanism is extremely low-level, and only allows one
such concrete subclass per tweakable behaviour.
We are interested in changing the way editor tabs work, but have been unable to reach a consensus in time for the 3.3 release. To make our experiments in this area (see Bug 168379) available to end-users, we have introduced this tweaklet.
To download the tweaklet plug-in, go to the Platform Incubator download page.
