While clicking on URI in a PDF document, generated from HTML document, I got an error window *Triggering URI not implemented" which triggered an idea for eaglemode use case.
How cool would it be, if you could use URI to local paths, and when clicking on such a link, eaglemode would fly there! This would allow you creating complex visiting sequences, among available paths on your local computer, within a single document. Somehow I liked this idea much and wanted to share it quickly here.
I hope for next eaglemode 0.96.2 update. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
URIs (or say URLs) which start with http:// or https:// are supported now since version 0.96.2. They open a web browser as usual. In addition, special URIs of the form eaglemode:<panel identity> are supported. For example, eaglemode:::Clock1: points to the clock, and eaglemode:::FS::::usr::src: points to the /usr/src directory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While clicking on URI in a PDF document, generated from HTML document, I got an error window *Triggering URI not implemented" which triggered an idea for eaglemode use case.
How cool would it be, if you could use URI to local paths, and when clicking on such a link, eaglemode would fly there! This would allow you creating complex visiting sequences, among available paths on your local computer, within a single document. Somehow I liked this idea much and wanted to share it quickly here.
I hope for next eaglemode 0.96.2 update. :)
URIs (or say URLs) which start with
http://orhttps://are supported now since version 0.96.2. They open a web browser as usual. In addition, special URIs of the formeaglemode:<panel identity>are supported. For example,eaglemode:::Clock1:points to the clock, andeaglemode:::FS::::usr::src:points to the /usr/src directory.