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

[Feature] Add more languages #26

Open
sskieller opened this issue Dec 12, 2022 · 9 comments
Open

[Feature] Add more languages #26

sskieller opened this issue Dec 12, 2022 · 9 comments

Comments

@sskieller
Copy link

sskieller commented Dec 12, 2022

Hello, is it possible to add the following languages as well:

  • Python

  • Batch

  • SAS

  • STP (Stored Procedure, fx MSSQLSTP)

  • CMD (Command Prompt)

  • PS (PowerShell)

  • SCD (SimCorp Dimension)

  • VB (Visual Basic)

  • DLL

  • Also just a Rich Text Editor:
    image

@huntercfreeman
Copy link
Owner

Added separate [Feature] request for the Rich Text Editor #30

@huntercfreeman
Copy link
Owner

Plan for this feature:

As per #27 adding more languages seems as though it would be a matter of referencing separate NuGet Packages as per one's language needs.

@sskieller
Copy link
Author

I agree, that would be better, but also lazy-loading? Because what if I need to be able to use all the languages, but its up to the user to choose the language and then load the language package?

@huntercfreeman
Copy link
Owner

I like the lazy-loading idea I'm going to look into that

@sskieller
Copy link
Author

Maybe be able to set a default that will be fetched on load and then possible to logically set the default depending on some type. So if the user picks a it starts with x and if the user picks b it starts with y.
And then you can have a switch where new languages can be loaded like above.

@sskieller
Copy link
Author

@huntercfreeman
Copy link
Owner

Yeah, the link you gave appears to be how the lazy loading would be implemented. Thanks for the link.

I am currently working on two new git branches:
v5.3.0
or
v6.0.0

I believe I will be going the route of v6.0.0 as I believe a lot of issues would be solved by changing how the Text Editor is architected a bit. As well a lot of features would be possible by doing this. I'll be changing the API so I'll increment the major version if I go this way.

@sskieller
Copy link
Author

Seems like a good idea.

For now, I could start using this for a proper project with the Rich Text Editor in place, but the languages above are definitely high on the wish list for further use.

@huntercfreeman
Copy link
Owner

huntercfreeman commented Dec 13, 2022

Ah thanks for the use case info. I'll see if I can prioritize a Rich Text Editor being finished for the next update. I suppose a lot of others would like that as well.

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

No branches or pull requests

2 participants