Hi Rob,
I managed to play around with BaseX on an older machine (Celeron, 1.3 GHz, 224 MB RAM), and I was surprised to see it worked pretty well. Maybe it was due to Windows XP, though, and the fact that it was a fresh installation.
I had a closer look at the files you sent to me, and the most noticeable delays I noticed happened when editing an XQuery file with numerous module imports. The reason for that is that all the imported modules need to be parsed with each key click.
Spontaneously, I got two ideas how this could be improved:
* XQuery parsing could be delayed for some milliseconds. This way, it would only be parsed if a user has (presumably) finished his input.
* An obsolete query parsing thread could be stopped before a new parsing thread is started.
* The least thrilling solution: A new option in the Preferences dialog to disable realtime parsing, and only parse if a file is saved.
I’ll see what can be done.
Cheers, Christian
On Thu, Mar 10, 2016 at 9:45 AM, Rob Stapper r.stapper@lijbrandt.nl wrote:
Hi Christian,
New tools, new challenges.
I’ve rearranged my source-code in packages/libraries conform the eXPath-specs in BaseX now.
But since than the GUI-editor is becoming very slow, even unworkably slow.
What is causing this and can you give me any tips how speed up the GUI-editor?
I’ve got 7 libraries now. The one with the largest interface counts 11 entries in file:expath-pkg.xml, all public entries, the smallest library counts one entry.
TIA,
Rob