Bug#159749: ITP: xcardii -- GUI program to manage MuscleCard smartcards
Ludovic Rousseau
Version: N/A; reported 2002-09-05
Severity: wishlist
* Package name : xcardii
Version : 0.9.7
Upstream Author : David Corcoran <corc...@linuxnet.com>
* URL : http://linuxnet.com/musclecard/index.html
* License : BSD
Description : GUI program to manage MuscleCard smartcards
XCardII is a GUI program to manage smartcards, drag and drop files to
the smartcard, manage PINs, objects, keys, etc. Import, export, and
generate onboard keys.
--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Colin Walters
> Package: wnpp
> Version: N/A; reported 2002-09-05
> Severity: wishlist
>
> * Package name : xcardii
> Version : 0.9.7
> Upstream Author : David Corcoran <corc...@linuxnet.com>
> * URL : http://linuxnet.com/musclecard/index.html
> * License : BSD
> Description : GUI program to manage MuscleCard smartcards
Could you at least change "GUI" to "Graphical"? We should keep as much
technical jargon out of the descriptions as possible, unless the target
audience of the package will know what it means.
Ludovic Rousseau
> On Thu, 2002-09-05 at 12:56, Ludovic Rousseau wrote:
> > Package: wnpp
> > Version: N/A; reported 2002-09-05
> > Severity: wishlist
> >
> > * Package name : xcardii
> > Version : 0.9.7
> > Upstream Author : David Corcoran <corc...@linuxnet.com>
> > * URL : http://linuxnet.com/musclecard/index.html
> > * License : BSD
> > Description : GUI program to manage MuscleCard smartcards
>
> Could you at least change "GUI" to "Graphical"? We should keep as much
> technical jargon out of the descriptions as possible, unless the target
> audience of the package will know what it means.
Of course I will change it. Sorry.
--
Dr. Ludovic Rousseau Ludovic....@free.fr
-- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. --
tomas p
> > Description : GUI program to manage MuscleCard smartcards
>
> Could you at least change "GUI" to "Graphical"? We should keep as much
> technical jargon out of the descriptions as possible, unless the target
> audience of the package will know what it means.
IMHO GUI is clearer than "graphical". I'd be expecting something fancy
when reading the word "graphical".
*t
*t
--
to
ma
s
p
Jamie Wilkinson
>On 5 Sep 2002, Colin Walters wrote:
>
>> > Description : GUI program to manage MuscleCard smartcards
>>
>> Could you at least change "GUI" to "Graphical"? We should keep as much
>> technical jargon out of the descriptions as possible, unless the target
>> audience of the package will know what it means.
>
>IMHO GUI is clearer than "graphical". I'd be expecting something fancy
>when reading the word "graphical".
Description: MuscleCard smartcard manager
Colin Walters
> On 5 Sep 2002, Colin Walters wrote:
>
> > > Description : GUI program to manage MuscleCard smartcards
> >
> > Could you at least change "GUI" to "Graphical"? We should keep as much
> > technical jargon out of the descriptions as possible, unless the target
> > audience of the package will know what it means.
>
> IMHO GUI is clearer than "graphical". I'd be expecting something fancy
> when reading the word "graphical".
I think this is not the case for the vast majority of people.
Ludovic Rousseau
> This one time, at band camp, tomas p wrote:
> >On 5 Sep 2002, Colin Walters wrote:
> >
> >> > Description : GUI program to manage MuscleCard smartcards
> >>
> >> Could you at least change "GUI" to "Graphical"? We should keep as much
> >> technical jargon out of the descriptions as possible, unless the target
> >> audience of the package will know what it means.
> >
> >IMHO GUI is clearer than "graphical". I'd be expecting something fancy
> >when reading the word "graphical".
>
> Description: MuscleCard smartcard manager
That would be a solution but I have two packages with nearly the same
functionnalities. One is graphical or GUI or whatever you call it (uses
QT) and the other is in text mode or CLI or whatere you call it.
The two ITPs are #159749 and #159751.
I think it is informative to tell if it is a "graphical" or "text"
version in the one-line description.
note: I found 113 occurences of "GUI" in the one-line description on
unstable, and only ~10 with "text-mode" or 'textmode".
--
Dr. Ludovic Rousseau Ludovic....@free.fr
-- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. --
Mario Lang
> Le vendredi 06 septembre 2002 à 18:57:09, Jamie Wilkinson a écrit:
>> This one time, at band camp, tomas p wrote:
>> >On 5 Sep 2002, Colin Walters wrote:
>> >
>> >> > Description : GUI program to manage MuscleCard smartcards
>> >>
>> >> Could you at least change "GUI" to "Graphical"? We should keep as much
>> >> technical jargon out of the descriptions as possible, unless the target
>> >> audience of the package will know what it means.
>> >
>> >IMHO GUI is clearer than "graphical". I'd be expecting something fancy
>> >when reading the word "graphical".
>>
>> Description: MuscleCard smartcard manager
>
> That would be a solution but I have two packages with nearly the same
> functionnalities. One is graphical or GUI or whatever you call it (uses
> QT) and the other is in text mode or CLI or whatere you call it.
>
> The two ITPs are #159749 and #159751.
>
> I think it is informative to tell if it is a "graphical" or "text"
> version in the one-line description.
I totally agree! I'd even say it's important. There are people out there
(like me) who can not use graphical programs at all.
I think it is quite important to clearly specify if something is
GUI or text-mode.
--
CYa,
Mario
John H. Robinson, IV
> I think it is quite important to clearly specify if something is
> GUI or text-mode.
is a curses interface GUI or text or cli?
i believe the distinction should be X, or console, since most
curses-based gui's will still work on a console.
good example: xfm (X), mc (curses), cp/mv/ls (cli)
all three do the same thing (basically) but have vastly different
interfaces.
so perhaps we need to better define what a GUI / CLI is or is not (if we
have not already, and i am simply dense)
-john
Mario Lang
> Mario Lang wrote:
>
>> I think it is quite important to clearly specify if something is
>> GUI or text-mode.
>
> is a curses interface GUI or text or cli?
It is text.
> i believe the distinction should be X, or console, since most
> curses-based gui's will still work on a console.
True, the most important distinction is if the program
is either:
1. X11 or framebuffer: Graphical
2. curses/slang, ctk, whatever, cli: text
But it could be useful to add a third category, cli, which specifies
all command-line and pipe-driven tools.
> good example: xfm (X), mc (curses), cp/mv/ls (cli)
You forgot gmc :)
> all three do the same thing (basically) but have vastly different
> interfaces.
>
> so perhaps we need to better define what a GUI / CLI is or is not (if we
> have not already, and i am simply dense)
I think it would be very useful if we could have a clear distinction,
best would be if this could be integrated into the package managment tools,
especially if it comes to viewing package lists or searching...
I'm too gren to step forward and propose some changes in control files,
but maybe someone can think of an elegant way to do this? It will
take a long time till all packages are categorized correctly, but
it would be very worthwhile doing imo.
--
CYa,
Mario
Erich Schubert
Well, these two should be distinguished. Console-Framebuffer are not
in every kernel.
Then there are developments such as Berlin, DirectFB, MicroWindows.
People also might want to distinguish QT and GTK...
(i don't like qt apps, i always prefer gtk ones)
That reminds me of my "Package-Tags" (formerly Keywords) proposal.
.desktop "VFolders" also are alike i think.
Greetings,
Erich
--
erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C
Go away or i'll replace you with a very small shell script.
Es ist besser, geliebt und verloren zu haben, als niemals geliebt zu haben.
Humor sollte immmer dabeisein, auch bei Problemen.