On 22/04/2011 18:05, Josselin Mouette wrote:
Le vendredi 22 avril 2011 à 17:51 +0200, Bernhard R. Link a écrit :
The difference is that a user has to know more when enabling stuff, as
they get shown many things were enabling does not make any sense.
And there is no way to say show me
+++ Josselin Mouette [2011-04-20 10:13 +0200]:
Le mercredi 20 avril 2011 à 09:12 +0200, Bernhard R. Link a écrit :
Some suggestions for a Debian .desktop policy[1]:
7) In case of 6) there must be a .desktop file with the same
command and adhering to this policy, unless that command
* Josselin Mouette j...@debian.org [110420 17:44]:
Le mercredi 20 avril 2011 à 17:30 +0200, Bernhard R. Link a écrit :
But for me having everything in the menu is its most important feature.
It’s not a feature. It is a design mistake.
Speaking about design mistakes: You suggest to use the
Le vendredi 22 avril 2011 à 13:48 +0200, Bernhard R. Link a écrit :
* Josselin Mouette j...@debian.org [110420 17:44]:
Le mercredi 20 avril 2011 à 17:30 +0200, Bernhard R. Link a écrit :
But for me having everything in the menu is its most important feature.
It’s not a feature. It is a
On Wed, Apr 20, 2011 at 9:12 AM, Bernhard R. Link brl...@debian.org wrote:
Some suggestions for a Debian .desktop policy[1]:
Could we add also a lintian check in order to check if mime type and
desktop file are the same ?
And add some emphasys about mime type in destop policy
Bastien
--
To
* Josselin Mouette j...@debian.org [110422 16:25]:
Le vendredi 22 avril 2011 à 13:48 +0200, Bernhard R. Link a écrit :
* Josselin Mouette j...@debian.org [110420 17:44]:
Le mercredi 20 avril 2011 à 17:30 +0200, Bernhard R. Link a écrit :
But for me having everything in the menu is its
Le vendredi 22 avril 2011 à 17:51 +0200, Bernhard R. Link a écrit :
The difference is that a user has to know more when enabling stuff, as
they get shown many things were enabling does not make any sense.
And there is no way to say show me everything in the menu, which is
especially bad for
On Friday, April 22, 2011 12:05:20 PM Josselin Mouette wrote:
Le vendredi 22 avril 2011 à 17:51 +0200, Bernhard R. Link a écrit :
The difference is that a user has to know more when enabling stuff, as
they get shown many things were enabling does not make any sense.
And there is no way to
On Fri, Apr 22, 2011 at 06:05:20PM +0200, Josselin Mouette wrote:
You’re missing something. A menu that “shows everything” is unusable.
The Debian menu is a very good example of that kind of problem.
I think this depends on the number of entries. If you have a high number
you’re right. When I
Le jeudi 21 avril 2011 à 01:14 +0200, Kurt Roeckx a écrit :
I will find it very annoying when it says music player in the
menu without telling me *which* one it is.
But for people looking for a music player, they don't care (yet)
how it's called, so there probably is also a need have a way
Josselin Mouette j...@debian.org writes:
For example, Thunar works perfectly fine outside Xfce, but you don’t
want to show it in KDE or GNOME.
Why not?
Some users may prefer it to the standard app for the desktop
environment they're using.
-Miles
--
Politeness, n. The most acceptable
On to, 2011-04-21 at 16:20 +0900, Miles Bader wrote:
Josselin Mouette j...@debian.org writes:
For example, Thunar works perfectly fine outside Xfce, but you don’t
want to show it in KDE or GNOME.
Why not?
Some users may prefer it to the standard app for the desktop
environment they're
Some suggestions for a Debian .desktop policy[1]:
1) syntax according to freedesktop's Desktop Entry Specification
[TODO: always the latest, fix some version and increase that at
fixed points?]
2) Name must be a name properly name the program and be unique enough
to be useable if multiple
Le mercredi 20 avril 2011 à 09:12 +0200, Bernhard R. Link a écrit :
Some suggestions for a Debian .desktop policy[1]:
1) syntax according to freedesktop's Desktop Entry Specification
[TODO: always the latest, fix some version and increase that at
fixed points?]
2) Name must be a name
* Josselin Mouette j...@debian.org [110420 10:14]:
5) Categories must contain applicable KDE,GNOME,GTK,Qt,Motif,Java[3]
so that a menu manager cat filter out things not matching
the UI lookfeel if wanted.
6) A .desktop file is allowed to break above rules if is has a
On Wed, 20 Apr 2011 09:12:52 +0200
Bernhard R. Link brl...@debian.org wrote:
Some suggestions for a Debian .desktop policy[1]:
Do we actually need one? lintian makes a fairly decent job of this
currently and I have yet to see any specific examples of where desktop
files are a joke or not in
On Wed, Apr 20, 2011 at 4:47 PM, Neil Williams codeh...@debian.org wrote:
.. as validated by the desktop-file-validate utility, as used by
lintian.
desktop-file-validate is not used by lintian, perhaps there should be
a test similar to the man-db test though.
--
bye,
pabs
On 2011-04-20, Neil Williams codeh...@debian.org wrote:
e.g. ddd is useless as a Name. Data Display Debugger is OK as a Name,
particularly as the comment is Graphical debugger frontend.=20
what is the name of that app? is it 'ddd' or 'Data Display Debugger'?
Graphical debugger frontend should
On Wed, 20 Apr 2011 at 09:24:14 +, Sune Vuorela wrote:
I think we should actually try to investigate how different 'menus' is
using the desktop entries.
GNOME Shell: displays only Name in the applications menu; displays only Name
when you hover over favourite apps in the dock; type-ahead
* Neil Williams codeh...@debian.org [110420 10:47]:
Have you examples of desktop files which are not in shape currently?
Well, for example currently in squeeze there is
/usr/share/menu/evince:
?package(evince):needs=X11 section=Applications/Viewers\
title=Evince command=/usr/bin/evince\
On Wed, 20 Apr 2011 11:46:31 +0200
Bernhard R. Link brl...@debian.org wrote:
* Neil Williams codeh...@debian.org [110420 10:47]:
Have you examples of desktop files which are not in shape currently?
Well, for example currently in squeeze there is
/usr/share/menu/evince:
Le mercredi 20 avril 2011 à 10:37 +0200, Bernhard R. Link a écrit :
7) In case of 6) there must be a .desktop file with the same
command and adhering to this policy, unless that command cannot
be run (or cannot work) outside this environment[4].
I disagree with this rule.
On Wed, April 20, 2011 09:57, Paul Wise wrote:
On Wed, Apr 20, 2011 at 4:47 PM, Neil Williams codeh...@debian.org
wrote:
.. as validated by the desktop-file-validate utility, as used by
lintian.
desktop-file-validate is not used by lintian, perhaps there should be
a test similar to the
Le mercredi 20 avril 2011 à 11:46 +0200, Bernhard R. Link a écrit :
I'm going to start dropping debian/menu files from my packages
henceforth.
Sorry to be a bit harsh about that, but seriously???
Yes, seriously. There’s a better use of our time than maintaining menu
files and, similarly,
* Josselin Mouette j...@debian.org [110420 13:59]:
It’s not only a problem of ugliness. The #1 usability problem with the
Debian menu is the huge amount of entries. If you repeat this mistake
with the freedesktop menus, a menu system that has been nice so far
(nice, not great) would become
Le mercredi 20 avril 2011 à 17:30 +0200, Bernhard R. Link a écrit :
But for me having everything in the menu is its most important feature.
It’s not a feature. It is a design mistake.
If you keep on implementing whatever seems best for *your* use, without
any care for usability, you’re going
On 2011-04-20, Josselin Mouette j...@debian.org wrote:
Le mercredi 20 avril 2011 à 17:30 +0200, Bernhard R. Link a écrit :
But for me having everything in the menu is its most important feature.
[...]
There is a place where you can access everything that’s installed on
your system: it’s call
On Wed, Apr 20, 2011 at 09:47:25AM +0100, Neil Williams wrote:
3) Comments should be used to describe the function of the program so
that users who are unfamiliar with the program name will be able to
understand how the program can help them achieve tasks or partake in an
activity. Comments
28 matches
Mail list logo
