<br><br><div class="gmail_quote">2008/12/14 Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sunday 14 December 2008, Fredrik Höglund wrote:<br>
> On Sunday 14 December 2008 17:09, Celeste Lyn Paul wrote:<br>
> > On Sunday 14 December 2008 10:34:22 Artur Souza (MoRpHeUz) wrote:<br>
> > > Hey!<br>
> > ><br>
> > > On Sun, Dec 14, 2008 at 12:00 PM, Fredrik Höglund <<a href="mailto:fredrik@kde.org">fredrik@kde.org</a>><br>
wrote:<br>
> > > > The warning that the desktop folder will be created when the user<br>
> > > > selects "Show Desktop folder" in the config dialog was carefully<br>
> > > > worked out in coordination with our usability experts, so I thank you<br>
> > > > for not removing it.<br>
> > ><br>
> > > That's why we are discussing this here and didnt commit<br>
> > > anything...from aseigo's point of view it shouldnt never create<br>
> > > automatically the folder thus making the warning useless.<br>
> ><br>
> > Because he doesn't want to promote the use of the Desktop folder?<br>
> > Personally, I agree and strongly dislike the use of the Desktop folder,<br>
> > but it is still part of the xdg folder spec isnt' it? I think it is a<br>
> > better idea to actively support it than allow users to configure it<br>
<br>
</div>er,... that's what we do: if the $DESKTOP path exists, as per xdg bullshit<br>
spec compliance, we respect it. if we're dealing with an OS with a forebrain<br>
then we respect that and don't force the $DESKTOP brain damage upon that poor<br>
user.<br>
<div class="Ih2E3d"><br>
> While slightly off-topic in the discussion, I think it's important that<br>
> when we want to change cross desktop standards that we do this in<br>
> collaboration with the other desktops,<br>
<br>
</div>yes, this needs to be taken to xdg.<br>
<div class="Ih2E3d"><br>
> and don't unilaterally start<br>
> ignoring standards we've helped create, but now decided that we don't like<br>
> anymore.<br>
<br>
</div>honestly, i'm not sure what the provenane of that spec is. fd.o is<br>
fundamentally BROKEN in this manner, but i do know that i never supported that<br>
craptastic spec.<br>
<div class="Ih2E3d"><br>
> If we don't do that then we end up creating problems for users and ISV's<br>
> alike.<br>
><br>
> An example of such a problem in this case is that Firefox saves all<br>
> downloaded files in the desktop folder by default. If we deny users access<br>
> to it, then they won't be able to find those files.<br>
<br>
</div>which belong in Downloads, not Desktop. poluting that folder with anything<br>
that isn't *desktop* oriented is so amazingly stupid that i sometimes wonder<br>
when software developers stopped thinking and just gave themselves up to<br>
punching in lines of code.<br>
<br>
which is to say we need to communicate, albeit more politely ;) , to the<br>
Firefox developers that they need to be putting their downloads elsewhere.<br>
<font color="#888888"></font></blockquote><div><br>The problem is, it isn't just Firefox, its lots of programs. Until the
majority of programs use the Downloads directory, as they should, there
has to be a way to make all downloads system wide go to the Downloads
directory, unless specified to go elsewhere. This would be a kludge,
but might be necessary. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Software<br>
<br>
</font><br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br>