Does anyone know of a way (or available plugin) that would open a context-specific (a.k.a. cell-specific) formatted information window (using YAD or zenity) to provide guidance related to the topic listed in the specified cell?
I’m already aware that I could add a hyperlink, which would force me to store the Guidance docs as distinct web pages available from GitHub, but I would rather have that guidance somehow embedded in a single companion document that is parsed by the “click-function” of what will likely be a macro calling an external function or an embedded bash script. I did a quick test with the mouse-over “Comment” function, but that just doesn’t cut it for the reason that I can’t format the contents.
I’m NOT an expert with either Zenity or Yad, yet in spite of that, I’ve taken work that OTHERS have done, grabbed their code, modified the parts I wanted to use, and thus I’ve written several really simple, functional, quick interfaces for various tools. Examples I’ve written from the code I extracted include clocks, system and package updating via a simple graphical interface and test tools for one of my favorite distributions.
I am less concerned with the Zenity/YAD aspect, as I am with identifying the proper functionality (macro/function) within LibreOffice that will allow me to call that external function which will react to the click-on-box to
extract the context “label” from the box,
then extract the appropriate guidance segment,
then present the guidance in a pop-up window using the Zenity/YAD
After further research and consideratoin, I am making a hard pivot, away from using LibreOffice as my documentation “launchpad”, to using straight HTML with CSS/JavaScript.
Using the “Save As” HTML calc.
(EDIT: continuing after rushing off due to Tornado warning and hail!)
The HTML generated is single HTML page with each individual sheet generated as a separately reference section with its own URL tag and an index list at the top of the page pointing to each of the sheets.
That will give me a good start, preserving the work I already did, but I will “massage” that into proper “modern” tags which are DIV-based.
Given this new approach, the resulting document could be monolithic, but the capabilities dictate using separate distinct files for each “sheet” and each cell-driven guidance.
So, the plan is to build the resulting “demo” with the necessary templates for the Outgoing packets under the PREROUTING/OUTPUT chain/table combination … then get feedback on that approach before continuing with the rest of the overall “project”. TTFN!
)