Recently on the user mailinglist there was a very long thread about people missing the power of the GUI we had in Qubes Manager, after switching to v4.0
My interpretation was that people don’t just specifically miss the QM, but that they miss the power of GUIs for many common tasks. The complaint of losing the QM is in my opinion the result of users losing the main (only) graphical user interface to get around in Qubes. I started 2 projects (not public just yet). * a library (.so) to provide a nice API to the admin-API. This is similar (is my guess) as the python code shipped by the core team, the difference is that this library allows access to those that use C++. This library in no way tried to compete with the python APIs, I’d see it more like language bindings as different people have different programming languages they are capable of using. * A simple “manager”. See attached screenshot of the first working version. For me the point is to learn the admin API with this project and create a useful GUI for my own use, hoping others will like it too. I can see the library being used to allow existing KDE/Gnome developers to write apps or extensions to the existing platforms there, something that is impossible currently as KDE plasma “apps” are mostly written in C++ or JavaScript. This is quite immature code and I still have to investigate the event APIs as I hope I can avoid polling updates. I just wanted to give you guys a heads-up :) -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/floweethehub -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/4280660.5h65eulxYS%40strawberry. For more options, visit https://groups.google.com/d/optout.
