steve8x8
commented
7 years ago There's a patch in my "work in progress" space - which I'm trying to test myself before going public (i.e. attaching it here). I'm not fully convinced yet... and would like to avoid multiple updates.
- Only gpx-cgeo will be affected for a start. (SInce this is done by extending the evaluation rules for
<%...%>stuff in the templates, you may forge your own template for whichever online-capable device.) - Links should be clickable, of course. Should I add the "href" value? (I think so. It had been in the output all the time. Wrap it into
[= ... =].) - What about images? What happens if c:geo finds an
element in GPX input? Will it load the image at import time? Will it ignore it? Will it try to load it from the 'net each time one opens the cache description page? More tests are necessary. For now, images are replaced by links wrapped in
[* ... *], click them or leave them... - Android has to be configured to open coord.info links in c:geo itself, and use a browser for everything else (you may even want to use a different browser for checker purposes...)
Any comments?
Currrently (3.25.5), all output formats pretend that the GPS device isn't online-capable. Therefore, ... hyperlinks are reformatted. (The same is true for![]()
but this might result in increased data traffic when opening a cache description - something I consider undesirable.)
An app with internet connection could profit from "live" hyperlinks, e.g. for geochecker access.
If the link text consists of real text, that should be shown as is (e.g. no replacements at all). If the link "text" is an image (including for example, the geochecker stats) it should be "masked". Cache-related images have to be retrieved by other means - the final option being a "reload" of the cache inside the app.