Hi Andreas, hi everyone,
Since XQDT works under Eclipse 3.7 and offers parentheses matching [...]
that's an important point of course. I would generally interested what tools you (all) prefer to develop applications with BaseX, XQuery and XML.
As you may know, the embedded BaseX editor can be used to process XQuery, XML and any other types of text documents. It know various powerful hotkeys [1] that are not documented in the GUI. It provides direct feedback on parsing errors in the edited and imported modules. The latest snapshot [2] also parses XML documents and command scripts and, since this weekend, offers a much more powerful facility for incrementally searching and replacing strings (incl. support for regular expressions).
Enough of the self-adulation… We're well aware that it would be a waste of time if we seriously tried to cope with existing text editors and IDEs, such as..
• Eclipse w/XQDT • oXygen • vim, Emacs, etc.
..so we’d like to know what are your favorite editors for writing XQuery expressions and applications, and what convinces, or deters you, mostly from using the built-in editor or the alternatives?
Thanks in advance for your opinion, Christian
[1] http://docs.basex.org/wiki/Shortcuts#Editor_Shortcuts [2] http://files.basex.org/releases/latest/
Hi,
Personally, I use oXygen for all my XML-related work, for all its integration mechanism, switching on a regular basis to Emacs when it comes to intensively editing files...
When I have to do anything specific to BaseX, the built-in editor is very good and provides everything at hand!
Regards,
Hi,
I prefer oXygen, as well. The WebDAV integration is ok for working with the data and to edit XQuery modules that are stored in the db.
The execution of XQuery is a different topic: oXygen uses Saxon for XQuery execution/debugging which helps for the general cases. But everything specific to BaseX isn't available, of course.
In the end, I tend to use the BaseX REST interface to get BaseX error handling. Since I am using BaseX, eXist-db and Saxon, I try to avoid any vendor specific tools.
Regards,
Max
2012/9/25 Florent Georges lists@fgeorges.org:
Hi,
Personally, I use oXygen for all my XML-related work, for all its integration mechanism, switching on a regular basis to Emacs when it comes to intensively editing files...
When I have to do anything specific to BaseX, the built-in editor is very good and provides everything at hand!
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
----- Mail original -----
De : Christian Grün christian.gruen@gmail.com À : BaseX basex-talk@mailman.uni-konstanz.de Cc : Andreas Rulle andreas.rulle@nexoma.de Envoyé le : Mardi 25 septembre 2012 13h49 Objet : [basex-talk] (How to) build application with BaseX
Hi Andreas, hi everyone,
Since XQDT works under Eclipse 3.7 and offers parentheses matching [...]
that's an important point of course. I would generally interested what tools you (all) prefer to develop applications with BaseX, XQuery and XML.
As you may know, the embedded BaseX editor can be used to process XQuery, XML and any other types of text documents. It know various powerful hotkeys [1] that are not documented in the GUI. It provides direct feedback on parsing errors in the edited and imported modules. The latest snapshot [2] also parses XML documents and command scripts and, since this weekend, offers a much more powerful facility for incrementally searching and replacing strings (incl. support for regular expressions).
Enough of the self-adulation… We're well aware that it would be a waste of time if we seriously tried to cope with existing text editors and IDEs, such as..
• Eclipse w/XQDT • oXygen • vim, Emacs, etc.
..so we’d like to know what are your favorite editors for writing XQuery expressions and applications, and what convinces, or deters you, mostly from using the built-in editor or the alternatives?
Thanks in advance for your opinion, Christian
[1] http://docs.basex.org/wiki/Shortcuts#Editor_Shortcuts [2] 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
Maximilian Gärber wrote:
Hi,
The execution of XQuery is a different topic: oXygen uses Saxon for XQuery execution/debugging which helps for the general cases. But everything specific to BaseX isn't available, of course.
That's true, but I wouldn't say "of course". If you'd like to use your copy of oXygen with BaseX, I am sure the oXygen team would like to know about that. And if anyone if willing to help drafting an implementation, I am sure they would listen ;-) I am sure writing an email to the oXygen list to ask if they have such a plan is worth spending the time.
I wrote once a set of XProc steps to evaluate XQuery on BaseX. So technically, you could even write a small XProc pipeline using them and associate a scenario to your XQuery to be the input of this pipeline. Just a thought... (honestly, I don't even remember where are those steps, but you should find them by googling for "basex calabash").
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
Thanks, Florent, mails to the oXygen list are always welcome.
Christian ___________________________
On Tue, Sep 25, 2012 at 6:59 PM, Florent Georges lists@fgeorges.org wrote:
Maximilian Gärber wrote:
Hi,
The execution of XQuery is a different topic: oXygen uses Saxon for XQuery execution/debugging which helps for the general cases. But everything specific to BaseX isn't available, of course.
That's true, but I wouldn't say "of course". If you'd like to use your copy of oXygen with BaseX, I am sure the oXygen team would like to know about that. And if anyone if willing to help drafting an implementation, I am sure they would listen ;-) I am sure writing an email to the oXygen list to ask if they have such a plan is worth spending the time.
I wrote once a set of XProc steps to evaluate XQuery on BaseX. So technically, you could even write a small XProc pipeline using them and associate a scenario to your XQuery to be the input of this pipeline. Just a thought... (honestly, I don't even remember where are those steps, but you should find them by googling for "basex calabash").
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
Hi Max,
thanks for your feedback. Btw, with oXygen it’s also possible to choose BaseX as XQuery processor. This can e.g. be done as described here:
http://docs.basex.org/wiki/Integrating_oXygen#Perform_Queries
Hope this helps, Christian ___________________________
On Tue, Sep 25, 2012 at 3:29 PM, Maximilian Gärber gaerber@axxepta.de wrote:
Hi,
I prefer oXygen, as well. The WebDAV integration is ok for working with the data and to edit XQuery modules that are stored in the db.
The execution of XQuery is a different topic: oXygen uses Saxon for XQuery execution/debugging which helps for the general cases. But everything specific to BaseX isn't available, of course.
In the end, I tend to use the BaseX REST interface to get BaseX error handling. Since I am using BaseX, eXist-db and Saxon, I try to avoid any vendor specific tools.
Regards,
Max
2012/9/25 Florent Georges lists@fgeorges.org:
Hi,
Personally, I use oXygen for all my XML-related work, for all its integration mechanism, switching on a regular basis to Emacs when it comes to intensively editing files...
When I have to do anything specific to BaseX, the built-in editor is very good and provides everything at hand!
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
----- Mail original -----
De : Christian Grün christian.gruen@gmail.com À : BaseX basex-talk@mailman.uni-konstanz.de Cc : Andreas Rulle andreas.rulle@nexoma.de Envoyé le : Mardi 25 septembre 2012 13h49 Objet : [basex-talk] (How to) build application with BaseX
Hi Andreas, hi everyone,
Since XQDT works under Eclipse 3.7 and offers parentheses matching [...]
that's an important point of course. I would generally interested what tools you (all) prefer to develop applications with BaseX, XQuery and XML.
As you may know, the embedded BaseX editor can be used to process XQuery, XML and any other types of text documents. It know various powerful hotkeys [1] that are not documented in the GUI. It provides direct feedback on parsing errors in the edited and imported modules. The latest snapshot [2] also parses XML documents and command scripts and, since this weekend, offers a much more powerful facility for incrementally searching and replacing strings (incl. support for regular expressions).
Enough of the self-adulation… We're well aware that it would be a waste of time if we seriously tried to cope with existing text editors and IDEs, such as..
• Eclipse w/XQDT • oXygen • vim, Emacs, etc.
..so we’d like to know what are your favorite editors for writing XQuery expressions and applications, and what convinces, or deters you, mostly from using the built-in editor or the alternatives?
Thanks in advance for your opinion, Christian
[1] http://docs.basex.org/wiki/Shortcuts#Editor_Shortcuts [2] 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
--
Maximilian Gärber
axxepta solutions GmbH Postfach 51 02 38 13362 Berlin
Tel +49 (0)30 499 147 66 Fax +49 (0)30 499 147 67 Mail gaerber@axxepta.de _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
When testing the script during the development against a sample database with BasexGUI this is manually changed into:
(: declare variable $dbName external; :) declare variable $dbName := 'll_i_one';
There may be various solutions for that problem:
1) You can specify a default value in the variable declaration:
declare variable $dbName external := 'll_i_one';
2) You can write a command script (e.g., commands.bxs) and run it with the GUI (works since 7.5):
<commands> <set option='bindings'>dbName=123</set> <xquery> declare variable $dbName external; $dbName </xquery> </commands>
3) With versions prior to 7.5, you can first use the command input to set your external variables (using "set dbName=123") and then run the query.
Thanks for your feedback, Christian
basex-talk@mailman.uni-konstanz.de