|Re: Parsing large files [message #759822 is a reply to message #759820]
||Wed, 30 November 2011 08:35
| Sebastian Zarnekow
Registered: July 2009
it's the editor redraw that takes the time. You have to customize the
damager repairer to your specific needs to get along with those.
Validation (and thereby cross linking) is already done async to the user
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 30.11.11 09:26, schrieb Vlad Dumitrescu:
> I am looking at migrating from a custom language support to one based on
> xtext. One of the issues we have today is that files can be huge (I've
> seen one that is ~2MB and 30000 lines) and it's slow. I was hoping that
> it could be faster with xtext, as it uses less naive implementations
> that I do, but from my trials it doesn't seem so.
> My reference is the Java editor, where one can edit huge files without
> delays in the UI. For my xtext-generated editor, I get for example ~4
> seconds where the editor freezes after pressing "enter" at the end of a
> huge file.
> Is there something I can do about that? I suppose that it's the
> validation and cross-linking that take most time - could these be done
> in the background, just like the semantic highlight?
> best regards,
Powered by FUDForum
. Page generated in 0.01959 seconds