You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there, I am looking to integrate a GUI with this project to make connections to an innernet network by less technical people possible.
However, it seems to me that the client binary crate contains a lot of code for maintaining Wireguard devices, as well as communication with the remote API. In the interest of creating more interaction surfaces (e.g., GUIs, Android applications, ...), I think it would be beneficial to refactor some of this code into its own library, separated from the command line interface code.
I would be interested to help with such refactoring, but I haven't had time to look into the code much, so I could be wrong and perhaps my suggestion does not really fit in the design philosophy of the project.
The text was updated successfully, but these errors were encountered:
Hey @bramvdbogaerde, very sorry for the late reply! I would love to help you work on GUIs for innernet, including refactoring the client code to provide an easy API for different frontends.
Hello there, I am looking to integrate a GUI with this project to make connections to an innernet network by less technical people possible.
However, it seems to me that the
client
binary crate contains a lot of code for maintaining Wireguard devices, as well as communication with the remote API. In the interest of creating more interaction surfaces (e.g., GUIs, Android applications, ...), I think it would be beneficial to refactor some of this code into its own library, separated from the command line interface code.I would be interested to help with such refactoring, but I haven't had time to look into the code much, so I could be wrong and perhaps my suggestion does not really fit in the design philosophy of the project.
The text was updated successfully, but these errors were encountered: