Description Dani Megert 2006-03-27 06:19:01 EST

I20060322-0800

In M5 Platform Text added the quickAssistProcessor extension-point without implementing it and with the hopes to get the code in for 3.2 M6. This was too optimistic for several reasons as we learned now:

- the extension point would not be able to fulfill its promises because an
  editor implementer which overrides the default behavior would no longer honor
  the extension point. We should provide APIs in 3.3 allows editor contributors 
  to easily define their own quick assist extension point, similar to the one
  already offered in JDT UI.

- an extension to this extension point can affect any editor we would
  need a preference UI that allows to control this and that's lot of UI
  feature work.

- we would not have a client inside the Eclipse SDK i.e. not eating our own
  dog food. JDT can't easily switch to it because its extension point and the
  code that goes along with it is API.

- the new code would not be well tested and pose a risk.

- other work like performance, bug fixing EclipseCon work took longer than 
  planned.

For all those reasons we have to remove the extension point again. So far no one could have really used it because there was no implementation behind i.e. we won't break any client or remove current functionality. Also note that the quick assist APIs that we introduce for 3.2 remain in place and are already in use e.g. by PDE UI.