Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move DefaultSpellingEngine for text to eclipse.platform.ui #2227

Open
DenisUngemach opened this issue Aug 28, 2024 · 2 comments
Open

Move DefaultSpellingEngine for text to eclipse.platform.ui #2227

DenisUngemach opened this issue Aug 28, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@DenisUngemach
Copy link
Contributor

I verified latest Integration Build of Eclipse SDK doesn't provide the feature:

image

Suggestion

It seems the spelling preferences are available with the text editor, but the default spelling handling of text happens in a jdt plugin: org.eclipse.jdt.ui with the class DefaultSpellingEngine .

This default spell checking for text is also very useful for other extensions, but it creates the dependency to jdt.

I would recommend to move the DefaultSpellingEngine only with the content type "org.eclipse.core.runtime.text" to the plugin org.eclipse.ui.workbench.texteditor next to the extension point org.eclipse.ui.workbench.texteditor.spellingEngine.

Then the text spelling feature can be easily used in the platform.

What do you think, do you agree to this feature or decline?

Then:
I would like to analyze this further and if it is possible, i will provide a pull request with a recommended implementation. Of course this must not break the jdt implementation of the spelling engine.
I will also open an issue in the jdt repo and ask them what they think about it.

Best regards,
Denis Ungemach

@DenisUngemach DenisUngemach added the enhancement New feature or request label Aug 28, 2024
@mickaelistria
Copy link
Contributor

This would indeed be an enhancement. Fortunately, it looks like all that is internal, so there are no strong risk of breaking APIs. However, the tricky part in the migration would be to figure out: 1. what to migrate to platform UI and 2. What are the minimal API to expose so it's usage by JDT and others.

@vogella
Copy link
Contributor

vogella commented Aug 28, 2024

This was suggested multiple times over the last decade but nobody was found to do the actual migration work. CDT would also profit from this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants