You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
@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...
+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?
That's why suggested subsections - like in the validation preference page or the Xtend compiler preferences. Using them, cluttering should not be a problem.
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)
The text was updated successfully, but these errors were encountered: