--===============0341914159==
Content-Type: multipart/signed;
  boundary="nextPart1779478.ppMuX34OiO";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1779478.ppMuX34OiO
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 28 September 2005 22:17, Aaron J. Seigo wrote:

> > with a list of applets and special buttons (!). In case of special
> > buttons add applet to panel (in fact, all references to applet)  is not
> > valid anymore.
>
> the point is that users don't know the difference between "special button=
s"
> and "applets". for instance, people would look in "Applets" for the K Menu
> or Window List buttons, but they aren't applets, they are "special
> buttons". so i lumped them all together so people don't have to know the
> internal workings of kicker to be able to use it.

Why not go one step further, forget about special button and call them
applets? This would remove the View combo from the add applet dialog,
which IMHO is redundant. The word "applet" is already very technical. So,
why scare my mom&dad with special buttons? :-)

> > I'd suggest to call the top level just "Add" or "Add Applet" and remove
> > any reference to special button. It'd make it less technical.
>
> how would one distinguish between adding an applicaton and adding an
> applet, then? they are two different entries and they aren't going to be
> merged into one.

Sorry, somehow I didn't finish my thought. In case of "Add" there would
be a submenu with "Applet" and "Application button", just like in remove
from panel. Finally, it could look like the following:

Add
 -> Applet
 -> Application Button
Remove
 -> Applet
 -> Application Button

> > If you really want to distinguish between panel and menubar, call the
> > dialog "Panel|Menubar - Add" and the add button "Add to Panel|Menubar".
>
> this is a bit more tricky to do (not hard, just more code to write) and i
> never got around to it. we're in string freeze now AFAIK so it's too late
> to do that now.

If one considers it as a bug, it is OK to introduce new strings, isn't it?

> btw, thanks for spending time and effort on translating kde! =3D)

Thanks for your time and efforts to make this happen. :-)

Mashrab.

=2D-=20
Mashrab Kuvatov
PGP key: www.uni-bremen.de/~kmashrab/kmashrab.asc

--nextPart1779478.ppMuX34OiO
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBDO8lPiSmHahjHWuoRAjrYAJ0ScEz0pcUOb13UhJ/nTKrxTL8qtACfU8KR
sawFDaPd50UxgNemyvmK8KM=
=JhAS
-----END PGP SIGNATURE-----

--nextPart1779478.ppMuX34OiO--

--===============0341914159==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

--===============0341914159==--