|Re: How to disable Parser-Markers in Project Explorer [message #1810356 is a reply to message #1810352]
||Thu, 08 August 2019 18:13
| Konrad Jünemann
Registered: December 2018
I guess the case is special. We use two separate DSLs in our project, a business DSL A and a technical DSL B. A files compile to B files, which are then compiled to all sorts of SQL scripts and so on. This approach is kinda similar to XTend -> Java -> Bytecode.
The actual build process is standalone, though. So during the typical business day, a user *rarely* requires the later files (of type B or SQLs), although occasions arise where you would like to look into those.
However, our infrastructure is "a little" weak in the context I am working in. In order to cope with this, I have to keep the number of generated files to an absolute minimum as a simple eclipse-refresh (unrelated to XTtext) takes multiple seconds to complete (CPU power is fine). So, I build a feature to turn off generation of B files (and SQL files), as typically you don't need those. I used the IShouldGenerate approach, as recommended by you in another thread.
However, as some (but few) B files are created manually *and* relate to generated B files, there will always be errors due to unresolved B-references. I don't want users to bother with those if they are business level users, who will at most edit A-files.
My ideal solution would be to generate *all* B files or to not allow not-generated B files to refer to generated B files, but we are not quite there.
OK, wall of text. I am eager to hear if you have any other recommendations - otherwise thank you a lot for your hint!
Powered by FUDForum
. Page generated in 0.04300 seconds