…thanks; we’ve added some usability tweaks in the editor.
On Mon, Mar 4, 2024 at 11:15 AM Eliot Kimber <eliot.kim...@servicenow.com> wrote: > Now that I’m using an expected extension, a bit more feedback on the > Editor UI. > > > > Having saved a file and then not modified what’s in the editor, opening a > new file should not prompt for confirmation as the editor isn’t “dirty” and > there can be no data loss (the contents of the editor were just saved). > > > > In my case I’m switching between two little test scripts: one to store > docs and one to operate on them, so having to respond to an unnecessary > confirmation every time I switch is annoying. > > > > Cheers, > > > > E. > > _____________________________________________ > > *Eliot Kimber* > > Sr Staff Content Engineer > > O: 512 554 9368 > > M: 512 554 9368 > > servicenow.com <https://www.servicenow.com> > > LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter > <https://twitter.com/servicenow> | YouTube > <https://www.youtube.com/user/servicenowinc> | Facebook > <https://www.facebook.com/servicenow> > > > > *From: *Christian Grün <christian.gr...@gmail.com> > *Date: *Friday, March 1, 2024 at 2:58 PM > *To: *Eliot Kimber <eliot.kim...@servicenow.com> > *Cc: *BaseX <basex-talk@mailman.uni-konstanz.de> > *Subject: *Re: [basex-talk] DBA Editor behavior in v11 not as expected > *[External Email]* > > > ------------------------------ > > Good to know, it'll be easy to fix that [1]; we should do so anyway [2]. > > > > [1] > https://github.com/BaseXdb/basex/blob/main/basex-api/src/main/webapp/dba/static/editor.js#L56 > > [2] https://help.basex.org/main/XQuery_Extensions#suffixes > > > > Eliot Kimber <eliot.kim...@servicenow.com> schrieb am Fr., 1. März 2024, > 21:41: > > I use “.xqy” for full XQuery scripts and “.xqm” for XQuery modules. > > > > Cheers, > > > > E. > > > > _____________________________________________ > > *Eliot Kimber* > > Sr Staff Content Engineer > > O: 512 554 9368 > > M: 512 554 9368 > > servicenow.com <https://www.servicenow.com> > > LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter > <https://twitter.com/servicenow> | YouTube > <https://www.youtube.com/user/servicenowinc> | Facebook > <https://www.facebook.com/servicenow> > > > > *From: *Christian Grün <christian.gr...@gmail.com> > *Date: *Friday, March 1, 2024 at 10:57 AM > *To: *Eliot Kimber <eliot.kim...@servicenow.com> > *Cc: *BaseX <basex-talk@mailman.uni-konstanz.de> > *Subject: *Re: [basex-talk] DBA Editor behavior in v11 not as expected > *[External Email]* > > > ------------------------------ > > Hi Eliot, > > > > We have aligned the behavior of the DBA editor to the BaseX GUI. Saved > files are only executable if they are detected as XQuery file. > > > > But maybe we need to support some more file suffixes (.xq is the default > extension). How do you name your files? > > > > Best, > > Christian > > > > > > Eliot Kimber <eliot.kim...@servicenow.com> schrieb am Fr., 1. März 2024, > 17:52: > > Using the 27-02-2024 build of v11, if I create a query in the Editor panel > and then save it, the Run button is disabled, which is unexpected. > > > > If I then open the file, the Run button remains disabled. > > > > If I cut the contents of the editing panel, select “close” to clear the > panel, then paste back into the panel, the Run button is enabled. > > > > I think this behavior is incorrect—as long as there is some content in the > editor the Run button should be enabled. > > > > Cheers, > > > > E. > > > > _____________________________________________ > > *Eliot Kimber* > > Sr Staff Content Engineer > > O: 512 554 9368 > > M: 512 554 9368 > > servicenow.com <https://www.servicenow.com> > > LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter > <https://twitter.com/servicenow> | YouTube > <https://www.youtube.com/user/servicenowinc> | Facebook > <https://www.facebook.com/servicenow> > >
