scrcpy
scrcpy copied to clipboard
QtScrcpy
Amazing project. Thank you! I reimplemented scrcpy with different technology stacks (Qt + Opengl) and added something:
- an interface for interaction.
- connecting multiple devices to the same application
Of course I want to share it. QtScrcpy

@rom1v Can we have this implemented into scrcpy please, Its such a great idea.
Cool UI :+1: Great job!
This is something missing in scrcpy, especially for users not comfortable with the command-line.
You "converted" every "class" into in C++/Qt (the signal/slots mechanism in indeed very appropriate), but now you if you want to keep it up to date with scrcpy, you will have to reimplement the changes introduced by every commit.
I would like (for a long time) to separate the "core" and the UI, to provide something like a libscrcpy. This would allow to implement different UI (I want to keep SDL for a lightweight version, but Qt is better if we want widgets), or even implement custom apps which could use the core API to receive video frames and control the device (for automation or whatever).
The core would remain in C, but a C++ app could use it directly (and use some RAII wrappers for convenience). That way, you could just write the UI part, and keep up to date with scrcpy easily.
I will try to think more about such an API.
Is it available in english sir?
Cool UI 👍 Great job!
This is something missing in scrcpy, especially for users not comfortable with the command-line.
You "converted" every "class" into in C++/Qt (the signal/slots mechanism in indeed very appropriate), but now you if you want to keep it up to date with scrcpy, you will have to reimplement the changes introduced by every commit.
I would like (for a long time) to separate the "core" and the UI, to provide something like a libscrcpy. This would allow to implement different UI (I want to keep SDL for a lightweight version, but Qt is better if we want widgets), or even implement custom apps which could use the core API to receive video frames and control the device (for automation or whatever).
The core would remain in C, but a C++ app could use it directly (and use some RAII wrappers for convenience). That way, you could just write the UI part, and keep up to date with scrcpy easily.
I will try to think more about such an API.
keeping up with strcpy is really a problem, but it's also in line with my goal: to improve my own Qt combat skills, I will continue to follow up on new features.
In addition, separating core and ui is a good idea. When libscrcpy is done, I am happy to add qt ui to it.
Is it available in english sir?
my english is not very good, so I google translated a readme english
nice job, man
Windows users savior =)
Very nice addition @barry-ran !!! Great work!
Is it available in english sir?
Will anyone reply to this ???