--a534148835c045b2b0f0a33c1b44c3e8
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ascii"
Mime-Version: 1.0

kossebau added a comment.


  Thanks for pasting the chat log, that sheds more light onto things :)
  Seems to me the spec author(s?) are not sure themselves what would be the best naming pattern (besides rtld namespacing) and are still sorting that out.
  Which to me leaves the choice between being consistent with existing naming practice (at least in KDE spheres) and going for some unclear motivated naming recommendation not yet hard-coded in spec policy. Where I personally then would tend to the former, leaving the .desktop suffix.
  
  But no hard opinion, leaving the call to the maintainers.
  
  Grepping across KDE's sources with https://lxr.kde.org/search?_filestring=&_string=launchable&_casesensitive=1 it seems that adding <launchable> needs more advertizing in general. Do I correctly assume that Discover and friends already make use of that data bit, so it's valuable to have it set? Would then go and add for apps I care a bit :)

REPOSITORY
  R118 Plasma SDK

REVISION DETAIL
  https://phabricator.kde.org/D10920

To: kossebau, sebas, mart, broulik
Cc: ngraham, plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart

--a534148835c045b2b0f0a33c1b44c3e8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="ascii"
Mime-Version: 1.0

<table><tr><td style=3D"">kossebau added a comment.
</td><a style=3D"text-decoration: none; padding: 4px 8px; margin: 0 8px 8px=
; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; back=
ground-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1=
f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href=
=3D"https://phabricator.kde.org/D10920" rel=3D"noreferrer">View Revision</a=
></tr></table><br /><div><div><p>Thanks for pasting the chat log, that shed=
s more light onto things :)<br />
Seems to me the spec author(s?) are not sure themselves what would be the b=
est naming pattern (besides rtld namespacing) and are still sorting that ou=
t.<br />
Which to me leaves the choice between being consistent with existing naming=
 practice (at least in KDE spheres) and going for some unclear motivated na=
ming recommendation not yet hard-coded in spec policy. Where I personally t=
hen would tend to the former, leaving the .desktop suffix.</p>

<p>But no hard opinion, leaving the call to the maintainers.</p>

<p>Grepping across KDE&#039;s sources with <a href=3D"https://lxr.kde.org/s=
earch?_filestring=3D&amp;_string=3Dlaunchable&amp;_casesensitive=3D1" class=
=3D"remarkup-link" target=3D"_blank" rel=3D"noreferrer">https://lxr.kde.org=
/search?_filestring=3D&amp;_string=3Dlaunchable&amp;_casesensitive=3D1</a> =
it seems that adding &lt;launchable&gt; needs more advertizing in general. =
Do I correctly assume that Discover and friends already make use of that da=
ta bit, so it&#039;s valuable to have it set? Would then go and add for app=
s I care a bit :)</p></div></div><br /><div><strong>REPOSITORY</strong><div=
><div>R118 Plasma SDK</div></div></div><br /><div><strong>REVISION DETAIL</=
strong><div><a href=3D"https://phabricator.kde.org/D10920" rel=3D"noreferre=
r">https://phabricator.kde.org/D10920</a></div></div><br /><div><strong>To:=
 </strong>kossebau, sebas, mart, broulik<br /><strong>Cc: </strong>ngraham,=
 plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, se=
bas, apol, mart<br /></div>
--a534148835c045b2b0f0a33c1b44c3e8--