Thanks for the response!
]]>Hi DD,
We probably won’t patch (not fork) just for that.
Libunity does something similar but globally for apps, not for windows. It’s also part of a project which was discontinued and was designed to only work in Ubuntu so we’ve little interest in relying on it or using it in the scope of Cinnamon which is supposed to work everywhere. We could support libunity as an optional dependency (i.e. in some distros and not others) in addition to libxapp in Cinnamon but it wouldn’t be very useful in the window list.. it would be more useful in docks and we don’t ship one. If we were to display app progress globally in the Cinnamon UI somewhere then we could look into it… but then again, we could get that done very easily via libxapp and have it work everywhere in all distributions.
We could support libunity in our tools (mintinstall, mintbackup..etc..). It’s not something we need, but it could make them communicate with docks using libunity. It’s typically something we would merge or approve if somebody proposed a patch or a PR, it’s just not worth spending time on doing it ourselves in the scope of a release because we don’t ship any of these docks.
]]>Here is a link describing the Unity way of doing it:
https://wiki.ubuntu.com/Unity/LauncherAPI#Progress
This way is supported by having your app depend on libunity, I believe: https://launchpad.net/libunity
]]>Michael, libunity isn’t even present in Debian. When something was designed for a single desktop and that desktop was designed for a single distribution and the minute you get away from that ecosystem, there’s no support whatsoever, you don’t spend time supporting it. Not only that but Unity was discontinued. We wouldn’t use libunity even if it implemented what we need (which is window progress, not app progress).
I’m disappointed you feel the same way about libxapp, because it’s clearly designed to work everywhere and for everybody, but that’s your right. If you feel like this then by all means do not spend time supporting it. Wait until it gets adopted broadly or dies silently. Nobody’s asking you to waste your time and effort, so please extend the courtoisie to us and don’t ask us to support things like libunity.
]]>> It’s not incompatible with Unity at all. If Unity was still being developed it could very well support it
Doesn’t make much difference, really. Applications will still need to support the Unity implementation and yours. That’s what I was talking about: duplicate time and effort, for not that much gain. And despite the demise of Unity, several docks (like Dash to Dock, and Plank IIRC) still support the progress bar (the former even introducing support for it _now_).
> First, there’s an issue with libunity itself.. the overall project was abandoned and it’s not available in all the distributions we support
Same problems apply to libxapp, which I doubt is available in more distros than libunity. (If that’s even a hard dependency.)
Edit by Clem: It’s not incompatible with Unity at all. If Unity was still being developed it could very well support it. When we work on Xapp we have other DEs in mind. This is there for any DE and in any distribution. First, there’s an issue with libunity itself.. the overall project was abandoned and it’s not available in all the distributions we support. Second, it doesn’t really do what we want. It sets progress for apps, not for windows. We don’t want to rely on the presence of a .desktop file and we need to set progress for one particular window. Sometimes that window even is outside of the scope of our own application. For instance when a script launches a Zenity dialog or installs packages via Synaptic.
]]>I’m glad to have been of some help. As far as I can tell, appimage.org is for people who want to make Appimages. Mostly, I get appimage files from the application website.
However, you can go to ‘bintray.com/probono/AppImages’ where you will find a large, searchable collection of appimages. I have no idea how ‘safe and secure’ this arrangement is and it might be a good idea to run them as a separate user who has been set up just for that purpose. You can’t be too paranoid when it comes to running software.
]]>Otherwise, thanks for all that you do and I look forward to seeing what 18.3 offers!
]]>While the Software Manager is great, I often find that Synaptic is quicker for me to navigate, and almost all online forum and article instructions are given in apt commands. If it only lists packages installed specifically through Software Manager, then it would severely cripple the Backup tool. If it lists packages from wherever you’ve installed it, then we’re all good and you can ignore this question.
]]>