Open theo-h opened 12 years ago
Thanks for your feedback, I'll definitively look at your issue and make it more performant, probably by verifying all these once the file is Saved only. I need to investigate where the time is spent. I'll keep you inform
it seemed to me, that the whole structure of the story file is evaluated on every key stroke.
You're right, that was the simplest approach (at least due to my Eclipse knowledged) to ensure syntax coloring is performed well.
I also have dreadful performance issues with your plugin :-/ I would really like the option to have the plugin's slow operations to happen only when saving the file
I'm currently working on improving Intellij's plugin. Once, it is stable enough, i'll take time to fix your pains. Please note, that the main repository has moved to: https://github.com/jbehave/jbehave-eclipse
first: thanks for the great plugin!
Having a project with a lot of steps (~250 real steps and ~150 aliases), there is a noticeable lag on every keystroke within a story file.
Even small stories, like:
result in lag of about 0.3 seconds on every key stroke. Having more complex stories (using more steps), the length of the lags grow up to several seconds.
I've enabled the loggers on "TRACE"-level, and it seemed to me, that the whole structure of the story file is evaluated on every key stroke. It would be nice, to have the opportunity, to perform these lookups/checks/formattings only after a linefeed.
best regards, Theo