All 8 comments
@rom1v Can we have this implemented into scrcpy please, Its such a great idea.
MrTeeXD
on 23 Jun 2019
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.
rom1v
on 23 Jun 2019
Is it available in english sir?
arley1708
on 23 Jun 2019
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.
barry-ran
on 24 Jun 2019
Is it available in english sir?
my english is not very good, so I google translated a readme
english
barry-ran
on 24 Jun 2019
nice job, man
latel
on 25 Jun 2019
Windows users savior =)
Plandercozeron
on 3 Jul 2019
Very nice addition @barry-ran !!! Great work!
TheRealMrSteel
on 18 Jul 2019
Related issues
fernandofreamunde
路
4Comments
jonnybrooks
路
3Comments
tonypachino
路
3Comments
targor
路
3Comments
udit7395
路
4Comments
Most helpful comment
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.