Hi all,

(sorry if this is too much off-topic)

I re-read some of the related topics on this list. I have also installed the Argon plugin (very nice). I tried this several times in the past but everytime I went back to the BaseX gui.

But I would like to be able to reduce my use of the BaseX gui and do more directly from Oxygen. Even though the gui is very nice I would like to more development to be done from Oxygen.

I wanted to post here first as you all may have some ideas on how to fix some shortcomings to the current BaseX/XQuery workflow with Oxygen.

When I have a better idea of what is really missing or can't be worked around I will also post some of these things on the Oxygen list.

1) Syntax

Although I understand that XQuery 3.1 wasn't official with the release of 17.1 earlier versions were a bit more relaxed about syntax. Instead in 17 and higher whenever XQuery code uses typical 3.1 syntax (such as literal arrays) syntax coloring displays parts of the code in red. Earlier versions, if I remember correctly, I believe did a better job at this. Is there a way to avoid having large parts of the code in red (I tend to use arrays and other 3.1 syntax quite a lot).

2) Validating

It seems that, even if I choose the BaseX connection for validation, the code still gets analyzed by Saxon 9.6 which doesn't know about the 3.1-isms and barfs with: E [BaseX - Localhost] Invalid XQuery syntax, syntax does not pass static validation. I guess that's Saxon talking here.

That's it really, quite basic. Feels like it's almost, but not quite, there yet.

Any tips? I will post to Oxygen mailing list once I am convinced that I have done everything I can to improve the situation.

--Marc