Some comments from email thread on this discussion:
Looking at plugins/Unity/Launcher/backend/launcherbackend.cpp it looks like the code only handles application://<desktopfile> urls. In the case of click packages, it should handle appid:// url's like: appid://com.ubuntu.gallery/gallery/current-user-version, similar to how url-dispatcher handles them (or some other form that doesn't require the specific version number). The internal code could stay the same, just need some sort of lookup mechansim to map from current-user-version to an absolute path to the desktop file.
Otherwise, if I want gallery to show up in the launcher as it does today
I have to put the full path of the click's desktop file that includes
the version:
application://com.ubuntu.gallery_gallery_2.9.1.910.desktop
This seems problematic as it will break when gallery version is updated.
Some comments from email thread on this discussion: Unity/Launcher/ backend/ launcherbackend .cpp it looks like the code only handles application: //<desktopfile> urls. In the case of click packages, it should handle appid:// url's like: appid:/ /com.ubuntu. gallery/ gallery/ current- user-version, similar to how url-dispatcher handles them (or some other form that doesn't require the specific version number). The internal code could stay the same, just need some sort of lookup mechansim to map from current- user-version to an absolute path to the desktop file.
Looking at plugins/
Otherwise, if I want gallery to show up in the launcher as it does today //com.ubuntu. gallery_ gallery_ 2.9.1.910. desktop
I have to put the full path of the click's desktop file that includes
the version:
application:
This seems problematic as it will break when gallery version is updated.