Replies: 1 comment 2 replies
-
There is no I don't know if the WPASupplicant code can be used on the OpenVario; the Kobo has no DBus daemon, and thus XCSoar talks directly to WPASupplicant; but for improved compatibility, we should use DBus on OpenVario. For other projects, I've written C++ bindings for libdbus, which I'll add to XCSoar. These libdbus bindings can then be used to talk to systemd-networkd. Much of WifiDialog can be used on OpenVario, but it requires some abstractions like how to talk to WPASupplicant and how to configure the IP address (systemd-networkd instead of launching udhcpc manually). I don't think Kobo/System.cpp can be reused. It hard-codes lots of Kobo things, and these need to be auto-detected on an OpenVario. |
Beta Was this translation helpful? Give feedback.
-
I also started working on the OpenvarioMenu, in parallel to @Blaubart (#1107). I recognized that a lot of stuff can be re-used from the KoboMenu, for example:
System.cpp
WPASupplicant.cpp
WifiDialog.cpp
My proposal would be to move those into a more generic folder (like EmbeddedMenu ?) with the device-specific menu files in sub-folders (Kobo, OV), then rename Kobo-specific methods (i.e.
IsKoboWifiOn()
toIsWifiOn()
inSystem.cpp
) and add the Openvario-specific code there.Is there a way to have a macro for Openvario to make the device specific changes within the same (renamed) method?
For example:
In the end, just the menu structure and device-specific menu items would remain separated.
What do you think @MaxKellermann ?
Beta Was this translation helpful? Give feedback.
All reactions