Re: [basex-talk] GUI feature request: paste into search boxes

2024-01-28 Thread James Ball
Tim,

I'm on an M1 MacBook Air and Cmd-V works for me in the GUI exactly as normal on 
macOS. Interestingly Ctl-V doesn't.

I build BaseX as an app[1] but I just tried double clicking the .jar file 
directly and Cmd-V still worked.

I wonder if the JDK has an impact? I run the Amazon Corretto version.

[1] https://docs.basex.org/wiki/MacOS

> Message: 3
> Date: Wed, 17 Jan 2024 17:58:46 +
> From: "Thompson, Timothy"  <mailto:timothy.thomp...@yale.edu>>
> To: Andy Bunce mailto:bunce.a...@gmail.com>>
> Cc: BaseX  <mailto:basex-talk@mailman.uni-konstanz.de>>
> Subject: Re: [basex-talk] GUI feature request: paste into search boxes
> Message-ID:
>   
>   
> <mailto:co6pr08mb77566b17b81325eb71851f87f9...@co6pr08mb7756.namprd08.prod.outlook.com>>
>   
> Content-Type: text/plain; charset="windows-1252"
> 
> Thanks, Andy, good point. I?m on macOS (M2 chip), and I?ve run into other 
> keyboard issues. Cmd-V is the usual paste combination, which works in the 
> editor pane, but I?ve just realized that Ctrl-V works to paste in the search 
> boxes :)
> 
> Apologies for the noise!
> Tim
> 
> 
> --
> Tim A. Thompson (he, him)
> Librarian for Applied Metadata Research
> Yale University Library
> www.linkedin.com/in/timathompson 
> <http://www.linkedin.com/in/timathompson><http://www.linkedin.com/in/timathompson>


Re: [basex-talk] GUI feature request: paste into search boxes

2024-01-17 Thread Thompson, Timothy
Thanks, Andy, good point. I’m on macOS (M2 chip), and I’ve run into other 
keyboard issues. Cmd-V is the usual paste combination, which works in the 
editor pane, but I’ve just realized that Ctrl-V works to paste in the search 
boxes :)

Apologies for the noise!
Tim


--
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
www.linkedin.com/in/timathompson<http://www.linkedin.com/in/timathompson>


From: Andy Bunce 
Date: Wednesday, January 17, 2024 at 12:54 PM
To: Thompson, Timothy 
Cc: BaseX 
Subject: Re: [basex-talk] GUI feature request: paste into search boxes
Hi Tim,

You don't say what OS or version but on Windows it is true the search boxes 
have no right click context menu, but they do support Ctl-V.

/Andy



On Wed, 17 Jan 2024 at 17:03, Thompson, Timothy 
mailto:timothy.thomp...@yale.edu>> wrote:
Hello,

In the BaseX GUI, it’s not possible (as far as I can tell) to paste a copied 
value into search boxes. Not being able to do so can be inconvenient, for 
example, when searching for a string like a UUID in result output, etc.

Is lack of support for pasting intentional, or am I missing something?

Thanks in advance,
Tim


--
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
www.linkedin.com/in/timathompson<http://www.linkedin.com/in/timathompson>



Re: [basex-talk] GUI feature request: paste into search boxes

2024-01-17 Thread Andy Bunce
Hi Tim,

You don't say what OS or version but on Windows it is true the search boxes
have no right click context menu, but they do support Ctl-V.

/Andy



On Wed, 17 Jan 2024 at 17:03, Thompson, Timothy 
wrote:

> Hello,
>
>
>
> In the BaseX GUI, it’s not possible (as far as I can tell) to paste a
> copied value into search boxes. Not being able to do so can be
> inconvenient, for example, when searching for a string like a UUID in
> result output, etc.
>
>
>
> Is lack of support for pasting intentional, or am I missing something?
>
>
>
> Thanks in advance,
>
> Tim
>
>
>
>
>
> --
> Tim A. Thompson (*he, him*)
> Librarian for Applied Metadata Research
> Yale University Library
> www.linkedin.com/in/timathompson
>
>
>


[basex-talk] GUI feature request: paste into search boxes

2024-01-17 Thread Thompson, Timothy
Hello,

In the BaseX GUI, it’s not possible (as far as I can tell) to paste a copied 
value into search boxes. Not being able to do so can be inconvenient, for 
example, when searching for a string like a UUID in result output, etc.

Is lack of support for pasting intentional, or am I missing something?

Thanks in advance,
Tim


--
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
www.linkedin.com/in/timathompson



Re: [basex-talk] GUI doesn't quit on Mac

2022-11-09 Thread Joe Wicentowski
This works perfectly, Christian. Thank you!

On Wed, Nov 9, 2022 at 4:51 AM Christian Grün 
wrote:

> Hi Joe, hi Steve,
>
> Thanks to Michael’s initiative, a new snapshot is available that may
> solve the problems you observed [1].
>
> Your feedback is welcome,
> Christian
>
> PS: BaseX 10.4 will be released before end of this month.
>
> [1] https://files.basex.org/releases/latest/
>
>
>
>
> On Wed, Nov 9, 2022 at 9:47 AM Michael Seiferle  wrote:
> >
> > Hi Joe,
> >
> > Hi list,
> >
> >
> >
> > I remember having a shared screen-screen-session with Christian not too
> long ago, where we tried to pin down the issue and iirc “it worked back
> then” — but obviously not for too long. It’s a rather odd behavior
> >
> >
> >
> > I fully agree with Joe, whether we click that little X or select Quit
> from the menu bar, the app should fully close.
> >
> >
> >
> > We are looking into this again :-)
> >
> >
> > You may follow my progress here:
> https://github.com/BaseXdb/basex/pull/2149
> >
> >
> > Best
> >
> >
> > Michael
> >
> >
> >
> >
> > Von: BaseX-Talk  im Auftrag
> von Joe Wicentowski 
> > Datum: Mittwoch, 9. November 2022 um 01:21
> > An: Majewski, Steven Dennis (sdm7g) 
> > Cc: BaseX 
> > Betreff: Re: [basex-talk] GUI doesn't quit on Mac
> >
> > As a Mac user, I do not generally expect closing a window via the red
> window button to quit an app. With only a few exceptions (e.g., single
> window only apps like the Calculator), closing any/all of an app's windows
> will keep the app open; apps that remain open after their windows are
> closed generally take a click on the app's Dock icon as a signal to open a
> new window.
> >
> >
> >
> > But I do expect that selecting Quit via the menu bar will fully quit the
> app. Respecting that Quit command is far more important than treating the
> red window button as a request to Quit.
> >
> >
> >
> > A few times I've needed to restart my Mac to install a software update
> or finish installing a piece of software. Typically, these processes
> present the user with a dialog to trigger the restart, which, when
> accepted, causes the OS to quit all open apps. In this scenario, BaseX
> causes the restart to fail, because it will not quit when told, and the
> restart will time out unless you find out how to quit it. (I use control-C
> in the Terminal window where I ran the `basexgui` command.)
> >
> >
> >
> > I hope this sheds some light on the matter. Thanks!
> >
> >
> >
> > On Tue, Nov 8, 2022 at 3:11 PM Majewski, Steven Dennis (sdm7g) <
> sd...@virginia.edu> wrote:
> >
> > It looks like it does exit, after a short delay, when closed by clicking
> the red button on the window, instead of quoting from the menu.
> >
> >
> >
> > — Steve.
> >
> >
> >
> >
> >
> > On Nov 8, 2022, at 3:04 PM, Christian Grün 
> wrote:
> >
> >
> >
> > Thanks for the observation. Mac support was improved in general with
> Java 11, but it still requires some OS-specific tweaks in the code. Our
> current solution may not be complete enough to achieve the expected default
> behavior [1].
> >
> >
> >
> > I’m no Mac user, but does it make a difference if the GUI is quit a) via
> the menu or b) the red icon?
> >
> >
> >
> > [1]
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
> >
> >
> >
> >
> >
> > Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:
> >
> > I've been experiencing this problem too on macOS (both 12 Monterey and
> now 13 Ventura), installed via Homebrew, and started via the `basexgui`
> command line command.
> >
> >
> >
> > On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
> sd...@virginia.edu> wrote:
> >
> > I’ve been having a problem for a while where after attempting to quit
> the Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
> when it actually started happening. Wondering if anyone else has had this
> issue, and whether it’s Mac specific or JDK version specific.
> >
> >
> >
> >
> >
> > MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
> >
> > Openjdk from home-brew install — currently openjdk/19.0.1, but was
> happening on earlier versions.
> >
> > And the current and last several versions of BaseX
> >
> >
> >
> > — Steve M.
> >
> >
> >
> >
> >
> >
>


Re: [basex-talk] GUI doesn't quit on Mac

2022-11-09 Thread Christian Grün
Hi Joe, hi Steve,

Thanks to Michael’s initiative, a new snapshot is available that may
solve the problems you observed [1].

Your feedback is welcome,
Christian

PS: BaseX 10.4 will be released before end of this month.

[1] https://files.basex.org/releases/latest/




On Wed, Nov 9, 2022 at 9:47 AM Michael Seiferle  wrote:
>
> Hi Joe,
>
> Hi list,
>
>
>
> I remember having a shared screen-screen-session with Christian not too long 
> ago, where we tried to pin down the issue and iirc “it worked back then” — 
> but obviously not for too long. It’s a rather odd behavior
>
>
>
> I fully agree with Joe, whether we click that little X or select Quit from 
> the menu bar, the app should fully close.
>
>
>
> We are looking into this again :-)
>
>
> You may follow my progress here: https://github.com/BaseXdb/basex/pull/2149
>
>
> Best
>
>
> Michael
>
>
>
>
> Von: BaseX-Talk  im Auftrag von 
> Joe Wicentowski 
> Datum: Mittwoch, 9. November 2022 um 01:21
> An: Majewski, Steven Dennis (sdm7g) 
> Cc: BaseX 
> Betreff: Re: [basex-talk] GUI doesn't quit on Mac
>
> As a Mac user, I do not generally expect closing a window via the red window 
> button to quit an app. With only a few exceptions (e.g., single window only 
> apps like the Calculator), closing any/all of an app's windows will keep the 
> app open; apps that remain open after their windows are closed generally take 
> a click on the app's Dock icon as a signal to open a new window.
>
>
>
> But I do expect that selecting Quit via the menu bar will fully quit the app. 
> Respecting that Quit command is far more important than treating the red 
> window button as a request to Quit.
>
>
>
> A few times I've needed to restart my Mac to install a software update or 
> finish installing a piece of software. Typically, these processes present the 
> user with a dialog to trigger the restart, which, when accepted, causes the 
> OS to quit all open apps. In this scenario, BaseX causes the restart to fail, 
> because it will not quit when told, and the restart will time out unless you 
> find out how to quit it. (I use control-C in the Terminal window where I ran 
> the `basexgui` command.)
>
>
>
> I hope this sheds some light on the matter. Thanks!
>
>
>
> On Tue, Nov 8, 2022 at 3:11 PM Majewski, Steven Dennis (sdm7g) 
>  wrote:
>
> It looks like it does exit, after a short delay, when closed by clicking the 
> red button on the window, instead of quoting from the menu.
>
>
>
> — Steve.
>
>
>
>
>
> On Nov 8, 2022, at 3:04 PM, Christian Grün  wrote:
>
>
>
> Thanks for the observation. Mac support was improved in general with Java 11, 
> but it still requires some OS-specific tweaks in the code. Our current 
> solution may not be complete enough to achieve the expected default behavior 
> [1].
>
>
>
> I’m no Mac user, but does it make a difference if the GUI is quit a) via the 
> menu or b) the red icon?
>
>
>
> [1] 
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
>
>
>
>
>
> Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:
>
> I've been experiencing this problem too on macOS (both 12 Monterey and now 13 
> Ventura), installed via Homebrew, and started via the `basexgui` command line 
> command.
>
>
>
> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) 
>  wrote:
>
> I’ve been having a problem for a while where after attempting to quit the Mac 
> GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t 
> able to track how this tracks with MacOS / JDK / BaseX updates and when it 
> actually started happening. Wondering if anyone else has had this issue, and 
> whether it’s Mac specific or JDK version specific.
>
>
>
>
>
> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
>
> Openjdk from home-brew install — currently openjdk/19.0.1, but was happening 
> on earlier versions.
>
> And the current and last several versions of BaseX
>
>
>
> — Steve M.
>
>
>
>
>
>


Re: [basex-talk] GUI doesn't quit on Mac

2022-11-09 Thread Michael Seiferle
Hi Joe,
Hi list,

I remember having a shared screen-screen-session with Christian not too long 
ago, where we tried to pin down the issue and iirc “it worked back then” — but 
obviously not for too long. It’s a rather odd behavior

I fully agree with Joe, whether we click that little X or select Quit from the 
menu bar, the app should fully close.

We are looking into this again :-)

You may follow my progress here: https://github.com/BaseXdb/basex/pull/2149

Best

Michael


Von: BaseX-Talk  im Auftrag von Joe 
Wicentowski 
Datum: Mittwoch, 9. November 2022 um 01:21
An: Majewski, Steven Dennis (sdm7g) 
Cc: BaseX 
Betreff: Re: [basex-talk] GUI doesn't quit on Mac
As a Mac user, I do not generally expect closing a window via the red window 
button to quit an app. With only a few exceptions (e.g., single window only 
apps like the Calculator), closing any/all of an app's windows will keep the 
app open; apps that remain open after their windows are closed generally take a 
click on the app's Dock icon as a signal to open a new window.

But I do expect that selecting Quit via the menu bar will fully quit the app. 
Respecting that Quit command is far more important than treating the red window 
button as a request to Quit.

A few times I've needed to restart my Mac to install a software update or 
finish installing a piece of software. Typically, these processes present the 
user with a dialog to trigger the restart, which, when accepted, causes the OS 
to quit all open apps. In this scenario, BaseX causes the restart to fail, 
because it will not quit when told, and the restart will time out unless you 
find out how to quit it. (I use control-C in the Terminal window where I ran 
the `basexgui` command.)

I hope this sheds some light on the matter. Thanks!

On Tue, Nov 8, 2022 at 3:11 PM Majewski, Steven Dennis (sdm7g) 
mailto:sd...@virginia.edu>> wrote:
It looks like it does exit, after a short delay, when closed by clicking the 
red button on the window, instead of quoting from the menu.

— Steve.



On Nov 8, 2022, at 3:04 PM, Christian Grün 
mailto:christian.gr...@gmail.com>> wrote:

Thanks for the observation. Mac support was improved in general with Java 11, 
but it still requires some OS-specific tweaks in the code. Our current solution 
may not be complete enough to achieve the expected default behavior [1].

I’m no Mac user, but does it make a difference if the GUI is quit a) via the 
menu or b) the red icon?

[1] 
https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584


Joe Wicentowski mailto:joe...@gmail.com>> schrieb am Di., 8. 
Nov. 2022, 20:54:
I've been experiencing this problem too on macOS (both 12 Monterey and now 13 
Ventura), installed via Homebrew, and started via the `basexgui` command line 
command.

On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) 
mailto:sd...@virginia.edu>> wrote:
I’ve been having a problem for a while where after attempting to quit the Mac 
GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t able 
to track how this tracks with MacOS / JDK / BaseX updates and when it actually 
started happening. Wondering if anyone else has had this issue, and whether 
it’s Mac specific or JDK version specific.


MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
Openjdk from home-brew install — currently openjdk/19.0.1, but was happening on 
earlier versions.
And the current and last several versions of BaseX


— Steve M.







Re: [basex-talk] GUI doesn't quit on Mac

2022-11-08 Thread Joe Wicentowski
As a Mac user, I do not generally expect closing a window via the red
window button to quit an app. With only a few exceptions (e.g., single
window only apps like the Calculator), closing any/all of an app's windows
will keep the app open; apps that remain open after their windows are
closed generally take a click on the app's Dock icon as a signal to open a
new window.

But I do expect that selecting Quit via the menu bar will fully quit the
app. Respecting that Quit command is far more important than treating the
red window button as a request to Quit.

A few times I've needed to restart my Mac to install a software update or
finish installing a piece of software. Typically, these processes present
the user with a dialog to trigger the restart, which, when accepted, causes
the OS to quit all open apps. In this scenario, BaseX causes the restart to
fail, because it will not quit when told, and the restart will time out
unless you find out how to quit it. (I use control-C in the Terminal window
where I ran the `basexgui` command.)

I hope this sheds some light on the matter. Thanks!

On Tue, Nov 8, 2022 at 3:11 PM Majewski, Steven Dennis (sdm7g) <
sd...@virginia.edu> wrote:

> It looks like it does exit, after a short delay, when closed by clicking
> the red button on the window, instead of quoting from the menu.
>
> — Steve.
>
>
> On Nov 8, 2022, at 3:04 PM, Christian Grün 
> wrote:
>
> Thanks for the observation. Mac support was improved in general with Java
> 11, but it still requires some OS-specific tweaks in the code. Our current
> solution may not be complete enough to achieve the expected default
> behavior [1].
>
> I’m no Mac user, but does it make a difference if the GUI is quit a) via
> the menu or b) the red icon?
>
> [1]
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
>
>
>
> Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:
>
>> I've been experiencing this problem too on macOS (both 12 Monterey and
>> now 13 Ventura), installed via Homebrew, and started via the `basexgui`
>> command line command.
>>
>> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
>> sd...@virginia.edu> wrote:
>>
>>> I’ve been having a problem for a while where after attempting to quit
>>> the Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
>>> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
>>> when it actually started happening. Wondering if anyone else has had this
>>> issue, and whether it’s Mac specific or JDK version specific.
>>>
>>>
>>> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
>>> Openjdk from home-brew install — currently openjdk/19.0.1, but was
>>> happening on earlier versions.
>>> And the current and last several versions of BaseX
>>>
>>> — Steve M.
>>>
>>>
>>>
>


Re: [basex-talk] GUI doesn't quit on Mac

2022-11-08 Thread Majewski, Steven Dennis (sdm7g)
It looks like it does exit, after a short delay, when closed by clicking the 
red button on the window, instead of quoting from the menu. 

— Steve. 


> On Nov 8, 2022, at 3:04 PM, Christian Grün  wrote:
> 
> Thanks for the observation. Mac support was improved in general with Java 11, 
> but it still requires some OS-specific tweaks in the code. Our current 
> solution may not be complete enough to achieve the expected default behavior 
> [1].
> 
> I’m no Mac user, but does it make a difference if the GUI is quit a) via the 
> menu or b) the red icon?
> 
> [1] 
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
>  
> 
> 
> 
> 
> Joe Wicentowski mailto:joe...@gmail.com>> schrieb am Di., 
> 8. Nov. 2022, 20:54:
> I've been experiencing this problem too on macOS (both 12 Monterey and now 13 
> Ventura), installed via Homebrew, and started via the `basexgui` command line 
> command.
> 
> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) 
> mailto:sd...@virginia.edu>> wrote:
> I’ve been having a problem for a while where after attempting to quit the Mac 
> GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t 
> able to track how this tracks with MacOS / JDK / BaseX updates and when it 
> actually started happening. Wondering if anyone else has had this issue, and 
> whether it’s Mac specific or JDK version specific. 
> 
> 
> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
> Openjdk from home-brew install — currently openjdk/19.0.1, but was happening 
> on earlier versions. 
> And the current and last several versions of BaseX 
> 
> — Steve M. 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature


Re: [basex-talk] GUI doesn't quit on Mac

2022-11-08 Thread Christian Grün
Thanks for the observation. Mac support was improved in general with Java
11, but it still requires some OS-specific tweaks in the code. Our current
solution may not be complete enough to achieve the expected default
behavior [1].

I’m no Mac user, but does it make a difference if the GUI is quit a) via
the menu or b) the red icon?

[1]
https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584



Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:

> I've been experiencing this problem too on macOS (both 12 Monterey and now
> 13 Ventura), installed via Homebrew, and started via the `basexgui` command
> line command.
>
> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
> sd...@virginia.edu> wrote:
>
>> I’ve been having a problem for a while where after attempting to quit the
>> Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
>> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
>> when it actually started happening. Wondering if anyone else has had this
>> issue, and whether it’s Mac specific or JDK version specific.
>>
>>
>> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
>> Openjdk from home-brew install — currently openjdk/19.0.1, but was
>> happening on earlier versions.
>> And the current and last several versions of BaseX
>>
>> — Steve M.
>>
>>
>>


Re: [basex-talk] GUI doesn't quit on Mac

2022-11-08 Thread Joe Wicentowski
I've been experiencing this problem too on macOS (both 12 Monterey and now
13 Ventura), installed via Homebrew, and started via the `basexgui` command
line command.

On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
sd...@virginia.edu> wrote:

> I’ve been having a problem for a while where after attempting to quit the
> Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
> when it actually started happening. Wondering if anyone else has had this
> issue, and whether it’s Mac specific or JDK version specific.
>
>
> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
> Openjdk from home-brew install — currently openjdk/19.0.1, but was
> happening on earlier versions.
> And the current and last several versions of BaseX
>
> — Steve M.
>
>
>


[basex-talk] GUI doesn't quit on Mac

2022-11-08 Thread Majewski, Steven Dennis (sdm7g)
I’ve been having a problem for a while where after attempting to quit the Mac 
GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t able 
to track how this tracks with MacOS / JDK / BaseX updates and when it actually 
started happening. Wondering if anyone else has had this issue, and whether 
it’s Mac specific or JDK version specific. 


MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
Openjdk from home-brew install — currently openjdk/19.0.1, but was happening on 
earlier versions. 
And the current and last several versions of BaseX 

— Steve M. 




smime.p7s
Description: S/MIME cryptographic signature


Re: [basex-talk] GUI syntax highlighting

2022-03-23 Thread Marc Coenegracht
Thank you Christian, from a happy night coder.

Best,
Marc



On Wed, 23 Mar 2022, Christian Grün wrote:

> Fixed [1]; thanks for the observation.
> All the best, Christian
>
> [1] https://files.basex.org/releases/latest/
>
>
>
> > The syntax highlighting doesn't change when changing the look and feel in
> > the BaseX GUI (9.6.2). I noticed this also happens in earlier versions.
> > After changing to a dark background this results in blue on black, for
> > instance. This happens with the JTattoo lib, but also GTK under a dark
> > Linux theme.
> >
> > This occurs in Linux, all kinds of distro's, both Debian and Fedora
> > based. Open JDK 11.0.6.
> >
> > In BaseX GUI 8.6.x all is fine, running under the same conditions.
> >
> >
> > Regards,
> > Marc
> >
>

Re: [basex-talk] GUI syntax highlighting

2022-03-23 Thread Christian Grün
Fixed [1]; thanks for the observation.
All the best, Christian

[1] https://files.basex.org/releases/latest/



> The syntax highlighting doesn't change when changing the look and feel in
> the BaseX GUI (9.6.2). I noticed this also happens in earlier versions.
> After changing to a dark background this results in blue on black, for
> instance. This happens with the JTattoo lib, but also GTK under a dark
> Linux theme.
>
> This occurs in Linux, all kinds of distro's, both Debian and Fedora
> based. Open JDK 11.0.6.
>
> In BaseX GUI 8.6.x all is fine, running under the same conditions.
>
>
> Regards,
> Marc
>


[basex-talk] GUI syntax highlighting

2022-03-22 Thread marc
The syntax highlighting doesn't change when changing the look and feel in
the BaseX GUI (9.6.2). I noticed this also happens in earlier versions.
After changing to a dark background this results in blue on black, for
instance. This happens with the JTattoo lib, but also GTK under a dark
Linux theme.

This occurs in Linux, all kinds of distro's, both Debian and Fedora
based. Open JDK 11.0.6.

In BaseX GUI 8.6.x all is fine, running under the same conditions.


Regards,
Marc



Re: [basex-talk] GUI Stack Trace

2020-06-08 Thread Christian Grün
Hi Ben,

> I got past this by switching to 1.11

Good to hear that it has been fixed in Java itself.

> Linux seems to have lots of problems with Java IMHO regarding rendering.

That’s true. Many Linux environments seem to ignore (or contradict)
the Java Swing conventions. In the BaseX code, we tried to find
compromise that does justice to both the Java rules and OS settings;
see e.g. [1]. If you want to have a fixed Look and Feel, you can
choose one in the GUI preferences, and you can add the JTattoo library
to your classpath [2].

Hope this helps,
Christian

PS: Thanks for the kudos.

[1] https://github.com/BaseXdb/basex/issues/1746
[2] https://docs.basex.org/wiki/Graphical_User_Interface#Look_and_Feel



  For instance, people seem to love that dark theme, but they're not
consistent.  It's very common to have icons that have solid black
foreground with a dark gray background, regardless of what Linux theme
you ask the system to pick.  I'm using Cinnamon, but I'm not sure if
that means I'm also using some flavor of Gnome as well.  Eclipse has
this issue much worse than the BaseX GUI.  If I could only find the
right combination of desktop + Windowing such that I can get the same
Start menu, a desktop with icons, support for normal Linux programs
like Firefox and LibreOffice, networking apps and most importantly,
the ability to have absolutely *no dark theme*, I would be much
happier.  I tried Trinity Desktop Environment, but they apparently
stopped maintenance on it, and little things like the networking app
don't work (important on a laptop), but it looked much more like the
Windows which worked better for me.  In my experience, if it doesn't
work out of the box, changing the theme doesn't fully work.  If you
read this, thank you for listening; I hope someone has a
recommendation.
>
> Separately, I recently started a web site, but am shocked at how easy it is 
> to get something to work on BaseX.  Adding a restful service was as simple as 
> creating an XQuery module.  Amazingly, the system actually found the service 
> without a hassle.  I made absolutely no configuration files to get this to 
> work.  Even if I wanted to attach security to the service, that seems to be 
> as easy as adding an extra decorator to the service.  I'm sure there's things 
> I'm missing, but again, whoever put this software together did a phenomenal 
> job towards making this easy to use.
>
> Kind Regards,
> Ben


Re: [basex-talk] GUI Stack Trace

2020-06-07 Thread Ben Pracht
I got past this by switching to 1.11, but I was using

java-1.8.0-openjdk-1.8.0.222.b10-0.fc30.x86_64

Not sure if the Oracle version works better.

I realize this is not a Linux specific group, but I've noticed that the
BaseX people tend to be both knowledgeable and approachable beyond what I
can get on StackOverflow.  That said, Linux seems to have lots of problems
with Java IMHO regarding rendering.  For instance, people seem to love that
dark theme, but they're not consistent.  It's very common to have icons
that have solid black foreground with a dark gray background, regardless of
what Linux theme you ask the system to pick.  I'm using Cinnamon, but I'm
not sure if that means I'm also using some flavor of Gnome as well.
Eclipse has this issue much worse than the BaseX GUI.  If I could only find
the right combination of desktop + Windowing such that I can get the same
Start menu, a desktop with icons, support for normal Linux programs like
Firefox and LibreOffice, networking apps and most importantly, the ability
to have absolutely *no dark theme*, I would be much happier.  I tried
Trinity Desktop Environment, but they apparently stopped maintenance on it,
and little things like the networking app don't work (important on a
laptop), but it looked much more like the Windows which worked better for
me.  In my experience, if it doesn't work out of the box, changing the
theme doesn't fully work.  If you read this, thank you for listening; I
hope someone has a recommendation.

Separately, I recently started a web site, but am shocked at how easy it is
to get something to work on BaseX.  Adding a restful service was as simple
as creating an XQuery module.  Amazingly, the system actually found the
service without a hassle.  I made absolutely no configuration files to get
this to work.  Even if I wanted to attach security to the service, that
seems to be as easy as adding an extra decorator to the service.  I'm sure
there's things I'm missing, but again, whoever put this software together
did a phenomenal job towards making this easy to use.

Kind Regards,
Ben



Best Regards,
Ben Pracht
919.809.2439
ben.pra...@gmail.com


On Sun, Jun 7, 2020 at 4:50 AM Christian Grün 
wrote:

> Thanks, Reece, for the hint, I overlooked this one.
>
> The used Java version might be even more interesting now, as we need to
> find out in which case JLabel.setIcon triggers a nullpointer exception.
>
>
>
>
> Reece Dunn  schrieb am So., 7. Juni 2020, 09:54:
>
>> Hi Christian,
>>
>> The following is the relevant part of the stack trace:
>>
>> >
>> org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
>>
>> It is difficult to spot among the rest of the Java function calls.
>>
>> Kind regards,
>> Reece
>>
>> On Sun, 7 Jun 2020 at 07:34, Christian Grün 
>> wrote:
>>
>>> Yes, this problem seems to be caused by the combination of your Linux
>>> environment and the Java version (the stack trace only contains paths to
>>> standard Java classes). Which JDK do you use?
>>>
>>>
>>>
>>>
>>> Ben Pracht  schrieb am So., 7. Juni 2020, 06:09:
>>>
 Hi Folks,

 I got this error trying to specify a directory location when creating a
 database using the GUI by dialog.  Creating the database via command
 works.  I feel like this is somehow not the fault of BaseX because I don't
 see this on my other Linux machine.  Nonetheless, I'd like recommendations
 on how the Linux side of the basex community works.

 My setup:
 cat /etc/*release
 edora release 30 (Thirty)
 NAME=Fedora
 VERSION="30 (Workstation Edition)"
 ID=fedora
 VERSION_ID=30
 VERSION_CODENAME=""
 PLATFORM_ID="platform:f30"
 PRETTY_NAME="Fedora 30 (Workstation Edition)"
 ANSI_COLOR="0;34"
 LOGO=fedora-logo-icon
 CPE_NAME="cpe:/o:fedoraproject:fedora:30"
 HOME_URL="https://fedoraproject.org/";
 DOCUMENTATION_URL="
 https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/
 "
 SUPPORT_URL="
 https://fedoraproject.org/wiki/Communicating_and_getting_help";
 BUG_REPORT_URL="https://bugzilla.redhat.com/";
 REDHAT_BUGZILLA_PRODUCT="Fedora"
 REDHAT_BUGZILLA_PRODUCT_VERSION=30
 REDHAT_SUPPORT_PRODUCT="Fedora"
 REDHAT_SUPPORT_PRODUCT_VERSION=30
 PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
 VARIANT="Workstation Edition"
 VARIANT_ID=workstation
 Fedora release 30 (Thirty)
 Fedora release 30 (Thirty)

 export |grep DESKTOP
 declare -x DESKTOP_SESSION="/usr/share/xsessions/cinnamon2d"
 declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
 declare -x IMSETTINGS_INTEGRATE_DESKTOP="yes"
 declare -x XDG_CURRENT_DESKTOP="X-Cinnamon"
 declare -x XDG_SESSION_DESKTOP=""


 bpracht2@pracht-office-closet basex-rent-world]$ java -cp
 /home/bpracht/rent-world/basex-rent-world/BaseX.jar:/home/bpracht/rent-world/basex-rent-world/li

Re: [basex-talk] GUI Stack Trace

2020-06-07 Thread Reece Dunn
Hi Christian,

The following is the relevant part of the stack trace:

>
org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)

It is difficult to spot among the rest of the Java function calls.

Kind regards,
Reece

On Sun, 7 Jun 2020 at 07:34, Christian Grün 
wrote:

> Yes, this problem seems to be caused by the combination of your Linux
> environment and the Java version (the stack trace only contains paths to
> standard Java classes). Which JDK do you use?
>
>
>
>
> Ben Pracht  schrieb am So., 7. Juni 2020, 06:09:
>
>> Hi Folks,
>>
>> I got this error trying to specify a directory location when creating a
>> database using the GUI by dialog.  Creating the database via command
>> works.  I feel like this is somehow not the fault of BaseX because I don't
>> see this on my other Linux machine.  Nonetheless, I'd like recommendations
>> on how the Linux side of the basex community works.
>>
>> My setup:
>> cat /etc/*release
>> edora release 30 (Thirty)
>> NAME=Fedora
>> VERSION="30 (Workstation Edition)"
>> ID=fedora
>> VERSION_ID=30
>> VERSION_CODENAME=""
>> PLATFORM_ID="platform:f30"
>> PRETTY_NAME="Fedora 30 (Workstation Edition)"
>> ANSI_COLOR="0;34"
>> LOGO=fedora-logo-icon
>> CPE_NAME="cpe:/o:fedoraproject:fedora:30"
>> HOME_URL="https://fedoraproject.org/";
>> DOCUMENTATION_URL="
>> https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/
>> "
>> SUPPORT_URL="
>> https://fedoraproject.org/wiki/Communicating_and_getting_help";
>> BUG_REPORT_URL="https://bugzilla.redhat.com/";
>> REDHAT_BUGZILLA_PRODUCT="Fedora"
>> REDHAT_BUGZILLA_PRODUCT_VERSION=30
>> REDHAT_SUPPORT_PRODUCT="Fedora"
>> REDHAT_SUPPORT_PRODUCT_VERSION=30
>> PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
>> VARIANT="Workstation Edition"
>> VARIANT_ID=workstation
>> Fedora release 30 (Thirty)
>> Fedora release 30 (Thirty)
>>
>> export |grep DESKTOP
>> declare -x DESKTOP_SESSION="/usr/share/xsessions/cinnamon2d"
>> declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
>> declare -x IMSETTINGS_INTEGRATE_DESKTOP="yes"
>> declare -x XDG_CURRENT_DESKTOP="X-Cinnamon"
>> declare -x XDG_SESSION_DESKTOP=""
>>
>>
>> bpracht2@pracht-office-closet basex-rent-world]$ java -cp
>> /home/bpracht/rent-world/basex-rent-world/BaseX.jar:/home/bpracht/rent-world/basex-rent-world/lib/custom/*:/home/bpracht/rent-world/basex-rent-world/lib/*:
>> -Xms2g -Xmx4g org.basex.BaseXGUI
>>
>> Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
>> at javax.swing.JLabel.setIcon(JLabel.java:406)
>> at
>> org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
>> at
>> javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2807)
>> at
>> javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:492)
>> at
>> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:553)
>> at
>> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:199)
>> at
>> javax.swing.tree.AbstractLayoutCache.getPreferredHeight(AbstractLayoutCache.java:190)
>> at
>> javax.swing.plaf.basic.BasicTreeUI.updateCachedPreferredSize(BasicTreeUI.java:1902)
>> at
>> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:2003)
>> at
>> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:1991)
>> at javax.swing.JComponent.getPreferredSize(JComponent.java:1662)
>> at
>> javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:791)
>> at java.awt.Container.layout(Container.java:1513)
>> at java.awt.Container.doLayout(Container.java:1502)
>> at java.awt.Container.validateTree(Container.java:1698)
>> at java.awt.Container.validate(Container.java:1633)
>> at javax.swing.RepaintManager$3.run(RepaintManager.java:711)
>> at javax.swing.RepaintManager$3.run(RepaintManager.java:709)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
>> at
>> javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:708)
>> at
>> javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1731)
>> at
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
>> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
>> at java.awt.EventQueue.access$500(EventQueue.java:97)
>> at java.awt.EventQueue$3.run(EventQueue.java:709)
>> at java.awt.EventQueue$3.run(EventQueue.java:703)
>> Best Regards,
>> Ben Pracht
>> ben.pra...@gmail.com
>>
>


Re: [basex-talk] GUI Stack Trace

2020-06-07 Thread Christian Grün
Thanks, Reece, for the hint, I overlooked this one.

The used Java version might be even more interesting now, as we need to
find out in which case JLabel.setIcon triggers a nullpointer exception.




Reece Dunn  schrieb am So., 7. Juni 2020, 09:54:

> Hi Christian,
>
> The following is the relevant part of the stack trace:
>
> >
> org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
>
> It is difficult to spot among the rest of the Java function calls.
>
> Kind regards,
> Reece
>
> On Sun, 7 Jun 2020 at 07:34, Christian Grün 
> wrote:
>
>> Yes, this problem seems to be caused by the combination of your Linux
>> environment and the Java version (the stack trace only contains paths to
>> standard Java classes). Which JDK do you use?
>>
>>
>>
>>
>> Ben Pracht  schrieb am So., 7. Juni 2020, 06:09:
>>
>>> Hi Folks,
>>>
>>> I got this error trying to specify a directory location when creating a
>>> database using the GUI by dialog.  Creating the database via command
>>> works.  I feel like this is somehow not the fault of BaseX because I don't
>>> see this on my other Linux machine.  Nonetheless, I'd like recommendations
>>> on how the Linux side of the basex community works.
>>>
>>> My setup:
>>> cat /etc/*release
>>> edora release 30 (Thirty)
>>> NAME=Fedora
>>> VERSION="30 (Workstation Edition)"
>>> ID=fedora
>>> VERSION_ID=30
>>> VERSION_CODENAME=""
>>> PLATFORM_ID="platform:f30"
>>> PRETTY_NAME="Fedora 30 (Workstation Edition)"
>>> ANSI_COLOR="0;34"
>>> LOGO=fedora-logo-icon
>>> CPE_NAME="cpe:/o:fedoraproject:fedora:30"
>>> HOME_URL="https://fedoraproject.org/";
>>> DOCUMENTATION_URL="
>>> https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/
>>> "
>>> SUPPORT_URL="
>>> https://fedoraproject.org/wiki/Communicating_and_getting_help";
>>> BUG_REPORT_URL="https://bugzilla.redhat.com/";
>>> REDHAT_BUGZILLA_PRODUCT="Fedora"
>>> REDHAT_BUGZILLA_PRODUCT_VERSION=30
>>> REDHAT_SUPPORT_PRODUCT="Fedora"
>>> REDHAT_SUPPORT_PRODUCT_VERSION=30
>>> PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
>>> VARIANT="Workstation Edition"
>>> VARIANT_ID=workstation
>>> Fedora release 30 (Thirty)
>>> Fedora release 30 (Thirty)
>>>
>>> export |grep DESKTOP
>>> declare -x DESKTOP_SESSION="/usr/share/xsessions/cinnamon2d"
>>> declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
>>> declare -x IMSETTINGS_INTEGRATE_DESKTOP="yes"
>>> declare -x XDG_CURRENT_DESKTOP="X-Cinnamon"
>>> declare -x XDG_SESSION_DESKTOP=""
>>>
>>>
>>> bpracht2@pracht-office-closet basex-rent-world]$ java -cp
>>> /home/bpracht/rent-world/basex-rent-world/BaseX.jar:/home/bpracht/rent-world/basex-rent-world/lib/custom/*:/home/bpracht/rent-world/basex-rent-world/lib/*:
>>> -Xms2g -Xmx4g org.basex.BaseXGUI
>>>
>>> Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
>>> at javax.swing.JLabel.setIcon(JLabel.java:406)
>>> at
>>> org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
>>> at
>>> javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2807)
>>> at
>>> javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:492)
>>> at
>>> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:553)
>>> at
>>> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:199)
>>> at
>>> javax.swing.tree.AbstractLayoutCache.getPreferredHeight(AbstractLayoutCache.java:190)
>>> at
>>> javax.swing.plaf.basic.BasicTreeUI.updateCachedPreferredSize(BasicTreeUI.java:1902)
>>> at
>>> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:2003)
>>> at
>>> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:1991)
>>> at javax.swing.JComponent.getPreferredSize(JComponent.java:1662)
>>> at
>>> javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:791)
>>> at java.awt.Container.layout(Container.java:1513)
>>> at java.awt.Container.doLayout(Container.java:1502)
>>> at java.awt.Container.validateTree(Container.java:1698)
>>> at java.awt.Container.validate(Container.java:1633)
>>> at javax.swing.RepaintManager$3.run(RepaintManager.java:711)
>>> at javax.swing.RepaintManager$3.run(RepaintManager.java:709)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
>>> at
>>> javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:708)
>>> at
>>> javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1731)
>>> at
>>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
>>> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)

Re: [basex-talk] GUI Stack Trace

2020-06-06 Thread Christian Grün
Yes, this problem seems to be caused by the combination of your Linux
environment and the Java version (the stack trace only contains paths to
standard Java classes). Which JDK do you use?




Ben Pracht  schrieb am So., 7. Juni 2020, 06:09:

> Hi Folks,
>
> I got this error trying to specify a directory location when creating a
> database using the GUI by dialog.  Creating the database via command
> works.  I feel like this is somehow not the fault of BaseX because I don't
> see this on my other Linux machine.  Nonetheless, I'd like recommendations
> on how the Linux side of the basex community works.
>
> My setup:
> cat /etc/*release
> edora release 30 (Thirty)
> NAME=Fedora
> VERSION="30 (Workstation Edition)"
> ID=fedora
> VERSION_ID=30
> VERSION_CODENAME=""
> PLATFORM_ID="platform:f30"
> PRETTY_NAME="Fedora 30 (Workstation Edition)"
> ANSI_COLOR="0;34"
> LOGO=fedora-logo-icon
> CPE_NAME="cpe:/o:fedoraproject:fedora:30"
> HOME_URL="https://fedoraproject.org/";
> DOCUMENTATION_URL="
> https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/
> "
> SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help
> "
> BUG_REPORT_URL="https://bugzilla.redhat.com/";
> REDHAT_BUGZILLA_PRODUCT="Fedora"
> REDHAT_BUGZILLA_PRODUCT_VERSION=30
> REDHAT_SUPPORT_PRODUCT="Fedora"
> REDHAT_SUPPORT_PRODUCT_VERSION=30
> PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
> VARIANT="Workstation Edition"
> VARIANT_ID=workstation
> Fedora release 30 (Thirty)
> Fedora release 30 (Thirty)
>
> export |grep DESKTOP
> declare -x DESKTOP_SESSION="/usr/share/xsessions/cinnamon2d"
> declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
> declare -x IMSETTINGS_INTEGRATE_DESKTOP="yes"
> declare -x XDG_CURRENT_DESKTOP="X-Cinnamon"
> declare -x XDG_SESSION_DESKTOP=""
>
>
> bpracht2@pracht-office-closet basex-rent-world]$ java -cp
> /home/bpracht/rent-world/basex-rent-world/BaseX.jar:/home/bpracht/rent-world/basex-rent-world/lib/custom/*:/home/bpracht/rent-world/basex-rent-world/lib/*:
> -Xms2g -Xmx4g org.basex.BaseXGUI
>
> Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
> at javax.swing.JLabel.setIcon(JLabel.java:406)
> at
> org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
> at
> javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2807)
> at
> javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:492)
> at
> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:553)
> at
> javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:199)
> at
> javax.swing.tree.AbstractLayoutCache.getPreferredHeight(AbstractLayoutCache.java:190)
> at
> javax.swing.plaf.basic.BasicTreeUI.updateCachedPreferredSize(BasicTreeUI.java:1902)
> at
> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:2003)
> at
> javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:1991)
> at javax.swing.JComponent.getPreferredSize(JComponent.java:1662)
> at
> javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:791)
> at java.awt.Container.layout(Container.java:1513)
> at java.awt.Container.doLayout(Container.java:1502)
> at java.awt.Container.validateTree(Container.java:1698)
> at java.awt.Container.validate(Container.java:1633)
> at javax.swing.RepaintManager$3.run(RepaintManager.java:711)
> at javax.swing.RepaintManager$3.run(RepaintManager.java:709)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
> at
> javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:708)
> at
> javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1731)
> at
> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
> at java.awt.EventQueue.access$500(EventQueue.java:97)
> at java.awt.EventQueue$3.run(EventQueue.java:709)
> at java.awt.EventQueue$3.run(EventQueue.java:703)
> Best Regards,
> Ben Pracht
> ben.pra...@gmail.com
>


[basex-talk] GUI Stack Trace

2020-06-06 Thread Ben Pracht
Hi Folks,

I got this error trying to specify a directory location when creating a
database using the GUI by dialog.  Creating the database via command
works.  I feel like this is somehow not the fault of BaseX because I don't
see this on my other Linux machine.  Nonetheless, I'd like recommendations
on how the Linux side of the basex community works.

My setup:
cat /etc/*release
edora release 30 (Thirty)
NAME=Fedora
VERSION="30 (Workstation Edition)"
ID=fedora
VERSION_ID=30
VERSION_CODENAME=""
PLATFORM_ID="platform:f30"
PRETTY_NAME="Fedora 30 (Workstation Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:30"
HOME_URL="https://fedoraproject.org/";
DOCUMENTATION_URL="
https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/
"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help";
BUG_REPORT_URL="https://bugzilla.redhat.com/";
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=30
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=30
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
VARIANT="Workstation Edition"
VARIANT_ID=workstation
Fedora release 30 (Thirty)
Fedora release 30 (Thirty)

export |grep DESKTOP
declare -x DESKTOP_SESSION="/usr/share/xsessions/cinnamon2d"
declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
declare -x IMSETTINGS_INTEGRATE_DESKTOP="yes"
declare -x XDG_CURRENT_DESKTOP="X-Cinnamon"
declare -x XDG_SESSION_DESKTOP=""


bpracht2@pracht-office-closet basex-rent-world]$ java -cp
/home/bpracht/rent-world/basex-rent-world/BaseX.jar:/home/bpracht/rent-world/basex-rent-world/lib/custom/*:/home/bpracht/rent-world/basex-rent-world/lib/*:
-Xms2g -Xmx4g org.basex.BaseXGUI

Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
at javax.swing.JLabel.setIcon(JLabel.java:406)
at
org.basex.gui.view.project.ProjectCellRenderer.getTreeCellRendererComponent(ProjectCellRenderer.java:29)
at
javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2807)
at
javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:492)
at
javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:553)
at
javax.swing.tree.FixedHeightLayoutCache.getBounds(FixedHeightLayoutCache.java:199)
at
javax.swing.tree.AbstractLayoutCache.getPreferredHeight(AbstractLayoutCache.java:190)
at
javax.swing.plaf.basic.BasicTreeUI.updateCachedPreferredSize(BasicTreeUI.java:1902)
at
javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:2003)
at
javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(BasicTreeUI.java:1991)
at javax.swing.JComponent.getPreferredSize(JComponent.java:1662)
at
javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:791)
at java.awt.Container.layout(Container.java:1513)
at java.awt.Container.doLayout(Container.java:1502)
at java.awt.Container.validateTree(Container.java:1698)
at java.awt.Container.validate(Container.java:1633)
at javax.swing.RepaintManager$3.run(RepaintManager.java:711)
at javax.swing.RepaintManager$3.run(RepaintManager.java:709)
at java.security.AccessController.doPrivileged(Native Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at
javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:708)
at
javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1731)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
Best Regards,
Ben Pracht
ben.pra...@gmail.com


Re: [basex-talk] GUI "create db" file patterns are not sticky

2020-05-11 Thread Graydon
On Mon, May 11, 2020 at 10:49:10PM +0200, Christian Grün scripsit:
> > ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, 
> > or at least I still get only "*.xml" as a suffix in the "File Patterns" box.
> 
> I found out why this doesn’t work: In the database creation dialog,
> CREATEFILTER depends on the input format (XML, JSON, etc.). It is
> always overwritten when the dialog is opened and when this value is
> changed. Well… I’ll think about that.

Thank you!

-- Graydon


Re: [basex-talk] GUI "create db" file patterns are not sticky

2020-05-11 Thread Christian Grün
> ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, or 
> at least I still get only "*.xml" as a suffix in the "File Patterns" box.

I found out why this doesn’t work: In the database creation dialog,
CREATEFILTER depends on the input format (XML, JSON, etc.). It is
always overwritten when the dialog is opened and when this value is
changed. Well… I’ll think about that.


Re: [basex-talk] GUI "create db" file patterns are not sticky

2020-05-11 Thread Graydon
On Mon, May 11, 2020 at 09:23:34AM +0200, Christian Grün scripsit:
> Hi Graydon,

Hi Christian --

[sensible reasons for why it does that snipped]
> If you want to make database options persistent, you can manually add
> them at the bottom of the .basex configuration file [1]. It’s
> recommendable to quit the GUI before editing the file, as the
> graphical user interface might overwrite your changes when it’s
> closed.

So if I edit ~/.basex so that the last lines are:

# Local Options
ARCHIVENAME = true

# create databases
CREATEFILTER = *.xml,*.met
ADDARCHIVES = false
CHOP = false
INTPARSE = true


ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, or at 
least I still get only "*.xml" as a suffix in the "File Patterns" box.

Am I doing this wrong? This is with 9.3.2.

Thanks!
Graydon


Re: [basex-talk] GUI "create db" file patterns are not sticky

2020-05-11 Thread Christian Grün
Hi Graydon,

In the BaseX GUI dialog, some options are pure GUI options, and
others, such as CREATEFILTER, are standard database options. The
latter ones are discarded, as they would also affect other BaseX
instances, such as the standalone mode. If you finish a GUI dialog
operation, you can have a look at the Info View panel, in which those
options will be listed. They are assigned via the SET command.

If you want to make database options persistent, you can manually add
them at the bottom of the .basex configuration file [1]. It’s
recommendable to quit the GUI before editing the file, as the
graphical user interface might overwrite your changes when it’s
closed.

Hope this helps,
Christian

[1] https://docs.basex.org/wiki/Configuration#Configuration_Files


On Thu, May 7, 2020 at 6:11 PM Graydon Saunders  wrote:
>
> This is a very small feature request.
>
> Everything else about the Create Database GUI is sticky -- when changed it 
> stays changed -- EXCEPT the file patterns.  Would it be possible to make the 
> file patterns sticky as well?
>
> I often need to create a new database repeatedly since I'm using XQuery to 
> test output from XSLT processes during development.  Remembering to add all 
> the file patterns is not excessively burdensome but I would like to not have 
> to do it.
>
> Thanks!
> Graydon


[basex-talk] GUI "create db" file patterns are not sticky

2020-05-07 Thread Graydon Saunders
This is a very small feature request.

Everything else about the Create Database GUI is sticky -- when changed it
stays changed -- EXCEPT the file patterns.  Would it be possible to make
the file patterns sticky as well?

I often need to create a new database repeatedly since I'm using XQuery to
test output from XSLT processes during development.  Remembering to add all
the file patterns is not excessively burdensome but I would like to not
have to do it.

Thanks!
Graydon


Re: [basex-talk] GUI, visualization panels

2019-09-10 Thread Giuseppe G. A. Celano
Hi, no, I just open the GUI and then an XML document. Thanks.

> On Sep 9, 2019, at 2:52 PM, Alexander Holupirek  wrote:
> 
> Hi Giuseppe,
> 
> just gave it a try using basex 9.2.4 with java version "1.8.0_121" on macOS 
> 10.14.6.
> I was not able to reproduce the issue so far.
> 
> One thing, did you open a database first? Visualization are only available on 
> (opened) databases (not in-memory documents, such as XML read from 
> filesystem, http, ...)
> 
> Kind regards,
>   Alex
> 
>> On 7. Sep 2019, at 15:56, Giuseppe G. A. Celano 
>>  wrote:
>> 
>> 1.8.0_171
>> 
>> Thanks.
>> 
>> 
>> 
>>> On Sep 7, 2019, at 1:43 PM, Alexander Holupirek  wrote:
>>> 
>>> Hi Giuseppe,
>>> 
>>> what java version do you use?
>>> 
>>> Kind regards,
>>> Alex
>>> 
 Am 07.09.2019 um 11:42 schrieb Giuseppe G. A. Celano 
 :
 
 Hi,
 
 Apparently, I cannot access the visualization panels in the GUI on my Mac 
 (10.13.6) (they cannot be selected): am I missing anything? Thanks.
 
 Best,
 Giuseppe
>>> 
>> 
> 
> 



[basex-talk] GUI, visualization panels

2019-09-07 Thread Giuseppe G. A. Celano
Hi,

Apparently, I cannot access the visualization panels in the GUI on my Mac 
(10.13.6) (they cannot be selected): am I missing anything? Thanks.

Best,
Giuseppe

Re: [basex-talk] GUI not counting all updates?

2019-06-26 Thread France Baril
Awesome, thanks!

On Wed, Jun 19, 2019 at 9:31 AM Christian Grün 
wrote:

> Hi France,
>
> Thanks for the hint. This was a little bug in the query info output:
> Empty string replacements were not counted as updates (with "delete
> node $i", it works). Fixed in the latest snapshot.
>
> Best,
> Christian
>
>
>
> On Wed, Jun 5, 2019 at 11:22 AM France Baril
>  wrote:
> >
> > Hi,
> >
> > I am running this query on my DB in BasexGui. The updates are performed,
> but the info window shows hit=0 and update=0.
> >
> > (
> >   for $i in db:open('en-us')//p/node()[1]
> >   return
> > if ($i instance of text() and normalize-space($i) = '')
> > then replace node $i with ''
> > else (),
> >   for $i in db:open('en-us')//p/node()[last()]
> >   return
> > if ($i instance of text() and normalize-space($i) = '')
> > then replace node $i with ''
> > else ()
> > )
> >
> > The DB has items like this one:
> >
> > 
> >  Turn off
> projector
> >   Switch off projector
> >   Projector off 
> >   Turn projector off
> >   Deactivate
> projector
> >Disable
> projector 
> > 
> >
> > --
> > France Baril
> > Architecte documentaire / Documentation architect
> > france.ba...@architextus.com
>


-- 
France Baril
Architecte documentaire / Documentation architect
france.ba...@architextus.com


Re: [basex-talk] GUI not counting all updates?

2019-06-19 Thread Christian Grün
Hi France,

Thanks for the hint. This was a little bug in the query info output:
Empty string replacements were not counted as updates (with "delete
node $i", it works). Fixed in the latest snapshot.

Best,
Christian



On Wed, Jun 5, 2019 at 11:22 AM France Baril
 wrote:
>
> Hi,
>
> I am running this query on my DB in BasexGui. The updates are performed, but 
> the info window shows hit=0 and update=0.
>
> (
>   for $i in db:open('en-us')//p/node()[1]
>   return
> if ($i instance of text() and normalize-space($i) = '')
> then replace node $i with ''
> else (),
>   for $i in db:open('en-us')//p/node()[last()]
>   return
> if ($i instance of text() and normalize-space($i) = '')
> then replace node $i with ''
> else ()
> )
>
> The DB has items like this one:
>
> 
>  Turn off projector
> 
>   Switch off projector
>   Projector off 
>   Turn projector off
>   Deactivate projector
>Disable projector 
> 
> 
>
> --
> France Baril
> Architecte documentaire / Documentation architect
> france.ba...@architextus.com


[basex-talk] GUI not counting all updates?

2019-06-05 Thread France Baril
Hi,

I am running this query on my DB in BasexGui. The updates are performed,
but the info window shows hit=0 and update=0.

(
  for $i in db:open('en-us')//p/node()[1]
  return
if ($i instance of text() and normalize-space($i) = '')
then replace node $i with ''
else (),
  for $i in db:open('en-us')//p/node()[last()]
  return
if ($i instance of text() and normalize-space($i) = '')
then replace node $i with ''
else ()
)

The DB has items like this one:


 Turn off projector
  
  Switch off projector
  Projector off 
  Turn projector off
  Deactivate
projector
   Disable projector
   


-- 
France Baril
Architecte documentaire / Documentation architect
france.ba...@architextus.com


Re: [basex-talk] GUI

2018-06-29 Thread Giuseppe Celano
Yes, the problem with the GUI started with Java 10. I was reluctant to upgrade 
to Java 10, but I was assuming I could still use BaseXGUI 8.x.


> On Jun 29, 2018, at 7:59 PM, Christian Grün  wrote:
> 
> Hi Giuseppe,
> 
> You’ll probably need to wait until we have worked on the issue that Alex has 
> referenced in an earlier reply. For now, I recommend you to stick with Java 
> 8. As Oracle will only provide LTS versions for Java 8 and 11 (but not for 
> version 9 and 10), Java 11 will be the next version that we’ll officially 
> support.
> 
> Did you time to check if the errors you reported in your last mail are 
> dependent on the Java version you are using?
> 
> Best,
> Christian
> 
> 
> 
> 
> 
> Giuseppe Celano  > schrieb am Fr., 29. Juni 2018, 
> 19:55:
> Hi Christian,
> 
> After I installed Java 10, I cannot use BaseXGUI 8.x anymore. The standalone 
> access of BaseX 8.x is possible, but not with the GUI. The following is the 
> error message (which is partially the same I get with BaseXGUI 9.0, but in 
> that case I can still open the GUI):
> 
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX 
> (file:/Users/mycomputer/Desktop/basex%20867/BaseX.jar) to method 
> com.apple.eawt.Application.getApplication()
> WARNING: Please consider reporting this to the maintainers of 
> org.basex.gui.GUIMacOSX
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Failed to initialize native Mac OS X interface
> 
> 
> Thanks!
> Giuseppe
> 
> 
>> On Jun 29, 2018, at 6:04 PM, Christian Grün > > wrote:
>> 
>> Hi Giuseppe,
>> 
>> Did this happen with BaseX 8, too? Does it make a difference which
>> Java version you are using?
>> 
>> Cheers,
>> Christian
>> 
>> 
>> On Fri, Jun 29, 2018 at 5:04 PM Giuseppe Celano
>> mailto:cel...@informatik.uni-leipzig.de>> 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> I have also noticed that after evaluating a query, BaseXGUI continues to 
>>> "work", absorbing CPU  (as I can see in my "Activity monitor" and in the 
>>> "Used Memory" field of the GUI). I do not know if this is somehow related 
>>> to the org.basex.gui.GUIMacOSX problem, but it happens regularly.
>>> 
>>> Best,
>>> Giuseppe
>>> 
>>> 
>>> Universität Leipzig
>>> Institute of Computer Science, NLP
>>> Augustusplatz 10
>>> 04109 Leipzig
>>> Deutschland
>>> E-mail: cel...@informatik.uni-leipzig.de 
>>> 
>>> E-mail: giuseppegacel...@gmail.com 
>>> Web site 1: http://www.dh.uni-leipzig.de/wo/team/ 
>>> 
>>> Web site 2: https://sites.google.com/site/giuseppegacelano/ 
>>> 
>>> 
>>> On Jun 21, 2018, at 9:48 AM, Alexander Holupirek >> > wrote:
>>> 
>>> Hi Guiseppe,
>>> 
>>> it is a known issue and refers to macOS-specific features that have been 
>>> removed, starting in JDK 9.
>>> 
>>> We've already started to prepare a fix and I've just filed an issue [1] for 
>>> it.
>>> 
>>> All the best,
>>> Alex
>>> 
>>> [1] https://github.com/BaseXdb/basex/issues/1582 
>>> 
>>> 
>>> On 20. Jun 2018, at 21:28, Giuseppe Celano 
>>> >> > wrote:
>>> 
>>> Hi,
>>> 
>>> I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
>>> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access 
>>> the relevant tabs). Is this a known issue? Moreover, if I start the GUI 
>>> from the command line, I keep getting the warning message "Illegal 
>>> reflective access by org.basex.gui.GUIMacOSX". Is there a way to avoid 
>>> that? Thanks.
>>> 
>>> Ciao,
>>> Giuseppe
>>> 
>>> 
>>> Universität Leipzig
>>> Institute of Computer Science, NLP
>>> Augustusplatz 10
>>> 04109 Leipzig
>>> Deutschland
>>> E-mail: cel...@informatik.uni-leipzig.de 
>>> 
>>> E-mail: giuseppegacel...@gmail.com 
>>> Web site 1: http://www.dh.uni-leipzig.de/wo/team/ 
>>> 
>>> Web site 2: https://sites.google.com/site/giuseppegacelano/ 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
> 
> 



Re: [basex-talk] GUI

2018-06-29 Thread Christian Grün
Hi Giuseppe,

You’ll probably need to wait until we have worked on the issue that Alex
has referenced in an earlier reply. For now, I recommend you to stick with
Java 8. As Oracle will only provide LTS versions for Java 8 and 11 (but not
for version 9 and 10), Java 11 will be the next version that we’ll
officially support.

Did you time to check if the errors you reported in your last mail are
dependent on the Java version you are using?

Best,
Christian





Giuseppe Celano  schrieb am Fr., 29. Juni
2018, 19:55:

> Hi Christian,
>
> After I installed Java 10, I cannot use BaseXGUI 8.x anymore. The
> standalone access of BaseX 8.x is possible, but not with the GUI. The
> following is the error message (which is partially the same I get with
> BaseXGUI 9.0, but in that case I can still open the GUI):
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX
> (file:/Users/mycomputer/Desktop/basex%20867/BaseX.jar) to method
> com.apple.eawt.Application.getApplication()
> WARNING: Please consider reporting this to the maintainers of
> org.basex.gui.GUIMacOSX
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Failed to initialize native Mac OS X interface
>
>
> Thanks!
> Giuseppe
>
>
> On Jun 29, 2018, at 6:04 PM, Christian Grün 
> wrote:
>
> Hi Giuseppe,
>
> Did this happen with BaseX 8, too? Does it make a difference which
> Java version you are using?
>
> Cheers,
> Christian
>
>
> On Fri, Jun 29, 2018 at 5:04 PM Giuseppe Celano
>  wrote:
>
>
> Hi,
>
> I have also noticed that after evaluating a query, BaseXGUI continues to
> "work", absorbing CPU  (as I can see in my "Activity monitor" and in the
> "Used Memory" field of the GUI). I do not know if this is somehow related
> to the org.basex.gui.GUIMacOSX problem, but it happens regularly.
>
> Best,
> Giuseppe
>
>
> Universität Leipzig
> Institute of Computer Science, NLP
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> 
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
>
> On Jun 21, 2018, at 9:48 AM, Alexander Holupirek 
> wrote:
>
> Hi Guiseppe,
>
> it is a known issue and refers to macOS-specific features that have been
> removed, starting in JDK 9.
>
> We've already started to prepare a fix and I've just filed an issue [1]
> for it.
>
> All the best,
> Alex
>
> [1] https://github.com/BaseXdb/basex/issues/1582
>
> On 20. Jun 2018, at 21:28, Giuseppe Celano <
> cel...@informatik.uni-leipzig.de> wrote:
>
> Hi,
>
> I  have updated Java (10 from 8) and I cannot apparently customize the GUI
> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access
> the relevant tabs). Is this a known issue? Moreover, if I start the GUI
> from the command line, I keep getting the warning message "Illegal
> reflective access by org.basex.gui.GUIMacOSX". Is there a way to avoid
> that? Thanks.
>
> Ciao,
> Giuseppe
>
>
> Universität Leipzig
> Institute of Computer Science, NLP
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
>
>
>
>
>
>
>
>


Re: [basex-talk] GUI

2018-06-29 Thread Giuseppe Celano
Hi Christian,

After I installed Java 10, I cannot use BaseXGUI 8.x anymore. The standalone 
access of BaseX 8.x is possible, but not with the GUI. The following is the 
error message (which is partially the same I get with BaseXGUI 9.0, but in that 
case I can still open the GUI):

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX 
(file:/Users/mycomputer/Desktop/basex%20867/BaseX.jar) to method 
com.apple.eawt.Application.getApplication()
WARNING: Please consider reporting this to the maintainers of 
org.basex.gui.GUIMacOSX
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Failed to initialize native Mac OS X interface


Thanks!
Giuseppe


> On Jun 29, 2018, at 6:04 PM, Christian Grün  wrote:
> 
> Hi Giuseppe,
> 
> Did this happen with BaseX 8, too? Does it make a difference which
> Java version you are using?
> 
> Cheers,
> Christian
> 
> 
> On Fri, Jun 29, 2018 at 5:04 PM Giuseppe Celano
>  wrote:
>> 
>> Hi,
>> 
>> I have also noticed that after evaluating a query, BaseXGUI continues to 
>> "work", absorbing CPU  (as I can see in my "Activity monitor" and in the 
>> "Used Memory" field of the GUI). I do not know if this is somehow related to 
>> the org.basex.gui.GUIMacOSX problem, but it happens regularly.
>> 
>> Best,
>> Giuseppe
>> 
>> 
>> Universität Leipzig
>> Institute of Computer Science, NLP
>> Augustusplatz 10
>> 04109 Leipzig
>> Deutschland
>> E-mail: cel...@informatik.uni-leipzig.de
>> E-mail: giuseppegacel...@gmail.com
>> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
>> Web site 2: https://sites.google.com/site/giuseppegacelano/
>> 
>> On Jun 21, 2018, at 9:48 AM, Alexander Holupirek  wrote:
>> 
>> Hi Guiseppe,
>> 
>> it is a known issue and refers to macOS-specific features that have been 
>> removed, starting in JDK 9.
>> 
>> We've already started to prepare a fix and I've just filed an issue [1] for 
>> it.
>> 
>> All the best,
>> Alex
>> 
>> [1] https://github.com/BaseXdb/basex/issues/1582
>> 
>> On 20. Jun 2018, at 21:28, Giuseppe Celano 
>>  wrote:
>> 
>> Hi,
>> 
>> I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
>> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access 
>> the relevant tabs). Is this a known issue? Moreover, if I start the GUI from 
>> the command line, I keep getting the warning message "Illegal reflective 
>> access by org.basex.gui.GUIMacOSX". Is there a way to avoid that? Thanks.
>> 
>> Ciao,
>> Giuseppe
>> 
>> 
>> Universität Leipzig
>> Institute of Computer Science, NLP
>> Augustusplatz 10
>> 04109 Leipzig
>> Deutschland
>> E-mail: cel...@informatik.uni-leipzig.de
>> E-mail: giuseppegacel...@gmail.com
>> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
>> Web site 2: https://sites.google.com/site/giuseppegacelano/
>> 
>> 
>> 
>> 
> 



Re: [basex-talk] GUI

2018-06-29 Thread Christian Grün
Hi Giuseppe,

Did this happen with BaseX 8, too? Does it make a difference which
Java version you are using?

Cheers,
Christian


On Fri, Jun 29, 2018 at 5:04 PM Giuseppe Celano
 wrote:
>
> Hi,
>
> I have also noticed that after evaluating a query, BaseXGUI continues to 
> "work", absorbing CPU  (as I can see in my "Activity monitor" and in the 
> "Used Memory" field of the GUI). I do not know if this is somehow related to 
> the org.basex.gui.GUIMacOSX problem, but it happens regularly.
>
> Best,
> Giuseppe
>
>
> Universität Leipzig
> Institute of Computer Science, NLP
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
>
> On Jun 21, 2018, at 9:48 AM, Alexander Holupirek  wrote:
>
> Hi Guiseppe,
>
> it is a known issue and refers to macOS-specific features that have been 
> removed, starting in JDK 9.
>
> We've already started to prepare a fix and I've just filed an issue [1] for 
> it.
>
> All the best,
> Alex
>
> [1] https://github.com/BaseXdb/basex/issues/1582
>
> On 20. Jun 2018, at 21:28, Giuseppe Celano  
> wrote:
>
> Hi,
>
> I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access 
> the relevant tabs). Is this a known issue? Moreover, if I start the GUI from 
> the command line, I keep getting the warning message "Illegal reflective 
> access by org.basex.gui.GUIMacOSX". Is there a way to avoid that? Thanks.
>
> Ciao,
> Giuseppe
>
>
> Universität Leipzig
> Institute of Computer Science, NLP
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
>
>
>
>


Re: [basex-talk] GUI

2018-06-29 Thread Giuseppe Celano
Hi,

I have also noticed that after evaluating a query, BaseXGUI continues to 
"work", absorbing CPU  (as I can see in my "Activity monitor" and in the "Used 
Memory" field of the GUI). I do not know if this is somehow related to the 
org.basex.gui.GUIMacOSX problem, but it happens regularly.

Best,
Giuseppe 


Universität Leipzig
Institute of Computer Science, NLP
Augustusplatz 10
04109 Leipzig
Deutschland
E-mail: cel...@informatik.uni-leipzig.de
E-mail: giuseppegacel...@gmail.com
Web site 1: http://www.dh.uni-leipzig.de/wo/team/
Web site 2: https://sites.google.com/site/giuseppegacelano/

> On Jun 21, 2018, at 9:48 AM, Alexander Holupirek  wrote:
> 
> Hi Guiseppe,
> 
> it is a known issue and refers to macOS-specific features that have been 
> removed, starting in JDK 9.
> 
> We've already started to prepare a fix and I've just filed an issue [1] for 
> it.
> 
> All the best,
>   Alex
> 
> [1] https://github.com/BaseXdb/basex/issues/1582
> 
>> On 20. Jun 2018, at 21:28, Giuseppe Celano 
>>  wrote:
>> 
>> Hi,
>> 
>> I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
>> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access 
>> the relevant tabs). Is this a known issue? Moreover, if I start the GUI from 
>> the command line, I keep getting the warning message "Illegal reflective 
>> access by org.basex.gui.GUIMacOSX". Is there a way to avoid that? Thanks.
>> 
>> Ciao,
>> Giuseppe
>> 
>> 
>> Universität Leipzig
>> Institute of Computer Science, NLP
>> Augustusplatz 10
>> 04109 Leipzig
>> Deutschland
>> E-mail: cel...@informatik.uni-leipzig.de
>> E-mail: giuseppegacel...@gmail.com
>> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
>> Web site 2: https://sites.google.com/site/giuseppegacelano/
>> 
> 
> 



Re: [basex-talk] GUI

2018-06-21 Thread Alexander Holupirek
Hi Guiseppe,

it is a known issue and refers to macOS-specific features that have been 
removed, starting in JDK 9.

We've already started to prepare a fix and I've just filed an issue [1] for it.

All the best,
Alex

[1] https://github.com/BaseXdb/basex/issues/1582

> On 20. Jun 2018, at 21:28, Giuseppe Celano  
> wrote:
> 
> Hi,
> 
> I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
> anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access 
> the relevant tabs). Is this a known issue? Moreover, if I start the GUI from 
> the command line, I keep getting the warning message "Illegal reflective 
> access by org.basex.gui.GUIMacOSX". Is there a way to avoid that? Thanks.
> 
> Ciao,
> Giuseppe
> 
> 
> Universität Leipzig
> Institute of Computer Science, NLP
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
> 



[basex-talk] GUI

2018-06-20 Thread Giuseppe Celano
Hi,

I  have updated Java (10 from 8) and I cannot apparently customize the GUI 
anymore on my Mac (if I click on BaseXGUI > aboutBaseXGUI, I cannot access the 
relevant tabs). Is this a known issue? Moreover, if I start the GUI from the 
command line, I keep getting the warning message "Illegal reflective access by 
org.basex.gui.GUIMacOSX". Is there a way to avoid that? Thanks.

Ciao,
Giuseppe


Universität Leipzig
Institute of Computer Science, NLP
Augustusplatz 10
04109 Leipzig
Deutschland
E-mail: cel...@informatik.uni-leipzig.de
E-mail: giuseppegacel...@gmail.com
Web site 1: http://www.dh.uni-leipzig.de/wo/team/
Web site 2: https://sites.google.com/site/giuseppegacelano/



Re: [basex-talk] GUI

2018-04-16 Thread Giuseppe Celano
Yes, I can now see it! Thanks!

Universität Leipzig
Institute of Computer Science, Digital Humanities
Augustusplatz 10
04109 Leipzig
Deutschland
E-mail: cel...@informatik.uni-leipzig.de
E-mail: giuseppegacel...@gmail.com
Web site 1: http://www.dh.uni-leipzig.de/wo/team/
Web site 2: https://sites.google.com/site/giuseppegacelano/

> On Apr 16, 2018, at 11:05 AM, Andy Bunce  wrote:
> 
> Hi Giuseppe,
> 
> It has been moved to be the 1st button on the toolbar "New"(or ctl-T)
> 
> /Andy
> 
> On 16 April 2018 at 09:55, Giuseppe Celano  > wrote:
> I see that in the 9.0 version the "+ button" to add a new tab is missing. I 
> think it was very useful: can it be re-introduced in the following releases?
> 
> Best,
> Giuseppe
> 
> 
> Universität Leipzig
> Institute of Computer Science
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de 
> 
> E-mail: giuseppegacel...@gmail.com 
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/ 
> 
> Web site 2: https://sites.google.com/site/giuseppegacelano/ 
> 
> 
> 



Re: [basex-talk] GUI

2018-04-16 Thread Andy Bunce
 Hi Giuseppe,

It has been moved to be the 1st button on the toolbar "New"(or ctl-T)

/Andy

On 16 April 2018 at 09:55, Giuseppe Celano  wrote:

> I see that in the 9.0 version the "+ button" to add a new tab is missing.
> I think it was very useful: can it be re-introduced in the following
> releases?
>
> Best,
> Giuseppe
>
>
> Universität Leipzig
> Institute of Computer Science
> Augustusplatz 10
> 04109 Leipzig
> Deutschland
> E-mail: cel...@informatik.uni-leipzig.de
> E-mail: giuseppegacel...@gmail.com
> Web site 1: http://www.dh.uni-leipzig.de/wo/team/
> Web site 2: https://sites.google.com/site/giuseppegacelano/
>
>


[basex-talk] GUI

2018-04-16 Thread Giuseppe Celano
I see that in the 9.0 version the "+ button" to add a new tab is missing. I 
think it was very useful: can it be re-introduced in the following releases?

Best,
Giuseppe


Universität Leipzig
Institute of Computer Science
Augustusplatz 10
04109 Leipzig
Deutschland
E-mail: cel...@informatik.uni-leipzig.de
E-mail: giuseppegacel...@gmail.com
Web site 1: http://www.dh.uni-leipzig.de/wo/team/
Web site 2: https://sites.google.com/site/giuseppegacelano/



Re: [basex-talk] GUI

2017-08-06 Thread Thomas Daly
Many thanks, this makes sense.

Thomas

-Original Message-
From: Liam R. E. Quin [mailto:l...@w3.org] 
Sent: 05 August 2017 21:06
To: Thomas Daly; basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] GUI

On Sat, 2017-08-05 at 16:52 +0100, Thomas Daly wrote:
>  
> 
> a)  It is not possible to log into a BaseX database running on a 
> remote server from a GUI running on a different machine?

You can probably also do it the other way round, setting DISPLAY and running 
BaseX on the server system with its display pointing to your system, e.g, using 
an ssh tunnel so you don't need to expose your system to the raw Internet. See 
e.g. https://askubuntu.com/questions/20
3173/run-application-on-local-machine-and-show-gui-on-remote-display
for using ssh -X or -Y to the server. You have to arrange for your X server to 
listen for remote connections I think.


> b)  Do I need any particular Linux distribution / GUI version to 
> run the BaseX Linux GUI?

No. I use Mageia Linux under Gnome 3, but as Christian said, you just need Java.

Liam

--
Liam Quin, W3C, http://www.w3.org/People/Quin/ Staff contact for Verifiable 
Claims WG, XQuery WG

Web slave for http://www.fromoldbooks.org/



Re: [basex-talk] GUI

2017-08-05 Thread Liam R. E. Quin
On Sat, 2017-08-05 at 16:52 +0100, Thomas Daly wrote:
>  
> 
> a)  It is not possible to log into a BaseX database running on a
> remote
> server from a GUI running on a different machine?

You can probably also do it the other way round, setting DISPLAY and
running BaseX on the server system with its display pointing to your
system, e.g, using an ssh tunnel so you don't need to expose your
system to the raw Internet. See e.g. https://askubuntu.com/questions/20
3173/run-application-on-local-machine-and-show-gui-on-remote-display
for using ssh -X or -Y to the server. You have to arrange for your X
server to listen for remote connections I think.


> b)  Do I need any particular Linux distribution / GUI version to
> run the BaseX Linux GUI?

No. I use Mageia Linux under Gnome 3, but as Christian said, you just
need Java.

Liam

-- 
Liam Quin, W3C, http://www.w3.org/People/Quin/
Staff contact for Verifiable Claims WG, XQuery WG

Web slave for http://www.fromoldbooks.org/


Re: [basex-talk] GUI

2017-08-05 Thread Christian Grün
Hi Thomas,

a) No, that's not possible. The visualizations rely on a tight coupling
with the database; socket communication would be too slow.

b) BaseX works with all Linux distributions that have a JRE.

Christian



Am 05.08.2017 17:52 schrieb "Thomas Daly" :



a)  It is not possible to log into a BaseX database running on a remote
server from a GUI running on a different machine?

b)  Do I need any particular Linux distribution / GUI version to run
the BaseX Linux GUI?





Many thanks,

Thomas


[basex-talk] GUI

2017-08-05 Thread Thomas Daly
 

a)  It is not possible to log into a BaseX database running on a remote
server from a GUI running on a different machine?

b)  Do I need any particular Linux distribution / GUI version to run the
BaseX Linux GUI?

 

 

Many thanks,

Thomas



Re: [basex-talk] GUI: Horizontal splitting needed

2016-01-05 Thread Christian Grün
Hi Alex,

If you talk about horizontal window splitting, do you refer to the
editor panel? Would you like to duplicate a single file, or do you
want to have different files displayed side by side?

Christian



On Tue, Jan 5, 2016 at 4:29 AM, Alex R. Loayza  wrote:
> Hello,
>
> I'd like to suggest an improvement to the GUI: the ability to split the
> window horizontally, as you can do in IDEA or Visual Studio. I'm finding
> myself all too frequently scrolling up and down between functions or
> variables. After a while, it wears you out.
>
> A horizontal split would make BaseX's already great GUI, even better. Hope
> you agree and we can find it in BaseX 8.4!
>
> Best regards,
>
> Alex
>


[basex-talk] GUI: Horizontal splitting needed

2016-01-04 Thread Alex R. Loayza
Hello,
I'd like to suggest an improvement to the GUI: the ability to split the window 
horizontally, as you can do in IDEA or Visual Studio. I'm finding myself all 
too frequently scrolling up and down between functions or variables. After a 
while, it wears you out.
A horizontal split would make BaseX's already great GUI, even better. Hope you 
agree and we can find it in BaseX 8.4!
Best regards,
Alex



Re: [basex-talk] GUI feature request "Add as import"

2016-01-03 Thread Christian Grün
Hi Andy,

> I never got round for thanking you for this,
>  I found it a great time saver , but it was a bit dodgy and now it seems it
> has gone in the latest 8.4 :-).

I should have told you about the recent removal… When having another
look at the feature, it didn’t feel good indeed, because it was simply
too much of a hack. For now, you can possibly save some time by typing
"im" and ctrl-space (but you’ll have to add the module prefix,
namespace and location by yourself...).

> What I really want, in the editor, is an module import wizard that allows me
> to pick from a variety of sources e.g. relative files, the repository

Oh yes, me too ;) In BaseX 8.4, as you may have seen, all erroneous
files in the project view, and their ancestor directories, will be
highlighted red. This is because XQuery modules are now compiled in
the background, and it may be the first step to provide some
context-aware code completion.

Cheers,
Christian


>
> /Andy
>
> On 23 December 2014 at 16:22, Christian Grün 
> wrote:
>>
>> Hi Andy,
>>
>> I have added your requested menu item "Add as Import" in BaseX [1].
>> The feature, as implemented right now, feels a bit dodgy, because it
>> does many things in one place (parsing a file, extracting things,
>> building a string, adding it to the editor), and I haven't checked all
>> possible error cases yet. But after all it cannot cause any real
>> problems.. I decided to add the import statement at the cursor
>> position. It's probably the most flexible solution as long as we don't
>> do real parsing.
>>
>> Cheers,
>> Christian
>>
>> [1] https://github.com/BaseXdb/basex/issues/1027
>>
>>
>>
>> On Thu, Nov 13, 2014 at 12:57 PM, Andy Bunce  wrote:
>> > Hi,
>> >
>> > I often find myself adding module imports in the GUI and I wonder if the
>> > following suggestion might speed up that process.
>> >
>> > Add a new menu item to the filelist right click context menu "Add as
>> > import"
>> > when the file selection is a XQuery module.
>> >
>> > The action would be to add a line to the current edit window source with
>> >
>> > import module namespace {$prefix} = '{$namespace}' at {$path};
>> >
>> > Where $prefix and $namespace} are read from the source of the selected
>> > file,
>> > and $path is calculated from the relative path from the edit file source
>> > to
>> > the selected filelist source. The line would be inserted at a suitable
>> > place
>> > in the prologue or at the current location if that is too tricky.
>> >
>> > /Andy
>> >
>> >
>> >
>
>


Re: [basex-talk] GUI feature request "Add as import"

2016-01-02 Thread Andy Bunce
Hi Christian,

I never got round for thanking you for this,
 I found it a great time saver , but it was a bit dodgy and now it seems it
has gone in the latest 8.4 :-).

>It's probably the most flexible solution as long as we don't do real
parsing.

And now you do?
What I really want, in the editor, is an module import wizard that allows
me to pick from a variety of sources e.g. relative files, the repository

/Andy

On 23 December 2014 at 16:22, Christian Grün 
wrote:

> Hi Andy,
>
> I have added your requested menu item "Add as Import" in BaseX [1].
> The feature, as implemented right now, feels a bit dodgy, because it
> does many things in one place (parsing a file, extracting things,
> building a string, adding it to the editor), and I haven't checked all
> possible error cases yet. But after all it cannot cause any real
> problems.. I decided to add the import statement at the cursor
> position. It's probably the most flexible solution as long as we don't
> do real parsing.
>
> Cheers,
> Christian
>
> [1] https://github.com/BaseXdb/basex/issues/1027
>
>
>
> On Thu, Nov 13, 2014 at 12:57 PM, Andy Bunce  wrote:
> > Hi,
> >
> > I often find myself adding module imports in the GUI and I wonder if the
> > following suggestion might speed up that process.
> >
> > Add a new menu item to the filelist right click context menu "Add as
> import"
> > when the file selection is a XQuery module.
> >
> > The action would be to add a line to the current edit window source with
> >
> > import module namespace {$prefix} = '{$namespace}' at {$path};
> >
> > Where $prefix and $namespace} are read from the source of the selected
> file,
> > and $path is calculated from the relative path from the edit file source
> to
> > the selected filelist source. The line would be inserted at a suitable
> place
> > in the prologue or at the current location if that is too tricky.
> >
> > /Andy
> >
> >
> >
>


Re: [basex-talk] GUI Textindex: false although true

2015-12-16 Thread Christian Grün
PS: I’ve just added a little flush call, which will now be called
before the database dialog is opened. The new snapshot is available in
a few minutes [1].

Christian

[1] http://files.basex.org/releases/latest/

On Wed, Dec 16, 2015 at 2:59 PM, Christian Grün
 wrote:
> Hi Benjamin,
>
>> I have played around with the options in BaseX to test the speed of CREATE 
>> and ADD operations.
>> Now the GUI "Open and manage" box shows me for any DB I create:
>> Up-to-date: true
>> TEXTINDEX: false
>> ATTRINDEX: false
>
> The reason is the autoflush flag: The meta data has not been written
> to disk yet. "true" will be displayed once you close the database in
> the GUI.
>
>> as does a "GET TEXTINDEX" (returns "true").
>
> Please be aware that this command will always give you the value of
> the global option. You can use INFO DB to get info on the currently
> opened database.
>
> Hope this helps,
> Christian
>
>
>>
>> I only made the following changes:
>> set updindex true; set autooptimize true; set autoflush false;
>>
>> --
>>
>> Joe Security LLC
>>
>> Benjamin Gathmann, Developer & Support
>> business parc Reinach, Christoph Merian-Ring 11, 4153 Reinach, Switzerland
>> benjamin.gathm...@joesecurity.org, http://www.joesecurity.org
>>
>> 
>>
>> The information contained in this email and any attachments is confidential 
>> and may be subject to copyright or other intellectual property protection. 
>> If you are not the intended recipient, you are not authorized to use or 
>> disclose this information, and we request that you notify us by reply mail 
>> or telephone and delete the original message from your mail system.


Re: [basex-talk] GUI Textindex: false although true

2015-12-16 Thread Christian Grün
Hi Benjamin,

> I have played around with the options in BaseX to test the speed of CREATE 
> and ADD operations.
> Now the GUI "Open and manage" box shows me for any DB I create:
> Up-to-date: true
> TEXTINDEX: false
> ATTRINDEX: false

The reason is the autoflush flag: The meta data has not been written
to disk yet. "true" will be displayed once you close the database in
the GUI.

> as does a "GET TEXTINDEX" (returns "true").

Please be aware that this command will always give you the value of
the global option. You can use INFO DB to get info on the currently
opened database.

Hope this helps,
Christian


>
> I only made the following changes:
> set updindex true; set autooptimize true; set autoflush false;
>
> --
>
> Joe Security LLC
>
> Benjamin Gathmann, Developer & Support
> business parc Reinach, Christoph Merian-Ring 11, 4153 Reinach, Switzerland
> benjamin.gathm...@joesecurity.org, http://www.joesecurity.org
>
> 
>
> The information contained in this email and any attachments is confidential 
> and may be subject to copyright or other intellectual property protection. If 
> you are not the intended recipient, you are not authorized to use or disclose 
> this information, and we request that you notify us by reply mail or 
> telephone and delete the original message from your mail system.


[basex-talk] GUI Textindex: false although true

2015-12-16 Thread Benjamin Gathmann
I use the GUI of the current release 8.3.1.
I have played around with the options in BaseX to test the speed of
CREATE and ADD operations.
Now the GUI "Open and manage" box shows me for any DB I create:
Up-to-date: true 
TEXTINDEX: false 
ATTRINDEX: false

However, I have never set TEXTINDEX or ATTRINDEX to false, and the files
in the "data" directory suggest that the indexes are there, as does a
"GET TEXTINDEX" (returns "true").

I only made the following changes:
set updindex true; set autooptimize true; set autoflush false;

-- 
joe-security-logo

Joe Security LLC

Benjamin Gathmann, Developer & Support
business parc Reinach, Christoph Merian-Ring 11, 4153 Reinach, Switzerland
benjamin.gathm...@joesecurity.org
, http://www.joesecurity.org



The information contained in this email and any attachments is
confidential and may be subject to copyright or other intellectual
property protection. If you are not the intended recipient, you are not
authorized to use or disclose this information, and we request that you
notify us by reply mail or telephone and delete the original message
from your mail system.



Re: [basex-talk] Gui

2015-06-18 Thread Christian Grün
Hi Joseph,

> I point out that In the last release, the number of repetions of a for clause 
> is not displayed anymore on the top right corner of the GUI. This was very 
> useful.

I am wondering what you mean by "number of repetions".. Do you refer
to the number of results of a query? It should still be displayed in
the top right corner.

Best,
Christian


[basex-talk] Gui

2015-06-17 Thread meumapple
Hallo,

I point out that In the last release, the number of repetions of a for clause 
is not displayed anymore on the top right corner of the GUI. This was very 
useful.

Thanks,
Joseph



Re: [basex-talk] GUI suggestion: no trace output when running tests

2015-03-24 Thread Christian Grün
Hi Marc,

I perfectly agree… It's a bit tricky indeed to cache all the debugging
information in the GUI mode, but we are frequently running into this,
too. I'll see what I can do.

Best,
Christian



On Sat, Mar 21, 2015 at 6:16 PM, Marc van Grootel
 wrote:
> Hi,
>
> When running tests from the GUI I sometimes insert debugging code to
> figure out which tests fails or why. The current behavior of the GUI
> makes this impossible though because when tests are run this info is
> printed to the Query Info window but immediately after tests are run
> it prints the test summary overwriting the debugging info (such as
> trace output).
>
> Currently I then go to the command-line but it might be an idea to
> somehow keep the output generated during test run visible.
>
> Cheers,
> --Marc


Re: [basex-talk] gui folder view delete

2015-03-24 Thread Christian Grün
> Personally I would be happy with the delete of multiple documents,  Could it
> not warn me in that case?
> Does another GUI document delete function suffer the same issue? I mean
> Menu:database>properties and then the  delete key in the document tree?

I just noticed that in this view, if there are documents with
identical names, only one will be listed..

Our middle-term plan is to only allow the insertion of documents with
unique names and paths. This will make things easier again..



>
> /Andy
>
> On 13 March 2015 at 11:42, Christian Grün  wrote:
>>
>> …fixed. I disallowed the deletion of document nodes, because it
>> resolves to the query db:delete($db, $path), and this query could
>> potentially delete more than a single document.
>>
>>
>> On Thu, Mar 12, 2015 at 9:44 PM, Andy Bunce  wrote:
>> > Hi,
>> > In  the GUI folder view I can delete nodes by selecting and using right
>> > click.
>> > But if I select a  top level  document name entry the UI prompts for
>> > delete
>> > confirmation but no delete occurs.
>> >
>> > /Andy
>> >
>
>


Re: [basex-talk] gui folder view delete

2015-03-22 Thread Andy Bunce
Personally I would be happy with the delete of multiple documents,  Could
it not warn me in that case?
Does another GUI document delete function suffer the same issue? I mean
Menu:database>properties and then the  delete key in the document tree?

/Andy

On 13 March 2015 at 11:42, Christian Grün  wrote:

> …fixed. I disallowed the deletion of document nodes, because it
> resolves to the query db:delete($db, $path), and this query could
> potentially delete more than a single document.
>
>
> On Thu, Mar 12, 2015 at 9:44 PM, Andy Bunce  wrote:
> > Hi,
> > In  the GUI folder view I can delete nodes by selecting and using right
> > click.
> > But if I select a  top level  document name entry the UI prompts for
> delete
> > confirmation but no delete occurs.
> >
> > /Andy
> >
>


[basex-talk] GUI suggestion: no trace output when running tests

2015-03-21 Thread Marc van Grootel
Hi,

When running tests from the GUI I sometimes insert debugging code to
figure out which tests fails or why. The current behavior of the GUI
makes this impossible though because when tests are run this info is
printed to the Query Info window but immediately after tests are run
it prints the test summary overwriting the debugging info (such as
trace output).

Currently I then go to the command-line but it might be an idea to
somehow keep the output generated during test run visible.

Cheers,
--Marc


Re: [basex-talk] gui folder view delete

2015-03-13 Thread Christian Grün
…fixed. I disallowed the deletion of document nodes, because it
resolves to the query db:delete($db, $path), and this query could
potentially delete more than a single document.


On Thu, Mar 12, 2015 at 9:44 PM, Andy Bunce  wrote:
> Hi,
> In  the GUI folder view I can delete nodes by selecting and using right
> click.
> But if I select a  top level  document name entry the UI prompts for delete
> confirmation but no delete occurs.
>
> /Andy
>


[basex-talk] gui folder view delete

2015-03-12 Thread Andy Bunce
Hi,
In  the GUI folder view I can delete nodes by selecting and using right
click.
But if I select a  top level  document name entry the UI prompts for delete
confirmation but no delete occurs.

/Andy


Re: [basex-talk] GUI feature request "Add as import"

2014-12-23 Thread Christian Grün
Hi Andy,

I have added your requested menu item "Add as Import" in BaseX [1].
The feature, as implemented right now, feels a bit dodgy, because it
does many things in one place (parsing a file, extracting things,
building a string, adding it to the editor), and I haven't checked all
possible error cases yet. But after all it cannot cause any real
problems.. I decided to add the import statement at the cursor
position. It's probably the most flexible solution as long as we don't
do real parsing.

Cheers,
Christian

[1] https://github.com/BaseXdb/basex/issues/1027



On Thu, Nov 13, 2014 at 12:57 PM, Andy Bunce  wrote:
> Hi,
>
> I often find myself adding module imports in the GUI and I wonder if the
> following suggestion might speed up that process.
>
> Add a new menu item to the filelist right click context menu "Add as import"
> when the file selection is a XQuery module.
>
> The action would be to add a line to the current edit window source with
>
> import module namespace {$prefix} = '{$namespace}' at {$path};
>
> Where $prefix and $namespace} are read from the source of the selected file,
> and $path is calculated from the relative path from the edit file source to
> the selected filelist source. The line would be inserted at a suitable place
> in the prologue or at the current location if that is too tricky.
>
> /Andy
>
>
>


Re: [basex-talk] GUI feature request "Add as import"

2014-11-16 Thread Christian Grün
Hi Andy,

thanks for the useful feature request. As I need some more thoughts on
how to implement this properly, I have added a new GitHub issue [1].
Currently (and I guess you do something similar), I usually open the
module to be imported, I copy the module declaration, paste it to the
importing module and add the relative URL.

A good alternative would be to have an "Organize Import" feature
similar to the one in Eclipse (triggered e.g. by the shortcut
Ctrl+Shift+O), which automatically adds modules that have not been
imported yet, and removes unused imports from the query prolog.

For all of those features, we could either decide to offer
straightforward solutions that work in 90% of the cases, but that are
not based on parsing the code, and thus fail miserably in the
remaining cases. Of course, my preference would be to do it right, but
it may then happen that nothing happens at all…

Christian

[1] https://github.com/BaseXdb/basex/issues/1027


> I often find myself adding module imports in the GUI and I wonder if the
> following suggestion might speed up that process.
>
> Add a new menu item to the filelist right click context menu "Add as import"
> when the file selection is a XQuery module.
>
> The action would be to add a line to the current edit window source with
>
> import module namespace {$prefix} = '{$namespace}' at {$path};
>
> Where $prefix and $namespace} are read from the source of the selected file,
> and $path is calculated from the relative path from the edit file source to
> the selected filelist source. The line would be inserted at a suitable place
> in the prologue or at the current location if that is too tricky.
>
> /Andy
>
>
>


[basex-talk] GUI feature request "Add as import"

2014-11-13 Thread Andy Bunce
Hi,

I often find myself adding module imports in the GUI and I wonder if the
following suggestion might speed up that process.

Add a new menu item to the filelist right click context menu "Add as
import" when the file selection is a XQuery module.

The action would be to add a line to the current edit window source with

import module namespace {$prefix} = '{$namespace}' at {$path};

Where $prefix and $namespace} are read from the source of the selected
file, and $path is calculated from the relative path from the edit file
source to the selected filelist source. The line would be inserted at a
suitable place in the prologue or at the current location if that is too
tricky.

/Andy


Re: [basex-talk] GUI Editor, Code Completions

2013-11-19 Thread Erdal Karaca
Hi Christian,
The Eclipse Xtext project [1] might be of interest to you which provides
facilities to create a full IDE like editor with syntax highlighting,
(context sensitive) code completion. Though, it may not be well suited to
the BaseX GUI as it is targeted at Eclipse/SWT.

Erdal

[1] http://www.eclipse.org/Xtext/


2013/11/19 Christian Grün 

> Dear followers,
>
> we are interested to get your opinion on the code completions that
> we’ve just added to the text editor of our BaseX GUI [1]. You are
> invited to propose templates that you are missing here!
>
> Many of you would probably love to have context-based code completions
> (such as all functions in the current context, etc.). All I can say is
> that this is indeed planned for a future version of BaseX.
>
> Beside that, we’ve just added an implementation of the upcoming EXPath
> Binary Module [2]. As usual, a new stable snapshot is available, which
> contains the new features [3].
>
> Thanks all,
> Christian
>
> [1] http://docs.basex.org/wiki/Shortcuts#Code_Completions
> [2] http://docs.basex.org/wiki/Binary_Module
> [3] http://files.basex.org/releases/latest/
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] GUI Editor, Code Completions

2013-11-19 Thread Christian Grün
Dear followers,

we are interested to get your opinion on the code completions that
we’ve just added to the text editor of our BaseX GUI [1]. You are
invited to propose templates that you are missing here!

Many of you would probably love to have context-based code completions
(such as all functions in the current context, etc.). All I can say is
that this is indeed planned for a future version of BaseX.

Beside that, we’ve just added an implementation of the upcoming EXPath
Binary Module [2]. As usual, a new stable snapshot is available, which
contains the new features [3].

Thanks all,
Christian

[1] http://docs.basex.org/wiki/Shortcuts#Code_Completions
[2] http://docs.basex.org/wiki/Binary_Module
[3] http://files.basex.org/releases/latest/
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot of documents

2013-03-26 Thread Fabrice Etanchaud
Dear all,
I'm sorry but I see no difference.

That's not a blocking issue at all.

And once again thank you for your fantastic XNDB.

Best,
Fabrice

-Message d'origine-
De : Christian Grün [mailto:christian.gr...@gmail.com] 
Envoyé : mardi 26 mars 2013 14:50
À : Fabrice Etanchaud
Cc : basex-talk@mailman.uni-konstanz.de
Objet : Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot 
of documents

Hi Fabrice,
and thanks Lukas,

I've just uploaded another snapshot; could you give it another try?

Best,
Christian
___

On Tue, Mar 26, 2013 at 2:40 PM, Fabrice Etanchaud  
wrote:
> Dear Lukas, thank you for your help !
>
>
>
> Is this fix present in the delivery of this morning ?
>
> The problem is still present.
>
>
>
> Best regards,
>
> Fabrice
>
>
>
>
>
> "The heart of fools is in their mouth, but the mouth of the wise men 
> is in their heart"
>
> -- Siracide
>
>
>
> De : Lukas Kircher [mailto:lukaskirch...@gmail.com] Envoyé : mardi 26 
> mars 2013 10:26 À : Fabrice Etanchaud Cc : 
> basex-talk@mailman.uni-konstanz.de
> Objet : Re: [basex-talk] [GUI] Properties window is frozen for a DB 
> with a lot of documents
>
>
>
> Hi Fabrice,
>
>
>
> we just uploaded a fix (hopefully) for this problem. The maximum 
> number of displayed nodes is now limited. Would be nice if you could 
> report your experience with the current solution, which will be 
> contained in the next latest stable release.
>
>
>
> Cheers,
>
> Lukas
>
> On Fri, Mar 15, 2013 at 9:36 AM, Fabrice Etanchaud 
> 
> wrote:
>
> Dear all,
>
>
>
> When dealing with collections containing more than a million 
> documents,
>
> The Properties window freezes the entire GUI while  trying to display 
> the documents' list.
>
> How could I disable the treeview for such collections ?
>
>
>
> I have to deal with such collections because XQuery Update on many 
> many nodes takes a long long time to complete,
>
> So add/replace/delete is a good alternative.
>
>
>
> Thank you for your continuous help and your great XNDB.
>
>
>
> Last : is the new ADDCACHE option the way to add data near the node 
> count limit without corrupting the collection ?
>
>
>
> Best regards,
>
> Fabrice
>
> Questel-Orbit
>
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
>
>
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot of documents

2013-03-26 Thread Christian Grün
Hi Fabrice,
and thanks Lukas,

I’ve just uploaded another snapshot; could you give it another try?

Best,
Christian
___

On Tue, Mar 26, 2013 at 2:40 PM, Fabrice Etanchaud
 wrote:
> Dear Lukas, thank you for your help !
>
>
>
> Is this fix present in the delivery of this morning ?
>
> The problem is still present.
>
>
>
> Best regards,
>
> Fabrice
>
>
>
>
>
> “The heart of fools is in their mouth, but the mouth of the wise men is in
> their heart”
>
> -- Siracide
>
>
>
> De : Lukas Kircher [mailto:lukaskirch...@gmail.com]
> Envoyé : mardi 26 mars 2013 10:26
> À : Fabrice Etanchaud
> Cc : basex-talk@mailman.uni-konstanz.de
> Objet : Re: [basex-talk] [GUI] Properties window is frozen for a DB with a
> lot of documents
>
>
>
> Hi Fabrice,
>
>
>
> we just uploaded a fix (hopefully) for this problem. The maximum number of
> displayed nodes is now limited. Would be nice if you could report your
> experience with the current solution, which will be contained in the next
> latest stable release.
>
>
>
> Cheers,
>
> Lukas
>
> On Fri, Mar 15, 2013 at 9:36 AM, Fabrice Etanchaud 
> wrote:
>
> Dear all,
>
>
>
> When dealing with collections containing more than a million documents,
>
> The Properties window freezes the entire GUI while  trying to display the
> documents’ list.
>
> How could I disable the treeview for such collections ?
>
>
>
> I have to deal with such collections because XQuery Update on many many
> nodes takes a long long time to complete,
>
> So add/replace/delete is a good alternative.
>
>
>
> Thank you for your continuous help and your great XNDB.
>
>
>
> Last : is the new ADDCACHE option the way to add data near the node count
> limit without corrupting the collection ?
>
>
>
> Best regards,
>
> Fabrice
>
> Questel-Orbit
>
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
>
>
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot of documents

2013-03-26 Thread Fabrice Etanchaud
Dear Lukas, thank you for your help !

Is this fix present in the delivery of this morning ?
The problem is still present.

Best regards,
Fabrice


"The heart of fools is in their mouth, but the mouth of the wise men is in 
their heart"
-- Siracide

De : Lukas Kircher [mailto:lukaskirch...@gmail.com]
Envoyé : mardi 26 mars 2013 10:26
À : Fabrice Etanchaud
Cc : basex-talk@mailman.uni-konstanz.de
Objet : Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot 
of documents

Hi Fabrice,

we just uploaded a fix (hopefully) for this problem. The maximum number of 
displayed nodes is now limited. Would be nice if you could report your 
experience with the current solution, which will be contained in the next 
latest stable release.

Cheers,
Lukas
On Fri, Mar 15, 2013 at 9:36 AM, Fabrice Etanchaud 
mailto:fetanch...@questel.com>> wrote:
Dear all,

When dealing with collections containing more than a million documents,
The Properties window freezes the entire GUI while  trying to display the 
documents' list.
How could I disable the treeview for such collections ?

I have to deal with such collections because XQuery Update on many many nodes 
takes a long long time to complete,
So add/replace/delete is a good alternative.

Thank you for your continuous help and your great XNDB.

Last : is the new ADDCACHE option the way to add data near the node count limit 
without corrupting the collection ?

Best regards,
Fabrice
Questel-Orbit

___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de<mailto:BaseX-Talk@mailman.uni-konstanz.de>
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] [GUI] Properties window is frozen for a DB with a lot of documents

2013-03-26 Thread Lukas Kircher
Hi Fabrice,

we just uploaded a fix (hopefully) for this problem. The maximum number of
displayed nodes is now limited. Would be nice if you could report your
experience with the current solution, which will be contained in the next
latest stable release.

Cheers,
Lukas

On Fri, Mar 15, 2013 at 9:36 AM, Fabrice Etanchaud
wrote:

>  Dear all,
>
> ** **
>
> When dealing with collections containing more than a million documents,***
> *
>
> The Properties window freezes the entire GUI while  trying to display the
> documents’ list.
>
> How could I disable the treeview for such collections ?
>
> ** **
>
> I have to deal with such collections because XQuery Update on many many
> nodes takes a long long time to complete,
>
> So add/replace/delete is a good alternative.
>
> ** **
>
> Thank you for your continuous help and your great XNDB.
>
> ** **
>
> Last : is the new ADDCACHE option the way to add data near the node count
> limit without corrupting the collection ?
>
> ** **
>
> Best regards,
>
> Fabrice
>
> Questel-Orbit
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] [GUI] Properties window is frozen for a DB with a lot of documents

2013-03-15 Thread Fabrice Etanchaud
Dear all,

When dealing with collections containing more than a million documents,
The Properties window freezes the entire GUI while  trying to display the 
documents' list.
How could I disable the treeview for such collections ?

I have to deal with such collections because XQuery Update on many many nodes 
takes a long long time to complete,
So add/replace/delete is a good alternative.

Thank you for your continuous help and your great XNDB.

Last : is the new ADDCACHE option the way to add data near the node count limit 
without corrupting the collection ?

Best regards,
Fabrice
Questel-Orbit
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI enhancement to show only query results as text in a tree?

2013-02-22 Thread Amanda Galtman
Christian,

Thanks a lot for your reply. I'll experiment with filtering. I think the 
Options > Realtime Filtering setting may be the piece I was missing. With that 
setting enabled, I can use the folder visualization to get the tree view and 
the text visualization to see the markup plus text content.

I understand about priorities, and thanks for setting my expectations.

Regards,
Amanda


-Original Message-
From: Christian Grün [mailto:christian.gr...@gmail.com] 
Sent: Friday, February 22, 2013 5:53 AM
To: Amanda Galtman
Cc: basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] GUI enhancement to show only query results as text in 
a tree?

Hi Amanda,

thanks for your mail. We have thought about adding new visualizations to BaseX 
now and then. As our focus has more and more been shifted to database-centric 
features, I'm afraid that the introduction of new visualization will need to 
have lower priority, unless we find some open source developers who are 
interested in contributing to the project, or unless there are no commercial 
use cases that require such extensions.

If all your results are nodes of the currently opened database, you may instead 
use the filter button, which will only visualize the resulting nodes in all 
visualizations, and use XQuery or the provided buttons to do more refinements. 
However, this approach differs a little from the solutions provided in Qizx or 
oXygen.

Hope this helps,
Christian
___

On Thu, Feb 21, 2013 at 2:05 PM, Amanda Galtman  
wrote:
> Hi,
>
> The BaseX GUI is very nice for interactively tweaking a query or 
> exploring my data set. However, one thing I wish I could do with the 
> GUI is see query results as text in a tree with expandable/collapsible 
> nodes. An example of what I mean is in the right pane of this Qizx screen 
> capture:
>
> http://www.axyana.com/qizxopen/_distrib/docs/manual/qizxstudio.html#d0
> e4472
>
> The tree in the screen capture makes it easy to distinguish between 
> adjacent result items, and the collapsibility of result items makes it 
> easier to decide when you want to browse the results at a high level 
> or dig into a specific result.
>
> By contrast, the BaseX GUI's text view shows all the text of the query 
> results, but they run together. The folder visualization has 
> expandable/collapsible nodes, but because it shows the query-result 
> nodes in the context of the entire database, you might have to expand 
> a lot of nodes to discover where the query-result nodes are. While it 
> can be useful to see the query-result nodes in context, I often want 
> to see only the results themselves; and if I decide I need more 
> context, I tweak my query to return more context.
>
> Would it be possible in a future release of BaseX to get a text 
> tree-view of just the query results? Better yet, is it already 
> available but I don't know about it?
>
> Thanks,
> Amanda
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI enhancement to show only query results as text in a tree?

2013-02-22 Thread Christian Grün
Hi Amanda,

thanks for your mail. We have thought about adding new visualizations
to BaseX now and then. As our focus has more and more been shifted to
database-centric features, I’m afraid that the introduction of new
visualization will need to have lower priority, unless we find some
open source developers who are interested in contributing to the
project, or unless there are no commercial use cases that require such
extensions.

If all your results are nodes of the currently opened database, you
may instead use the filter button, which will only visualize the
resulting nodes in all visualizations, and use XQuery or the provided
buttons to do more refinements. However, this approach differs a
little from the solutions provided in Qizx or oXygen.

Hope this helps,
Christian
___

On Thu, Feb 21, 2013 at 2:05 PM, Amanda Galtman
 wrote:
> Hi,
>
> The BaseX GUI is very nice for interactively tweaking a query or exploring
> my data set. However, one thing I wish I could do with the GUI is see query
> results as text in a tree with expandable/collapsible nodes. An example of
> what I mean is in the right pane of this Qizx screen capture:
>
> http://www.axyana.com/qizxopen/_distrib/docs/manual/qizxstudio.html#d0e4472
>
> The tree in the screen capture makes it easy to distinguish between adjacent
> result items, and the collapsibility of result items makes it easier to
> decide when you want to browse the results at a high level or dig into a
> specific result.
>
> By contrast, the BaseX GUI’s text view shows all the text of the query
> results, but they run together. The folder visualization has
> expandable/collapsible nodes, but because it shows the query-result nodes in
> the context of the entire database, you might have to expand a lot of nodes
> to discover where the query-result nodes are. While it can be useful to see
> the query-result nodes in context, I often want to see only the results
> themselves; and if I decide I need more context, I tweak my query to return
> more context.
>
> Would it be possible in a future release of BaseX to get a text tree-view of
> just the query results? Better yet, is it already available but I don’t know
> about it?
>
> Thanks,
> Amanda
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] GUI enhancement to show only query results as text in a tree?

2013-02-21 Thread Amanda Galtman
Hi,

The BaseX GUI is very nice for interactively tweaking a query or exploring my 
data set. However, one thing I wish I could do with the GUI is see query 
results as text in a tree with expandable/collapsible nodes. An example of what 
I mean is in the right pane of this Qizx screen capture:
http://www.axyana.com/qizxopen/_distrib/docs/manual/qizxstudio.html#d0e4472
The tree in the screen capture makes it easy to distinguish between adjacent 
result items, and the collapsibility of result items makes it easier to decide 
when you want to browse the results at a high level or dig into a specific 
result.

By contrast, the BaseX GUI's text view shows all the text of the query results, 
but they run together. The folder visualization has expandable/collapsible 
nodes, but because it shows the query-result nodes in the context of the entire 
database, you might have to expand a lot of nodes to discover where the 
query-result nodes are. While it can be useful to see the query-result nodes in 
context, I often want to see only the results themselves; and if I decide I 
need more context, I tweak my query to return more context.

Would it be possible in a future release of BaseX to get a text tree-view of 
just the query results? Better yet, is it already available but I don't know 
about it?

Thanks,
Amanda


___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI no longer pretty-printing?

2012-04-11 Thread Christian Grün
> I'm accustomed to the GUI providing XML output in easy-to-read,
> pretty-printed form.
>
> I just upgraded to 7.2.1-pre-20120410.144517, and that behavior no longer
> appears to be the case -- documents (as displayed in the GUI) have no
> whitespace they weren't originally created with.
>
> Is this an intentional change? Is a toggle available?

Yes, this is an important issue in the current snapshot, and will be
updated soon:

  https://github.com/BaseXdb/basex/issues/479

The reason is that the serialization code has undergone some minor
changes, which have led to the deactivation of the default
indentation.

Christian
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] GUI no longer pretty-printing?

2012-04-11 Thread Charles Duffy

Howdy --

I'm accustomed to the GUI providing XML output in easy-to-read, 
pretty-printed form.


I just upgraded to 7.2.1-pre-20120410.144517, and that behavior no 
longer appears to be the case -- documents (as displayed in the GUI) 
have no whitespace they weren't originally created with.


Is this an intentional change? Is a toggle available?

___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI stops displaying results when query is too large

2012-02-22 Thread Christian Grün
Hi Andy,

thanks, that was helpful. In the latest snapshot, the updating issue
has been fixed (the views will only be updated if the data has
actually changed).

Christian
___

On Wed, Feb 22, 2012 at 12:34 PM, Andy Bunce  wrote:
> I have seen something similar, maybe it is your case:
> If I have a database open and I have an updating query in the editor or just
> referenced from an import module then when I execute the result is displayed
> for a moment then immediately replaced by the open db display.
>
> e.g.
> import module namespace state="apb.state"; (: this has an update function :)
> 2
>
> My workaround is just to work with no open db.
> /Andy
>>
>>
>> When the size of the submitted query gets too large, GUI functionality
>> stops working: Results stop being highlighted in the tree or displayed in
>> the "text" window (which instead always displays the entire document). I
>> can run the exact same XQuery file through basexclient or a REST query
>> and everything works perfectly, so this appears to be strictly a GUI
>> concern.
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI stops displaying results when query is too large

2012-02-22 Thread Andy Bunce
I have seen something similar, maybe it is your case:
If I have a database open and I have an updating query in the editor or
just referenced from an import module then when I execute the result is
displayed for a moment then immediately replaced by the open db display.

e.g.
import module namespace state="apb.state"; (: this has an update function :)
2

My workaround is just to work with no open db.
/Andy

>
> When the size of the submitted query gets too large, GUI functionality
> stops working: Results stop being highlighted in the tree or displayed in
> the "text" window (which instead always displays the entire document). I
> can run the exact same XQuery file through basexclient or a REST query
> and everything works perfectly, so this appears to be strictly a GUI
> concern.
>
>
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] gui vs. server

2012-02-13 Thread Cerstin Mahlow



OK, I got it, I somehow managed to confuse ">" and "<".

Everything is running smoothly :)
--
Dr. phil. Cerstin Mahlow

Universität Basel
Deutsches Seminar
Nadelberg 4
4051 Basel
Schweiz

Tel:  +41 61 267 07 65
Fax: +41 61 267 34 40
Mail: cerstin.mah...@unibas.ch
Web: http://www.oldphras.net


This message was sent using IMP, the Internet Messaging Program.


___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] gui vs. server

2012-02-13 Thread Cerstin Mahlow
Hi, 

when displaying search results, I would like to show more or less following and 
preceding nodes depending on the fond node name. This works fine in the GUI 
using this XQuery:

for $i at $p in //*[text() contains text ('Kopf' ftand 'Sand' ftand 
'stecken')][self::*:p or self::*:l]

let $pre := $i/preceding-sibling::*[position()<8]
let $suc := $i/following-sibling::*[position()<8]

return 
{if (string(fn:node-name($i)) = "l") then  $pre  else "P"}
{ft:mark($i [text() contains text ('Kopf' ftand 'Sand' ftand 
'stecken')]) }
{if (string(fn:node-name($i)) = "l") then  $suc else "P"}



For "l"-nodes I get preceding and following nodes, for "p" nodes the "P" will 
be printed.

However, when running the same on the server using a perl client (applying 
quoting for variables), I get the "P" for p-nodes but nothing for "l"-nodes. 
The conditional expression is correct, if I replace 

then $pre

with 

then LLL

everything works fine, "LLL" will be printed.

If I skip the condition and allow preceding and following nodes for every $i, I 
get preceding and following nodes for "p"-nodes only, but not for "l"-nodes -- 
there is simple nothing.

Is there any difference between GUI and Server? I use BaseX 7.1 beta, but I got 
the same effect with the BaseX 7.1 stable.

Best regards

Cerstin
-- 
Dr. phil. Cerstin Mahlow

Universität Basel
Deutsches Seminar
Nadelberg 4
4051 Basel
Schweiz

Tel:  +41 61 267 07 65
Fax: +41 61 267 34 40
Mail: cerstin.mah...@unibas.ch
Web: http://www.oldphras.net







___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI query editor --> revert file

2012-01-26 Thread Christian Grün
Dear Piotr,

I've processed your GitHub issue [1]: Opened files can now be reverted
in the BaseX editor. Next, an opened file will be automatically be
refreshed if the editor pane regains is focus, and if it has not been
modified. Feel free to check out the latest snapshot [2].

Best,
Christian

[1] https://github.com/BaseXdb/basex/issues/343
[2] http://docs.basex.org/wiki/Releases
___

BaseX Team
Christian Grün
Uni KN, Box 188
D-78457 Konstanz
http://www.basex.org



2012/1/24 Piotr Bański :
> Dear Christian,
>
> Somewhat belated thanks -- also for pointing me to the GitHub, I've
> managed to miss it and it appears to contain an answer to at least one
> problem I've encountered so far.
>
> Best,
>
>  Piotr
>
> On 20/01/12 01:30, Christian Grün wrote:
>> Hi Piotr,
>>
>> I've added a GitHub issue to memorize your report..
>>
>>   https://github.com/BaseXdb/basex/issues/343
>>
>> ..will probably be taken care of before the next release.
>>
>> Thanks,
>> Christian
>> ___
>>
>> On Thu, Jan 19, 2012 at 9:38 PM, Piotr Bański  wrote:
>>> Hi all,
>>>
>>> I have an feature request for the GUI editor (veeery handy for testing,
>>> thanks!): make it possible to revert files from disk. I have a file open
>>> in it that I want to update, because it got modified externally. But I
>>> can't -- not even if I open the open-file dialog and try to open it
>>> again, as if. No go, the old version sits in the editor still, and I was
>>> lucky not to overlook this fact or else I wouldn't know why it doesn't work.
>>>
>>> Thanks for considering this, and thanks for your work on BaseX,
>>>
>>>  Piotr
>>> ___
>>> BaseX-Talk mailing list
>>> BaseX-Talk@mailman.uni-konstanz.de
>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>>
>
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI query editor --> revert file

2012-01-24 Thread Piotr Bański
Dear Christian,

Somewhat belated thanks -- also for pointing me to the GitHub, I've
managed to miss it and it appears to contain an answer to at least one
problem I've encountered so far.

Best,

  Piotr

On 20/01/12 01:30, Christian Grün wrote:
> Hi Piotr,
> 
> I've added a GitHub issue to memorize your report..
> 
>   https://github.com/BaseXdb/basex/issues/343
> 
> ..will probably be taken care of before the next release.
> 
> Thanks,
> Christian
> ___
> 
> On Thu, Jan 19, 2012 at 9:38 PM, Piotr Bański  wrote:
>> Hi all,
>>
>> I have an feature request for the GUI editor (veeery handy for testing,
>> thanks!): make it possible to revert files from disk. I have a file open
>> in it that I want to update, because it got modified externally. But I
>> can't -- not even if I open the open-file dialog and try to open it
>> again, as if. No go, the old version sits in the editor still, and I was
>> lucky not to overlook this fact or else I wouldn't know why it doesn't work.
>>
>> Thanks for considering this, and thanks for your work on BaseX,
>>
>>  Piotr
>> ___
>> BaseX-Talk mailing list
>> BaseX-Talk@mailman.uni-konstanz.de
>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
> 

___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


Re: [basex-talk] GUI query editor --> revert file

2012-01-19 Thread Christian Grün
Hi Piotr,

I've added a GitHub issue to memorize your report..

  https://github.com/BaseXdb/basex/issues/343

..will probably be taken care of before the next release.

Thanks,
Christian
___

On Thu, Jan 19, 2012 at 9:38 PM, Piotr Bański  wrote:
> Hi all,
>
> I have an feature request for the GUI editor (veeery handy for testing,
> thanks!): make it possible to revert files from disk. I have a file open
> in it that I want to update, because it got modified externally. But I
> can't -- not even if I open the open-file dialog and try to open it
> again, as if. No go, the old version sits in the editor still, and I was
> lucky not to overlook this fact or else I wouldn't know why it doesn't work.
>
> Thanks for considering this, and thanks for your work on BaseX,
>
>  Piotr
> ___
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk


[basex-talk] GUI query editor --> revert file

2012-01-19 Thread Piotr Bański
Hi all,

I have an feature request for the GUI editor (veeery handy for testing,
thanks!): make it possible to revert files from disk. I have a file open
in it that I want to update, because it got modified externally. But I
can't -- not even if I open the open-file dialog and try to open it
again, as if. No go, the old version sits in the editor still, and I was
lucky not to overlook this fact or else I wouldn't know why it doesn't work.

Thanks for considering this, and thanks for your work on BaseX,

  Piotr
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk