Some GUI suggestions
Wednesday, 26 October 2016 · 6 messages · last reply 27 Oct 2016
AB
Andy Bunce26 Oct 2016 13:14 #
Hi,
Here are some suggestions for future GUI enhancements:
Project window:
* Add recent locations button, similar to the editor (recent files)
Editor window:
* use scrollable run of tabs rather than multi row see [1]. Ideally with dropdownlist to select any item as with Eclipse, Firefox etc.
* more tab close options. E.g "close all", "close others"
Query info window
Very useful but typically, at any one time, I am only interested in a particular section from: Compiling,Optimized
Query,Query,Result,Timing,Query plan.
Maybe checkbox config for which are shown or links to sections or tabs for sections
Map/tree/folder windows
All these views are rooted at a document. There are times when I would like a collection based root here, as shown on database>properties>resources
Cheers
/Andy
[1]
http://docs.oracle.com/javase/7/docs/technotes/guides/swing/1.4/tabbedPane.html
CG
Christian Grün26 Oct 2016 16:07 #
Hi Andy,
Thanks for the feature requests, some of which seem easy to realize; I’ll have a look soon.
Quoted text · Andy Bunce · 1 line
> * more tab close options. E.g "close all", "close others"
This may not be the most elegant option, but you can usually press down Ctrl-W until all tabs are closed.
Cheers,
Christian
CG
Hi Graydon,
Quoted text · Graydon Saunders · 3 lines
> Configurable "dump the output to a file" (rather than using file:write in > the query) would be nice, too; development is not always at a place where > file:write is straightforward.
One existing solution is to press the "Save" button in the Text View once the query has been evaluated. If the result is small enough, the text will be saved as is. Otherwise, the query will be re-evaluated, and the result ends up in the specified file.
Hope this helps,
Christian
GS
Named, saveable, and loadable sets of external variables defined under the $x button of the Editor window would be nice.
Configurable "dump the output to a file" (rather than using
file:write in the query) would be nice, too; development is not always at a place where file:write is straightforward.
-- GraydonQuoted text · Andy Bunce · 33 lines
On Wed, Oct 26, 2016 at 7:14 AM, Andy Bunce <bunce.andy at gmail.com> wrote: > Hi, > > Here are some suggestions for future GUI enhancements: > > Project window: > * Add recent locations button, similar to the editor (recent files) > > Editor window: > * use scrollable run of tabs rather than multi row see [1]. Ideally with > dropdownlist to select any item as with Eclipse, Firefox etc. > * more tab close options. E.g "close all", "close others" > > Query info window > Very useful but typically, at any one time, I am only interested in a > particular section from: Compiling,Optimized Query,Query,Result,Timing,Query > plan. > Maybe checkbox config for which are shown or links to sections or tabs > for sections > > Map/tree/folder windows > All these views are rooted at a document. There are times when I would > like a collection based root here, as shown on database>properties>resources > > Cheers > /Andy > > [1] http://docs.oracle.com/javase/7/docs/technotes/guides/swing/ > 1.4/tabbedPane.html > > > >
GS
Hi Christian --
That's certainly true and it's useful. I am more looking for a configurable file target so I don't have to have the very early stages of "what is going on in there?" organized enough for a
file:write or to find the large set of results twice each time.
This is much less interesting to me than the named, loadable list of external variables; that would make life easier to various semi-technical folks I'm delivering queries to.
Thanks!
GraydonQuoted text · Christian Grün · 16 lines
On Wed, Oct 26, 2016 at 10:08 AM, Christian Grün <christian.gruen at gmail.com> wrote: > Hi Graydon, > > > Configurable "dump the output to a file" (rather than using file:write in > > the query) would be nice, too; development is not always at a place where > > file:write is straightforward. > > One existing solution is to press the "Save" button in the Text View > once the query has been evaluated. If the result is small enough, the > text will be saved as is. Otherwise, the query will be re-evaluated, > and the result ends up in the specified file. > > Hope this helps, > Christian >
CG
Christian Grün27 Oct 2016 10:35 #
I have created an issue to keep track of your suggestions [1]. Implementors out there: Get back to us :)
[1] https://github.com/BaseXdb/basex/issues/1378
Quoted text · Graydon Saunders · 35 lines
On Wed, Oct 26, 2016 at 5:00 PM, Graydon Saunders <graydonish at gmail.com> wrote: > Hi Christian -- > > That's certainly true and it's useful. I am more looking for a configurable > file target so I don't have to have the very early stages of "what is going > on in there?" organized enough for a file:write or to find the large set of > results twice each time. > > This is much less interesting to me than the named, loadable list of > external variables; that would make life easier to various semi-technical > folks I'm delivering queries to. > > Thanks! > Graydon > > On Wed, Oct 26, 2016 at 10:08 AM, Christian Grün <christian.gruen at gmail.com> > wrote: >> >> Hi Graydon, >> >> > Configurable "dump the output to a file" (rather than using file:write >> > in >> > the query) would be nice, too; development is not always at a place >> > where >> > file:write is straightforward. >> >> One existing solution is to press the "Save" button in the Text View >> once the query has been evaluated. If the result is small enough, the >> text will be saved as is. Otherwise, the query will be re-evaluated, >> and the result ends up in the specified file. >> >> Hope this helps, >> Christian > >
Written for BaseX 8.5. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery