Software to Introduce Hypertext Links in OpenCPN Waypoints

[HappySeagull]

Great,Nohal!...It'd be great to just open one dialogue to see links,write descriptions,(and it looks like I'll be able to have more than a single long line in the description box!) etc....but where will the icon choice be?

Is there a way to have TABS in the waypoint/mark dialogue?

[HappySeagull]

Robert,is there a way MarinePOI could preserve OpenCPN's waypoint Description" field?Presently,it wipes it out .
From the gpx...
<desc>blah blah blah blah a single long line because there&apos;s no way I can enter a second line and SEE IT!
enter a second line and SEEE it!</desc>

If anybody's wondering,the above is an illustration resulting from using the RETURN key in Opcn's description dialogue.Topical,considering the "&amp"

[nohal]

Happy...
Yes, unifying the two dialogs and making everything editable inside opencpn is my longer term plan. But I first want to have a look at some under the hood stuff to make it worth doing.

Pavel

[Robert_1]

Originally Posted by HappySeagull

Robert,is there a way MarinePOI could preserve OpenCPN's waypoint Description" field?Presently,it wipes it out .
From the gpx...

Yes, it is an easy change to make in Marine Poi. But I need a real gpx sample file.

[sinbad7]

Robert..

Here is a .gps test file of OCPN 'Waypoints Description'

Tore

[HappySeagull]

Sinbad beat me to it but here,anyways..
HappySeagullwithDescriptionGone.gpx

HappySeagullwithDescription.gpx

[Robert_1]

Originally Posted by HappySeagull

Sinbad beat me to it but here,anyways..

You may test this one (version 1_2j) : http://upload.plaisance-pratique.com...-MarinePoi.zip
Unzip, and replace in "program files/marinepoi/".

Descriptions are saved now.

If MarinePoi is run with GoogleEarth, I made a spécial arrangement : description and WP name are read by GoogleEarth too.

Carriage-return and line feed work properly. I attached 2 pictures.

[Robert_1]

Originally Posted by nohal

As I wrote in flyspray: a GPX file containing & not encoded as &amp; is broken, not valid XML and should be refused as such.

We must be realistic: even if the standard rejects "&", if billions of links are using "&" (Even Google !) , and all web browsers read them properly, it makes no sense that OpenCPN attempts to deny this reality ... OpenCPN will die before he won ...

[nohal]

Robert...
Could you please send me a GPX file produced by Google Earth (or another Google product), which is malformed XML? I have never seen one and as far as i know, GE does not export GPX at all, so I can't create such a file myself.

Please keep on mind, that the contents of the GPX file have absolutely nothing to do with the link that is sent to the browser.

Pavel

[Robert_1]

Originally Posted by nohal

Robert...
Please keep on mind, that the contents of the GPX file have absolutely nothing to do with the link that is sent to the browser.Pavel

Yes, Nohal, I am speaking about links, not about gpx files. From a practical point of view, someone using OpenCPN must have the possibility to introduce in the gpx file the links as he found them on the web, containing "&" or "&amp;" without manual processing

Therfore, MarinePoi translates "&" into "&amp;" to be consistant with the standard.

For exemple, a link from the Web :

ww.stw.fr/marina_stw/voir_evaluation.cfm?marina_id=1027&period=0&ll=%28 46.227638,%202.213749%29

And the link written by MarinePoi in the gpx file:

<link href="http://www.stw.fr/marina_stw/voir_evaluation.cfm?marina_id=1027&amp;period=0&am p;ll=%2846.227638,%202.213749%29">

Now, remenber Dave in Flyspay :FS#667 : Waypoint with "&" or "&amp;" in "additional informations" links

"Worse, if we use "&amp" in navobj, for instance, then this gets converted to "&" on the next OCPN close, and then lost forever on the next open/parse.
That is, tinyxml cannot do a read-write-read "round trip" on "&" or "&amp".

Maybe I missed something ?

Robert.

[nohal]

Robert,
then consider it solved, nothing like this actually happens...
TinyXML itself "eats" the '&' characters just in the malformed GPX files, not when they are encoded as '&amp;'. This is the penalty for being a non-validating parser - it's lightning fast, but of course at some price.
Even in case the file is malformed, and we actually should refuse to load, there's now logic to *try* to correct it in https://github.com/nohal/OpenCPN/tree/links_scrollable

Pavel

[HappySeagull]

Thank you,Robert!
Comments in the "Description" field are now preserved!...I find OpenCPN's "Description" Field" useful,because it doesn't take up the whole screen to write it or read it when navigating.

Nohal,
If you are still here?All this about "Description" is a little confusing...more so in O's Mark GUI...so if you are steering your GlowingGreyMatter towards a rebuild.....?

[boraxtr]

Rebert,
The links at WayPoints over 6 can nat be seen at the fly. Is there any possibility to display over than 6 links and even adjustable fly?

[Robert_1]

Originally Posted by boraxtr

Rebert,
The links at WayPoints over 6 can nat be seen at the fly. Is there any possibility to display over than 6 links and even adjustable fly?

OpenCPN v2.5 cannot display more than 6 links for each waypoint !

[yoruk]

Originally Posted by Robert_1

OpenCPN v2.5 cannot display more than 6 links for each waypoint !

Please pavel... open the window...

Michel