| Re: [platform-ui-dev] Enhanced extensibility for the default text editor in Eclipse |
|
On 07/05/2016 03:52 PM, Angelo zerr
wrote:
The plan here isn't to adopt Liclipse inside Platform UI, but to evaluate whether the proposed patch and extension points can do the work as expected and be used for a generic and extensible editor. We took Liclipse as example because it's sharing the same goal as this generic editor initiative and it already implements many interesting features that match with the current needs. Performance issues can happen, and they are one of the reasons why a raw text editor in Eclipse IDE will remain relevant, as it was already discussed on that thread. However, part of the effort of a generic text editor is to evaluate whether some work inside editors can easily be implemented asynchronously to prevent from freeze and bad user experience. So we'll definitely look at your use-case when we have a kind of minimal viable integration and see whether the lag you noticed with Liclipse is something that can be easily avoided already or if it requires some changes in the Text Editor to better support such long operations. |