Improve documentation about launchers #391
Conversation
|
|
There was a problem hiding this comment.
Some comments about things that you might not be aware of and a question about usefulness of NotShowIn=X-MeeGo. I didn't check if that D-Bus information is correct, but it sounds sane, although anything with Maemo sounds like a super old relic 😂 and I'd personally rather not advertise those.
Reference/Core_Areas_and_APIs/Apps_and_MW/Lipstick/Launchers/README.md
Outdated
Show resolved
Hide resolved
Reference/Core_Areas_and_APIs/Apps_and_MW/Lipstick/Launchers/README.md
Outdated
Show resolved
Hide resolved
For me it's about reducing confusion. Sailjail-related documentation being rather fragmented, it's really hard to piece everything together, which was one of the main motivations for this PR. You can see devs wondering on how to do DBus-related things often on the Forums and other places. But it's your call, we can drop it from this. |
| This is mainly useful for registering a MIME Type launchers. | ||
|
|
||
| In case of multi-platform apps sharing the same .desktop file, app developers | ||
| can use _NotShowIn=X-MeeGo_, to hide the launcher only in Sailfish OS. |
There was a problem hiding this comment.
Uh, think we could avoid meego references at this point. If needed it should be easy to add sailfish specific NotShownIn option, but then again is there actual need to have this? Unlike on linux desktop where one can change the desktop environment the sailfish apps are executed in more controlled environment. If a .desktop is not wanted to be visible as launcher, why include it in the rpm at all?
4 participants
No description provided.