• More uniformity in .desktop files

    From Daniele Forsi@21:1/5 to All on Sat Sep 11 23:10:01 2021
    Hello,

    I'm looking at .desktop files of applications maintained by debian
    hams and there are some cases where we could have more similar
    categories.
    For example look at the following applications:

    CubicSDR ['DataVisualization', 'HamRadio', 'Science']
    CuteSdr ['HamRadio', 'Tuner', 'Utility']
    Fldigi ['HamRadio', 'Network']
    Gqrx ['HamRadio', 'Network']
    qthid-2.2 ['HamRadio', 'Tuner', 'Utility']
    qthid ['HamRadio', 'Tuner', 'Utility']
    Quisk ['HamRadio', 'Tuner', 'Utility']

    I think that at least CuteSdr and Quisk aren't "Utility" and all of
    them have tuner functionality.
    Removing the "Utility" category would reduce that submenu which is so big. There isn't a "Tuner" submenu at least in Xfce4 and in KDE, but I
    guess that it could exist in a different desktop environment because
    it is an "Additional Category" listed at https://specifications.freedesktop.org/menu-spec/latest/apas02.html

    Here is the list of the .desktop files installed on my Debian testing
    system which contain the HamRadio category, do you see some
    application missing:

    CHIRP ['HamRadio', 'Utility']
    comptext ['HamRadio', 'Network']
    comptty ['HamRadio', 'Network']
    CQRLOG ['HamRadio', 'Network']
    CubicSDR ['DataVisualization', 'HamRadio', 'Science']
    CuteSdr ['HamRadio', 'Tuner', 'Utility']
    Dire Wolf ['HamRadio', 'Network']
    ebook2cw ['Audio', 'HamRadio']
    fccexam ['Education', 'HamRadio']
    flamp ['HamRadio', 'Network']
    Flarq ['HamRadio', 'Network']
    Fldigi ['HamRadio', 'Network']
    flmsg ['HamRadio', 'Network']
    Flrig ['HamRadio', 'Network']
    Flwrap ['HamRadio', 'Network']
    FreeDV ['Audio', 'AudioVideo', 'GNOME', 'GTK', 'HamRadio']
    glfer ['HamRadio', 'Utility']
    GNU Radio Companion ['Development', 'HamRadio', 'Science']
    Gpredict ['Astronomy', 'Education', 'HamRadio', 'Network', 'Science']
    Gqrx ['HamRadio', 'Network']
    Grig ['Audio', 'HamRadio']
    GTK Smith Chart Calculator ['Education', 'HamRadio']
    hamexam ['Education', 'HamRadio']
    KLog ['HamRadio', 'Network']
    Linpsk ['HamRadio', 'Network']
    Message Aggregator ['Audio', 'AudioVideo', 'HamRadio']
    nec2c ['HamRadio', 'Network', 'X-HamRadio-Antennas']
    psk31lx ['Audio', 'AudioVideo', 'ConsoleOnly', 'HamRadio']
    PyQSO ['HamRadio', 'Utility']
    qrq ['Audio', 'HamRadio']
    QSSTV ['HamRadio', 'Network']
    Qtel ['Application', 'HamRadio', 'Network', 'Qt']
    qthid-2.2 ['HamRadio', 'Tuner', 'Utility']
    qthid ['HamRadio', 'Tuner', 'Utility']
    Quisk ['HamRadio', 'Tuner', 'Utility']
    TrustedQSL ['Application', 'HamRadio', 'Utility']
    Tucnak ['HamRadio', 'Network']
    twclock ['HamRadio', 'Utility']
    twpsk ['HamRadio', 'Network']
    wsjtx ['Audio', 'AudioVideo', 'HamRadio']
    Xastir ['HamRadio', 'Network']
    Xdx ['HamRadio', 'Network']
    Xlog ['Database', 'GTK', 'HamRadio', 'Utility']

    What surprises me is that psk31lx and wsjtx appear under the
    Multimedia menu of desktop environments because they have the Audio
    and AudioVIdeo categories and many radio applications appear under the
    Internet menu because they have the Network category.

    From that list is missing xnec2 because it hasn't got the HamRagio
    category which nec2c has.

    The .desktop files of nec2 and xnec2 could be more similar, I wonder
    if it's worth it because nec2 can be started from the menu but it
    isn't usable because there is no way to set the input and the output
    files or stidin/stdout

    Some applications have a full path in the .desktop file:
    PyQSO /usr/bin/pyqso
    Qtel /usr/bin/qtel
    Grig /usr/bin/grig
    Xdx /usr/bin/xdx
    Tucnak /usr/bin/tucnak
    nec2c /usr/bin/nec2c
    Dire Wolf /usr/bin/x-terminal-emulator -e direwolf
    KLog /usr/bin/klog
    CuteSdr /usr/bin/CuteSdr

    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniele Forsi@21:1/5 to All on Sun Sep 12 19:50:02 2021
    Hello,

    I'm trying to display categories and keywords and you can find here an
    HTML table and a CSV file:
    https://forsi.it/debian/packages/desktop-files/

    There are at least 2 errors among the keywords:

    1)
    in /usr/share/applications/gsmc.desktop the "Keywords=" part is present twice: Keywords=Keywords=Ham Radio;Antenna;RF;Impedence;Calculator;

    2)
    in /usr/share/applications/grig.desktop there is a space before
    "Remote radio" and it's the only one that uses a comma instead of a
    semicolon:
    Keywords=HamRadio, Remote radio

    however,the specs say "multiple values should be separated by a semicolon"
    https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s04.html I have no idea about the leading space


    There are some keywords that maybe could be uniformed:
    Ham
    Ham Radio
    HamRadio
    Hamradio
    ham
    hamradio

    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Berg@21:1/5 to All on Mon Sep 13 10:00:02 2021
    Re: Daniele Forsi
    Hello,

    I'm trying to display categories and keywords and you can find here an
    HTML table and a CSV file:
    https://forsi.it/debian/packages/desktop-files/

    There are at least 2 errors among the keywords:

    1)
    in /usr/share/applications/gsmc.desktop the "Keywords=" part is present twice:
    Keywords=Keywords=Ham Radio;Antenna;RF;Impedence;Calculator;

    2)
    in /usr/share/applications/grig.desktop there is a space before
    "Remote radio" and it's the only one that uses a comma instead of a semicolon:
    Keywords=HamRadio, Remote radio

    however,the specs say "multiple values should be separated by a semicolon"
    https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s04.html
    I have no idea about the leading space


    There are some keywords that maybe could be uniformed:
    Ham
    Ham Radio
    HamRadio
    Hamradio
    ham
    hamradio

    Hi Daniele,

    thanks for looking at this. As said in the twclock thread, I'm not
    using .desktop files, so I cannot say which of these are real issues
    and not just syntax details, but we should try to get them fixed.

    Do you want git access on https://salsa.debian.org/debian-hamradio-team ? Though we should also try to avoid having to carry these around as
    patches forever, so submitting upstream is probably even more
    important.

    73,
    Christoph DF7CB

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniele Forsi@21:1/5 to Christoph Berg on Tue Sep 14 08:10:03 2021
    Christoph Berg wrote:

    Do you want git access on https://salsa.debian.org/debian-hamradio-team ?

    yes, please, my username is dforsi-guest
    I can fix the syntax errors in gsmc.desktop and grig.desktop

    Though we should also try to avoid having to carry these around as
    patches forever, so submitting upstream is probably even more
    important.

    agree, however I think that showing that patches are available might
    increase the chances that they applied upstream, shall we use a
    different branch than master in the packaging repos, or only attach
    patches to our bugs and forward them to upstreams?

    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Berg@21:1/5 to All on Tue Sep 14 22:00:01 2021
    Re: Daniele Forsi
    Christoph Berg wrote:

    Do you want git access on https://salsa.debian.org/debian-hamradio-team ?

    yes, please, my username is dforsi-guest
    I can fix the syntax errors in gsmc.desktop and grig.desktop

    Added you now. Welcome!

    Fwiw, there is also #debian-hams on OFTC if you are on IRC.

    Though we should also try to avoid having to carry these around as
    patches forever, so submitting upstream is probably even more
    important.

    agree, however I think that showing that patches are available might
    increase the chances that they applied upstream, shall we use a
    different branch than master in the packaging repos, or only attach
    patches to our bugs and forward them to upstreams?

    I guess that depends on how fast you think the next upstream release
    would happen. Feel free to push directly to master if you want to, or
    open merge requests.

    73,
    Christoph

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniele Forsi@21:1/5 to Christoph Berg on Thu Sep 16 23:00:01 2021
    Christoph Berg wrote:

    Feel free to push directly to master if you want to, or
    open merge requests.

    I pushed to master; should I have added a new section to the changelogs?

    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Berg@21:1/5 to All on Fri Sep 17 09:50:02 2021
    Re: Daniele Forsi
    Christoph Berg wrote:

    Feel free to push directly to master if you want to, or
    open merge requests.

    I pushed to master; should I have added a new section to the changelogs?

    That would at least the packaging style I prefer (updating
    debian/changelog along with the changes), I don't think any repo is
    using after-the-fact "git dch" changelogs.

    Christoph

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)