Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.misc > #1041 > unrolled thread

Nine Lessons Other Desktops Can Learn from KDE

Back to article view | Back to comp.misc

Contents

  Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-27 15:33 +0000
    Re: Nine Lessons Other Desktops Can Learn from KDE "jonh" <jon@nada-sub.co.uk> - 2014-02-27 11:41 -0600
      Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 15:33 +0000
    Re: Nine Lessons Other Desktops Can Learn from KDE Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-28 11:24 +0000
      Re: Nine Lessons Other Desktops Can Learn from KDE Marko Rauhamaa <marko@pacujo.net> - 2014-02-28 13:50 +0200
        Re: Nine Lessons Other Desktops Can Learn from KDE Bjoern Hoehrmann <bjoern@hoehrmann.de> - 2014-02-28 14:04 +0100
      Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 13:47 +0000
        Re: Nine Lessons Other Desktops Can Learn from KDE Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-03-01 00:46 +0000
      Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 14:01 +0000
        Re: Nine Lessons Other Desktops Can Learn from KDE Mike Easter <MikeE@ster.invalid> - 2014-02-28 08:03 -0800

#1041 — Nine Lessons Other Desktops Can Learn from KDE

 http://mobile.datamation.com/open-source/nine-lessons-other-deskto
ps-can-learn-from-kde-1.html
-- 

[toc] | [next] | [standalone]

#1047

When I set up FreeBSD recently on an old MacBook, I decided to use KDE as the desktop, 
just so I could have a look at something alternative to Ubuntu/Unity, which is my 
/de facto/ non-Windows desktop. I'd say my biggest gripe with it is that it doesn't 
use the "standard" keyboard mappings which I'm used to, such as  
#v+ 
Alt+Space
#v- 
 to open the system menu, 
#v+ 
Ctrl+Esc
#v- 
, etc, etc. (These keyboard mappings are entrenched in my muscle memory from over 
20 years of using Windows at work, and, for the most part, they work in Unity as 
well.)

But, as the article says, KDE is highly configurable, so with a bit of poking around 
in the settings, and some google fu, it wasn't to hard to remap any unfamiliar 
keyboard shortcuts. I also mapped all the various laptop brightness/volume controls 
so that they correspond to the Mac's funtion keys with the appropriate icons.

And then, I probably spent 3 or 4 hours reskinning widgets, tweaking the colour 
scheme and downloading new themes, until I had the 'perfect' look: light text 
on dark background with red accents. I don't think I've spent so long customizing 
my desktop since I discovered FVWM at University back in '94. It seems that the 
trend these days is away from user configuration -- some modern versions of Windows 
7 don't even let you change the colour of widgets at all -- and removing "power-user" 
functionality (rather than just hiding it) in the name of making things easier for 
the hypothetical "average computer user". 
-- 
--
"Make use of a lover or white-noise machine inside your master bedroom to assist you in drifting off to sleep."
View this thread at http://squte.com/node/4821#comment-11267

[toc] | [prev] | [next] | [standalone]

#1099

On Thu, 27 Feb 2014 11:41:14 -0600
"jonh" <jon@nada-sub.co.uk> wrote:

> But, as the article says, KDE is highly configurable, so with a bit of poking around 
> in the settings, and some google fu, it wasn't to hard to remap any unfamiliar 
> keyboard shortcuts. I also mapped all the various laptop brightness/volume controls 
> so that they correspond to the Mac's funtion keys with the appropriate icons.


I agree about the usefulness of the configurability.  I think in
general KDE4 is better looking than KDE3, but for sheer
configurability, KDE3 was better.  In fact, despite the article saying
how awesome it is that there are hundreds of existing modules and
widgets, I don't use many of them.  I much prefer the KDE3 desktop,
which I was able to tweak the hell out of, with KDE4 apps, which are
better than their KDE3 predecessors (big exception: KDEPIM, which is
now tied into Akonadi in annoying ways.  I much prefer the old version).

Still, the KDE team did the right thing in my opinion by building their
new environment in a way it can be reworked for a netbook or a tablet.
I'm not sure how Gnome3 is going to dig its way out of its hole, but
they're in bad shape at the moment, if you ask me.

I'd encourage anyone not already familiar with it to check out E17
too.  I gave it a whirl on Bodhi Linux and was really impressed.  On
that machine it replaced the Gnome Netbook Edition, which was OK but
not great.  E17 is really useful, and nice to look at too, and it flies
on my little Atom machine with low spec memory.

[toc] | [prev] | [next] | [standalone]

#1090

In message <lenls5$dao$2@solani.org> 
  RS Wood <rsw@therandymon.com> wrote:
>  http://mobile.datamation.com/open-source/nine-lessons-other-deskto
> ps-can-learn-from-kde-1.html

It would also be nice if your posting thingy didn't force-wrap URLs.

-- 
The Disc, being flat, has no real horizon. Any adventurous sailors who
get funny ideas from staring at eggs and oranges for too long and set
out for the antipodes soon learned that the reason why distant ships
sometimes looked as though they were disappearing over the edge of the
world was that they were disappearing over the edge of the world. --The
Light Fantastic

[toc] | [prev] | [next] | [standalone]

#1093

Lewis <g.kreme@gmail.com.dontsendmecopies>:

> It would also be nice if your posting thingy didn't force-wrap URLs.

You know, there's an actual standard for that (RFC 1738):

   In addition, there are many occasions when URLs are included in other
   kinds of text; examples include electronic mail, USENET news
   messages, or printed on paper. In such cases, it is convenient to
   have a separate syntactic wrapper that delimits the URL and separates
   it from the rest of the text, and in particular from punctuation
   marks that might be mistaken for part of the URL. For this purpose,
   is recommended that angle brackets ("<" and ">"), along with the
   prefix "URL:", be used to delimit the boundaries of the URL. This
   wrapper does not form part of the URL and should not be used in
   contexts in which delimiters are already specified.

   In the case where a fragment/anchor identifier is associated with a
   URL (following a "#"), the identifier would be placed within the
   brackets as well.

   In some cases, extra whitespace (spaces, linebreaks, tabs, etc.) may
   need to be added to break long URLs across lines. The whitespace
   should be ignored when extracting the URL.

   No whitespace should be introduced after a hyphen ("-") character.
   Because some typesetters and printers may (erroneously) introduce a
   hyphen at the end of line when breaking a line, the interpreter of a
   URL containing a line break immediately after a hyphen should ignore
   all unencoded whitespace around the line break, and should be aware
   that the hyphen may or may not actually be part of the URL.

   Examples:

      Yes, Jim, I found it under <URL:ftp://info.cern.ch/pub/www/doc;
      type=d> but you can probably pick it up from <URL:ftp://ds.in
      ternic.net/rfc>.  Note the warning in <URL:http://ds.internic.
      net/instructions/overview.html#WARNING>.

But then, RFC 2396 gives up on the idea:

   Within certain document media types, the base URI of the document can
   be embedded within the content itself such that it can be readily
   obtained by a parser. This can be useful for descriptive documents,
   such as tables of content, which may be transmitted to others through
   protocols other than their usual retrieval context (e.g., E-Mail or
   USENET news).

   It is beyond the scope of this document to specify how, for each
   media type, the base URI can be embedded.


Marko

[toc] | [prev] | [next] | [standalone]

#1094

* Marko Rauhamaa wrote in comp.misc:
>But then, RFC 2396 gives up on the idea:
>
>   Within certain document media types, the base URI of the document can
>   be embedded within the content itself such that it can be readily
>   obtained by a parser. This can be useful for descriptive documents,
>   such as tables of content, which may be transmitted to others through
>   protocols other than their usual retrieval context (e.g., E-Mail or
>   USENET news).
>
>   It is beyond the scope of this document to specify how, for each
>   media type, the base URI can be embedded.

You are misreading the document. For instance, in Appendix E you still
find "Using <> angle brackets around each URI is especially recommended
as a delimiting style for URI that contain whitespace." The text above
is about base URIs (absolute addresses used to resolve relative ones),
an unrelated concept.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

[toc] | [prev] | [next] | [standalone]

#1096

On Fri, 28 Feb 2014 11:24:38 +0000 (UTC)
Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

> In message <lenls5$dao$2@solani.org> 
>   RS Wood <rsw@therandymon.com> wrote:
> >  http://mobile.datamation.com/open-source/nine-lessons-other-deskto
> > ps-can-learn-from-kde-1.html
> 
> It would also be nice if your posting thingy didn't force-wrap URLs.
> 
> -- 
> The Disc, being flat, has no real horizon. Any adventurous sailors who
> get funny ideas from staring at eggs and oranges for too long and set
> out for the antipodes soon learned that the reason why distant ships
> sometimes looked as though they were disappearing over the edge of the
> world was that they were disappearing over the edge of the world. --The
> Light Fantastic

I'll get working on it as soon as your posts are longer than your sig.

[toc] | [prev] | [next] | [standalone]

#1116

In message <20140228134755.f2685339.rsw@therandymon.com> 
  RS Wood <rsw@therandymon.com> wrote:
> On Fri, 28 Feb 2014 11:24:38 +0000 (UTC)
> Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

>> In message <lenls5$dao$2@solani.org> 
>>   RS Wood <rsw@therandymon.com> wrote:
>> >  http://mobile.datamation.com/open-source/nine-lessons-other-deskto
>> > ps-can-learn-from-kde-1.html
>> 
>> It would also be nice if your posting thingy didn't force-wrap URLs.
>> 
>> -- 
>> The Disc, being flat, has no real horizon. Any adventurous sailors who
>> get funny ideas from staring at eggs and oranges for too long and set
>> out for the antipodes soon learned that the reason why distant ships
>> sometimes looked as though they were disappearing over the edge of the
>> world was that they were disappearing over the edge of the world. --The
>> Light Fantastic

> I'll get working on it as soon as your posts are longer than your sig.

Ah, I see, you react poorly to having a problem pointed out to you. Good
plan. Well, at least now I know and shall not waste any more time with
you.

FTR, the signs are randomly attached. Some are long, the vast majority
are short.

-- 
I'd rather have my mind opened by wonder than closed by belief

[toc] | [prev] | [next] | [standalone]

#1097

On Fri, 28 Feb 2014 11:24:38 +0000 (UTC)
Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

> In message <lenls5$dao$2@solani.org> 
>   RS Wood <rsw@therandymon.com> wrote:
> >  http://mobile.datamation.com/open-source/nine-lessons-other-deskto
> > ps-can-learn-from-kde-1.html
> 
> It would also be nice if your posting thingy didn't force-wrap URLs.

To be fair, I agree having to glue URLs back together is annoying and I
don't like it either.  It probably means I won't post any more stuff using the Android RSS reader mechanism, which means I will do less posting as I don't have access to the better method throughout the day.  Not the end of the world!

[toc] | [prev] | [next] | [standalone]

#1104

RS Wood wrote:
> Lewis wrote:
>> RS Wood wrote:
>>> http://mobile.datamation.com/open-source/nine-lessons-other-deskto
>>>
>>>
ps-can-learn-from-kde-1.html

(should have been)
http://mobile.datamation.com/open-source/nine-lessons-other-desktops-can-learn-from-kde-1.html

>> It would also be nice if your posting thingy didn't force-wrap
>> URLs.

> To be fair, I agree having to glue URLs back together is annoying and
> I don't like it either.  It probably means I won't post any more
> stuff using the Android RSS reader mechanism, which means I will do
> less posting as I don't have access to the better method throughout
> the day.  Not the end of the world!

Or alternatively, when you post with the wrapping app, to accompany the 
long URL with a short URL (which has preview functionality) so that the 
reader can choose to either reconstruct the fractured URL or use the 
alternate previewable shortened one.

Some people do that routinely, even when posting with an agent which 
doesn't break URLs, based on the experience that some agents are going 
to be breaking the URL in subsequent quoted exchanges.

I think the two big no-no/s are: posting (only) b0rken URLs and posting 
only shortened URLs which aren't readily previewable, such as requiring 
special handling or a special app to preview shortened into a full URL.



-- 
Mike Easter

[toc] | [prev] | [standalone]

Back to top | Article view | comp.misc

csiph-web