-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make a crossplatform build #2
Comments
The problem you have is that this project is using I'm not sure if any of the socket libraries are also Windows dependent. |
AFAIK AvaloniaUI is supported by Wayland and most of used Linux Distributions works with Wayland. 😃 |
Also I don't think that most of Gentoo users or i3 DE will be use this instead of using teamviewer or other proprietary software. |
Thank you so much for the valuable advice. It would be great to make it cross-platform. |
Highly suggest using Eto and the modern dotnet 6+ to very easily build your app cross-platform with not much UI rework. I usually spend my days in Eto.Xammac and Eto.Wpf so I can help with the conversion as well. |
This is absolutely amazing!!! But I too would like a cross-platform version. I believe it would be best creating it in Qt (since it's already cross-platform ready) and that it can help reduce your problems @miroslavpejic85 (An AppImage of it would be gold!!!) |
Hello @eirannejad & @maverick74 Thank you so much, Your advice is greatly appreciated, I'm sure that all together we will find the best solution to make it so. |
Qt ( https://www.qt.io/ ) is largely used by the KDE community ( https://kde.org/ ) so you get a lot of support and documentation and you also have examples such as the Falkon browser or Linus Torvalds' Sub-surface |
I would advise against using Qt. While C# bindings exist, they're not actively maintained and ones that are, have no official support. Also, the winforms style of design is very old school, some form of markup language (i.e XAML) is favourable as most frameworks are taking this approach. Ive used AvaloniaUI in the past and it has good community support as well as official commercial support. Or maybe even having a web UI either through Blazor (WASM), WebSocket / SignalR bidirectional communication or a pure javascript / HTML5 implementation. |
Descargue y compile la aplicación , la ejecute y la probé , ingrese la IP del punto remoto , presione el botón conectar y se queda en un while mostrando el mensaje e: 4 trying to connect to , que me puede estar faltando para que funcione,? , cuando lo ejecute acepte que permitiera realizar cambios en el dispositivo. Gracias |
Create a new issue. This topic is regarding cross platform builds. |
Hi @jsanchez2021, I'm agree with @KieranDevvs, |
I've opened a PR to migrate the existing codebase over to .NET 8 (#61). |
Any updates on this? :D |
I'm working on refactoring the code based to separate out the UI and platform specific code from each other. Specifically I'm working on the encryption. Right now, the AES key is hard coded into the binary so a man in the middle attack is very trivial. Adding a Diffie–Hellman key exchange to the initial request handshake allows us to send a randomly generated AES key and IV securely so that the network session can be encrypted without any keys being known prior. Making this cross platform isn't as easy as just using something like Avalonia. Each platform has its own way of handling device inputs and providing a screen buffer. I'd have to add support for one platform at a time. With that being said, I'll be looking at Linux. I have no interest in macOS or any other platform as I don't know them well enough. Maybe others will also contribute towards that effort. But the bottom line is that P2P will have the ability to have other platform support added. I give no time frame, I'm working on it in my free time which I have almost none of. |
As I see this project is windows compatible only.
AFAIK there is a lot libraries which are compatible for different OS e.g. https://docs.microsoft.com/en-us/dotnet/core/install/linux
So could your provide builds for Ubuntu/MacOS ?
The text was updated successfully, but these errors were encountered: