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

Compiler preference page with project specific settings #127

Open
nittka opened this issue Sep 13, 2016 · 4 comments
Open

Compiler preference page with project specific settings #127

nittka opened this issue Sep 13, 2016 · 4 comments

Comments

@nittka
Copy link
Collaborator

nittka commented Sep 13, 2016

Xtext's default compiler preference page supports project specific settings. The use case I have in mind is "stable" project you use as snippet repository and one you actively work on. For the latter you may want LilyPond compilation on save, for the former no compilation at all. (However, this is not an urgent issue, as the Recompile functionality achieves almost the same)

@nittka
Copy link
Collaborator Author

nittka commented Sep 16, 2016

@thSoft: It may be easier to include the syntax updater options as a subsection of the compiler preferences rather than keeping a separate preference page. That way, implementing project specific settings works for both without any additional effort. Two more check boxes do not make any significant difference...

@thSoft
Copy link
Owner

thSoft commented Sep 18, 2016

+1: a frequent use case is that you edit two projects simultaneously: a large project where you prefer manual compilation and a small one where automatic compilation is preferred.
Merging the two preference pages clearly simplifies things for the developers, however, I'm afraid it will get too cluttered for the users. If there are other users out there: what do you think?

@nittka
Copy link
Collaborator Author

nittka commented Sep 18, 2016

That's why suggested subsections - like in the validation preference page or the Xtend compiler preferences. Using them, cluttering should not be a problem.

@thSoft
Copy link
Owner

thSoft commented Sep 18, 2016

Yes, subsections would be fine. :)

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

No branches or pull requests

2 participants