Are you getting data and money from Google analytics and advertising respectively?
Does the Google JavaScript even work on gpsd.io?
A very brief check suggests that "Dark Reader" makes a few pages less readable.
I will work on getting my changes here to be less bloated and ugly.
They are not fit to be merged now, I need to portion them better.
Reverted the label text changes except for the search string label which I wrapped around the icon.
I didn't use the simpler syntax then because I am stupid.
what to search for
Seems condescending to me. None of the new label text feels right to me.
<input id="gs_query" type="text" name="q" size="31"
Why the new id's?
Why not the simpler:
<label>
all the web
<input type="radio" name="sitesearch" value="">
/label>And one MR more to correct the "hansdfree" typo, right?
Could have put it in the pterformance MR, They are both typo fixes, but too late now.
Gary E. Miller (f9512dc7) at 03 Oct 21:06
www: Fix index/FAQ links to 'performance' page.
This has been clipped to the performance link update and rebased.
And one MR more to correct the "hansdfree" typo, right?
This should be two MRs. One for the link fixes, the other for the google search changes.
I don't know enough about dbus to do something like that. If there was an app publishing NMEA to dbus then it might not be too hard for gpsd to use it. Might be easier to write a standalone app that reads NMEA off dbus and sends it to gpsd.
Do you have doc on what is published to dbus from this app?
When projects like this fail it is usually due to bad doc, or badly formatted data. So let's be sure we have that first.
Gary E. Miller (96a1f175) at 03 Oct 03:12
gpsd/packet.c: All TAB and CR in comments.
... and 1 more commit
when leaving out the -D argument on the (slave) gpsd
-D makes gpsd run way slower. So prolly a timing issue. But there could be a crash bug in one of the log calls.
Ditto for cgps vs. gpspipe. cgps puts a larger load on the system.
Another problem I currently face is that the raw capture file contains the password from the NTRIP uri.
Apply sed, or your fave editor, or send to me privately. Size does matter. I though the recent patch fixed that.
@garyedmundsmiller I just found out - by coincidence - that when leaving out the -D<number> argument on the (slave) gpsd the problem doesn't trigger. Also to problem does not seem to trigger when only gpspipe is used. So it triggers when cgps is connecting to the GPSD as only client but not when both cgps and gpspipe are connected to the gpsd.
Another problem I currently face is that the raw capture file contains the password from the NTRIP uri. How can I best remove that? I could do a binary replace on that string and replace it with a filler string of the same size?
Gary E. Miller (3232f841) at 01 Oct 03:35
gps/ubx.py: Add UBX-RXM-SPARTN decode and enable.
Gary E. Miller (b5a699cc) at 30 Sep 03:10
gps/ubx.py: add "-p MON-COMMS", add partial decode RXM-SPARTNKEYS.
I thought there were some technical reasons for that,
The fact that very could use it would be a valid technical reason. But if it helps you, go for it.
I would suggest you make an early MR, so we can maybe prevent you from going off in a bad direction.
at least for u-blox driver's SHM export,
Many, many, layers between UBX decode and SHM. JSON support will also be required for a successful MR. And both server and client support, plus doc.