AvNav - navigation in the browser

[sparticle]

Originally Posted by mgrouch

BBN Marine OS is another one for raspberry pi4 which has AvNav preinstalled:

https://github.com/bareboat-necessit...ag/v2022-10-01

Fair Winds!

Please stop plugging BBN Marine OS! If you want to plug that then start a new top level sub forum!

I am not interested in all the bloat that comes with it.

Spart

[mgrouch]

Originally Posted by sparticle

Please stop plugging BBN Marine OS! If you want to plug that then start a new top level sub forum!



I am not interested in all the bloat that comes with it.



Spart

It’s designed for offshore and live aboard sailors. So it has more programs than YOU need. Are you a moderator of this forum?

Thanks

[BlackSea]

So it has more programs than YOU need.

exactly. you are right. it is not necessary to use/advertise a distro in which only 10% maybe is used.
[offtopic]

in my opinion, everything that is not really needed (facebook, youtube, spotify etc) should be gone and optionally installable
[/offtopic]

[mgrouch]

Originally Posted by BlackSea

exactly. you are right. it is not necessary to use/advertise a distro in which only 10% maybe is used.
[offtopic]

in my opinion, everything that is not really needed (facebook, youtube, spotify etc) should be gone and optionally installable
[/offtopic]

Installable from where? If you are limited on internet traffic such as people living aboard or offshore they need it on SD card. In that case why make them waste time and install it instead of giving installed. These programs are not using resources if they are not started (except of disk space).

So I totally disagree with your point of view.

You have a way to customize the whole image process and build your own on CircleCi by forking and removing parts of the scripts. Not hard to do. It’s open source.

[BlackSea]

for me is enough to maintain AvNav Headless Image with all repos for AvNav&Openplotter ( that you consume also)


Greetings
BlackSea aka free-x@github

[mgrouch]

Originally Posted by BlackSea

for me is enough to maintain AvNav Headless Image with all repos for AvNav&Openplotter ( that you consume also)


Greetings
BlackSea aka free-x@github

For YOU. There are other people with other use cases. Just AvNav alone on pi is a bit low on value compared to a tablet with chartplotter.
Pi is really bringing value in integrating sensors and ability to run DIY autopilot (pypilot) as addition to chart plotting. Weather access is important too as power monitoring. On board music is also useful feature.

BBN OS doesn’t contain any openplotter code,
and doesn’t include openplotter as it’s not needed with it.

[BlackSea]

Just AvNav on pi is a bit low on value compared to a tablet with chartplotter.
Pi is really bringing value in integrating

AvNav can more than you think. if you have implemented only a fraction of possibilities in your distro, do not allow to talk so deprecatingly about AvNav

Pi is really bringing value in integrating sensors

AvNav can

ability to run DIY autopilot (pypilot)

AvNav can send RMB/APB, that pypilot understands

Weather access is important

agree...is not yet implemented

power monitoring

see below (sensors)

On board music is also useful feature.

completely overrated



P.S. I'm using AvNav at Pi3B

[mgrouch]

Originally Posted by BlackSea

AvNav can more than you think. if you have implemented only a fraction of possibilities in your distro, do not allow to talk so deprecatingly about AvNav


AvNav can


AvNav can send RMB/APB, that pypilot understands
agree...is not yet implemented
see below (sensors)

completely overrated



P.S. I'm using AvNav at Pi3B

Not sure how you can know what I think.

Suggest what is missing in the distro in AvNav functionality. There is issue tracking here:

https://github.com/bareboat-necessit...ine_gen/issues

I care about AvNav being better and improving
that’s why I report issues to AvNav. Not even sure what you talking about ‘deprecating’.
Submit concrete issues to contribute if you have any issues.


AvNav can’t drive autopilot motor controller.
It can’t be autopilot. Talking to some other autopilot is not same.

I see you are not big music fan.

[ekoleponen]

Hello,

putting musical differencies aside I have a question regarding the Keyboard shortcuts/keys.json.

My HW: RPi4 2G, OP3 64bit

Regarding "zoomIn" and zoomOut the default setting allegedly is:

"zoomIn":["+","PageUp"],
"zoomOut":["-","PageDown"],

(from https://github.com/wellenvogel/avnav...atic/keys.json)

My goal is to drop out "PageUp" and "PageDown" keys from zooming.

So I copied the content of the "github.com.../static/keys.json" to keys.json using the UI of AvNav and dropped "PageUp" and "PageDown (and the brackets):

"zoomIn":"+",
"zoomOut":"-",

Saved, restarted AvNav and to my surprise PageUp- and PageDown-keys were still fully functional zooming in and out.
Then I added e-key to zoomIn:

"zoomIn":["+", "e"],
"zoomOut":"-",

Saved, restarted AvNav and PageUp- and PageDown-keys were zooming in and out,
but also the key-e also zooms in (as was ecpected).

I understood that the setting in "github.com---/static/keys.json" is the builtin setting, but the document also states "keys.json in the user directory overwrites the defaults".

So it seems that the user defined keys are only appended to the default keys.

Is there a way to get rid of the default settings?
Or is my conclusion totally wrong??

with best regards,
eko

[wellenvogel02]

Did you reload the page in the browser?
The server part is out of the game...
Maybe you could just attach your keys.json so I could have a look.

[ekoleponen]

Yes, I reloaded succesfully as the e-key zoomsIn succesfully.

keys.json is attached.

[wellenvogel02]

Ok, will have a look.

[wellenvogel02]

Ok, currently it works a bit different then you may expect...
When looking for a mapping this is done somehow "reverse" - so when you press a key it looks for an entry just with the key on the page you are currently on (or at "all").
This starts with your user keys and continues with the system defined ones.
So what happens:
It does not find a mapping for "PageUp" in your user keys and therefore falls back to the system defined one.
So currently you would need to assign PageUp to some different (although existing) action to remove it from the map handling.
Hmm - maybe not that straight forward as it should be.
Could you maybe open an issue on GitHub to describe your problem - I guess there should be an easy solution for it.
A fast fix would be to have some "unused" action on every page that you could assign keys to for "hiding" a key mapping from the system defined one.
But I guess it should work more like the way you tried it.

[ekoleponen]

Ok, big thanks for clarifying the shortcut-logic !

I think I will handle the problem by changing keycode-keysym mapping.
I am putting together an AvNav-tablet using old computer-stuff (display is no touch-screen), so by using the numeric-keypad I can map the keys to generate whatever keysym I need.

One question still to be sure:
Are the usable functions for kb-shortcuts those listed in the document starting on page 174.
The document is dated 4/21/22, 2:54 PM.

For example, there is no way to make a shortcut for the "Measure"-function on the "navpage"-page ?

[wellenvogel02]

I have just been working on a solution. On my test system it already works...
Just waiting for the GitHub issue ;-).

Not sure what you are looking for.
Actions for buttons are generic - just look for the Button name in the docs (or just use the Web developer tools in the browser to find it at the button element).
One drawback today: Buttons are only working as long as they are visible (i.e. when auto hiding them or when they are in the second row the shortcuts will also not work).
Changing this seems to be slightly bigger effort as it is not that generic any more.