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

Plans for Version 3.0 #357

Open
4 tasks
twibiral opened this issue May 30, 2024 · 0 comments
Open
4 tasks

Plans for Version 3.0 #357

twibiral opened this issue May 30, 2024 · 0 comments
Labels
important Only for very important issues which are deciding for the future of the plugin.

Comments

@twibiral
Copy link
Owner

twibiral commented May 30, 2024

Hi everyone,

Development on the plugin was slow over the last few months. I try to keep up with all the bugs and feature requests, but so many people are adding new features and opening new issues (which is fantastic!) that it is hard to keep track. I am incredibly impressed by the love and support this plugin receives. I will continue merging pull requests and developing new features. Still, at the moment, I can only dedicate limited time to this plugin.

Anyway, I have some plans for version 3.0 that should make it much easier to integrate new languages:

  • Most languages share the same simple settings and configuration parameters. A simple configuration JSON file per language should suffice to save all information necessary to run the language
  • The settings page should contain the option/possibility to add new custom languages easily
  • Share function for custom languages: If you added a new language that works for your vault, you should be able to easily share the configuration for that language on GitHub or per email so it canbe included in the next release.
  • For better integration of compiled languages, there should be two configuration types, one for interpreted languages and one for compiled languages

I would love to hear all your ideas for version 2.0! Otherwise, if you came here for another issue, bug, or feature request, you can open a separate issue.

@twibiral twibiral added the important Only for very important issues which are deciding for the future of the plugin. label May 30, 2024
@twibiral twibiral pinned this issue May 30, 2024
@twibiral twibiral changed the title Plans for Version 2.0 Plans for Version 3.0 Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important Only for very important issues which are deciding for the future of the plugin.
Projects
None yet
Development

No branches or pull requests

1 participant