If you are allowed to include macros, there should be a way to use some VBA scripting for providing a launcher for Oxygen... but you don’t want to ask me about VBA :-)

Over here we run a self-built NodeJS-webapp, where we can display an “Open in Oxygen” button next to the message.

Von: Eliot Kimber <eliot.kimber@servicenow.com>
Gesendet: Donnerstag, 22. Dezember 2022 15:01
An: Zimmel, Daniel <D.Zimmel@ESVmedien.de>; basex-talk@mailman.uni-konstanz.de
Betreff: Re: Possible to get line number of node?

Interesting—I did not know Oxygen provided this option.

I’m wondering what I could put in an Excel spreadsheet that would make this work on a user’s machine…

Cheers,

_____________________________________________

Eliot Kimber

Sr Staff Content Engineer

O: 512 554 9368

M: 512 554 9368

servicenow.com

LinkedIn | Twitter | YouTube | Facebook

From: Zimmel, Daniel <D.Zimmel@ESVmedien.de>
Date: Thursday, December 22, 2022 at 4:21 AM
To: Eliot Kimber <eliot.kimber@servicenow.com>, basex-talk@mailman.uni-konstanz.de <basex-talk@mailman.uni-konstanz.de>
Subject: AW: Possible to get line number of node?

[External Email]

I can’t answer anything helpful for the reliability of line numbers, but can tell you how we are doing this in a similar use case:

we make use of what Oxygen calls “simplified XPath index path” (https://www.oxygenxml.com/doc/versions/25.0/ug-editor/topics/opening-document-from-cli.html)

Roughly:

* we write out that path (“#element(1/2/6/15)”) to a Schematron diagnostics element

* in our frontend to Schemaron we generate a button which will take you directly to Oxygen

So, if you don’t have to care about other editors than Oxygen, this might be a simple and reliable way. At least to us, works like a charm.

Best, Daniel

Von: BaseX-Talk <basex-talk-bounces@mailman.uni-konstanz.de> Im Auftrag von Eliot Kimber
Gesendet: Mittwoch, 21. Dezember 2022 23:14
An: basex-talk@mailman.uni-konstanz.de
Betreff: [basex-talk] Possible to get line number of node?

I’m pretty sure the answer is “no”, but is there any way from BaseX 9.6 to get the source line number a given node starts on?

My use case is I’m looking for specific elements and making a report of documents that contain them and identifying information about the elements to help with finding them outside of BaseX (i.e., in Oxygen where the authoring happens). I’m parsing with the “trim whitespace” option turned off and I’m not doing any DTD-aware parsing, so the elements as loaded into the database will match the source (no additional attributes or anything). So at least in theory BaseX could maintain accurate line numbers.

These elements don’t have @id attributes so no natural way to identify them, so it would be useful to be able to report the source line number as a guide to people fixing these elements.

I didn’t see anything in the docs so I thought I’d ask just in case I’ve missed some trick.