From kde-usability  Wed Nov 22 22:48:39 2006
From: Kevin Krammer <kevin.krammer () gmx ! at>
Date: Wed, 22 Nov 2006 22:48:39 +0000
To: kde-usability
Subject: Re: Localised folders in /home/user (Documents and Desktop)
Message-Id: <200611222348.48488.kevin.krammer () gmx ! at>
X-MARC-Message: https://marc.info/?l=kde-usability&m=116423577110593
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1846606494=="

--===============1846606494==
Content-Type: multipart/signed;
  boundary="nextPart9099669.BqqCbrgmH9";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart9099669.BqqCbrgmH9
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 22 November 2006 09:37, Sven Burmeister wrote:
> Hi!
>
> Am Mittwoch, 22. November 2006 01:26 schrieb Kevin Krammer:
> > You mean because they will just be using relative paths?
> >
> > What about URL edit widgets in file managers? Will they just remove
> > anything upwards from the user's home directory?
> > Do we then also rename the home: IO slave?
>
> On openusability there are reports about the usage of konqueror in
> filesystem mode. People hardly pay attention to the address-bar, if they
> work with files. But even if, a "normal user" works /home downwards and n=
ot
> upwards, so it is not as important. And of course renaming /home has bigg=
er
> implications and comes with bigger problems than anything in the user's
> directory.

Hmm, well, if we start assuming that "normal users" are not
=2D looking at paths
=2D not accessing the root directory
=2D not activating hidding file

why do we need a direct association with directories and folder names anywa=
y?
Wouldn't it be easier to have Desktop and Document just not be directories=
=20
from the user's point of view, i.e. below a hidden directory and thus never=
=20
visible in paths?

> > If this happens with data files, those of such broken programs will be
> > "lost". Data loss is considered to be one of the worst possible bugs.
> > Will be extremely "nice" to debug and great "fun" for us support people.
>
> I do not have any apps installed in home and even if, they should not be
> installed in Desktop or Documents.

I was talking about data, not applications.
Location of applications are unimportant, they are started by launchers (e.=
g.=20
K-menu)

Consider Firefox downloading something to the desktop, it won't be there fo=
r=20
users with KDE and German localisation, because their "desktop" is=20
called "Arbeitsfl=E4che", so the file is obviously not there.

Too bad for the Mozilla people, they'll get nice bugreports for broken=20
downloading, which they will be closing as not reproducible until someone=20
discovers it applies only to KDE users using non-English locales.
=46un!

> If there was a variable like=20
> $USERNAME_DOCUMENTS and all apps would use it, there would not be such a
> problem. You cannot make it easier for applications.

Variables do not work technically, can't be altered during runtime.

> What happens currently, if I rename Documents or Desktop, nothing fails, =
so
> why should it happen when they are localised straight away.

Right. Move/rename Desktop and tell me you still have all the file visible =
and=20
accessible on KDesktop

Cheers,
Kevin
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart9099669.BqqCbrgmH9
Content-Type: application/pgp-signature

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

iD8DBQBFZNPQnKMhG6pzZJIRAqrsAJ9FHe6qt/Ie2E90FCWfbr3WW5TOIgCff+b5
FXDujbiEDSTfar79hzu4EWo=
=qvCv
-----END PGP SIGNATURE-----

--nextPart9099669.BqqCbrgmH9--

--===============1846606494==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1846606494==--