From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: KDE 4.0.4 upgrade, sort of.
Date: Sat, 31 May 2008 15:43:21 +0000 [thread overview]
Message-ID: <d257c3560805310843t605009b7x4ae908a4b1c6d46a@mail.gmail.com> (raw)
In-Reply-To: <pan.2008.05.31.10.24.54@cox.net>
[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]
2008/5/31 Duncan <1i5t5.duncan@cox.net>:
> Beso <givemesugarr@gmail.com> posted
> d257c3560805301217q5af4d9c3rc3ea014a012fe04f@mail.gmail.com, excerpted
> below, on Fri, 30 May 2008 19:17:59 +0000:
>
> > 2008/5/30 Duncan <1i5t5.duncan@cox.net>:
>
> In any case, 4.1 appears to have fixed at least some of the 4.0 blockers,
> including the big one here, the lack of multipanel support and
> configuration, so unless there's something really stupid like that
> missing proxy support (tho it looks like it'll work for me after all),
> there's at least a decent chance I'll find it at least minimally usable,
> now, enough to remerge it and start the task of customizing it to my
> needs and switching my habits to the 4.x methodology, even if I have to
> keep parts of KDE3 around for awhile. That's what I had intended to do
> with 4.0, but it was just too *broken*, too many now vital but missing in
> 4.0 features, to make it work, even for this normally out-in-front
> bleeding edge guy who /loves/ many betas. That's why I say 4.0 was only
> early tech-preview alpha, not even beta, because betas normally have the
> features all there or at least blocked out even if buggy, and 4.0...
> didn't! So 4.1's the first real beta, if it even reaches that. It might
> still be more a late tech preview alpha. Time will tell.
>
or you could just use the kde4 apps in kde3.5. flameeyes has posted a dirty
hack on his blog on how to use kde4 apps from 3.5 environment natively (ie
calling them directly from command line without the full path). you'll just
need the kdebase-meta package and then you could test them out. just one
warning: after installing solid hal would stop mounting stuff on request and
you'd need to work the mounting through dolphin. the device manager handles
the dolphin calls directly in plasma environment. the thing that is
interesting is the ability in plasma to create new workspaces. i think that
the zoom out feature of plasma desktop is meant for that and it should work
out similar to the leopard workspaces. also the widget exposè i think would
work as the osx one, since there's an option to put the widget on a layer
external to the desktop. the thing is that after getting out of the layer
the widget would stay on the visible desktop. the problems still there are
with phonon which doesn't implements enough features yet to be able to port
kaffeine and amarok only through phonon, so these packages devs are still
doing some extra job on that. still, the desktop has now come to be quite
usable.
--
dott. ing. beso
[-- Attachment #2: Type: text/html, Size: 3171 bytes --]
next prev parent reply other threads:[~2008-05-31 15:43 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 10:25 [gentoo-amd64] KDE 4.0.4 upgrade, sort of Mark Haney
2008-05-28 12:10 ` [gentoo-amd64] KDE 4.0.4 upgrade, sort of. [UPDATE] Mark Haney
2008-05-28 12:48 ` [gentoo-amd64] KDE 4.0.4 upgrade, sort of Hemmann, Volker Armin
2008-05-28 12:54 ` Mark Haney
2008-05-28 13:49 ` Hemmann, Volker Armin
2008-05-28 17:59 ` Beso
2008-05-29 17:41 ` Mark Haney
2008-05-29 18:17 ` Hemmann, Volker Armin
2008-05-29 20:53 ` Beso
2008-05-30 12:26 ` Mark Haney
2008-05-30 12:59 ` Beso
2008-05-30 12:59 ` Beso
2008-05-30 13:15 ` Mark Haney
2008-05-30 13:19 ` Beso
2008-05-30 16:40 ` [gentoo-amd64] " Duncan
2008-05-30 19:17 ` Beso
2008-05-31 10:28 ` Duncan
2008-05-31 15:43 ` Beso [this message]
2008-05-31 17:52 ` Duncan
2008-05-31 18:12 ` Beso
2008-05-31 19:01 ` Duncan
2008-05-31 19:18 ` Beso
2008-05-30 20:16 ` Hemmann, Volker Armin
2008-05-30 20:28 ` David Leverton
2008-05-30 20:48 ` Barry Schwartz
2008-05-30 20:51 ` David Leverton
2008-05-30 21:10 ` Hemmann, Volker Armin
2008-05-30 21:16 ` David Leverton
2008-05-30 22:17 ` Hemmann, Volker Armin
2008-05-30 23:16 ` David Leverton
2008-05-31 9:53 ` Hemmann, Volker Armin
2008-05-31 10:08 ` David Leverton
2008-05-31 2:15 ` Richard Freeman
2008-05-31 3:25 ` Avuton Olrich
2008-05-31 8:48 ` Beso
2008-05-31 6:36 ` ionut cucu
2008-05-31 8:31 ` Beso
2008-05-30 21:18 ` Hemmann, Volker Armin
2008-05-30 22:06 ` David Leverton
2008-05-30 23:41 ` Hemmann, Volker Armin
2008-05-30 23:52 ` David Leverton
2008-05-31 2:14 ` Barry Schwartz
2008-05-31 2:20 ` Barry Schwartz
2008-05-31 8:33 ` Beso
2008-05-31 6:34 ` ionut cucu
2008-05-31 9:57 ` Hemmann, Volker Armin
2008-05-31 8:17 ` Duncan
2008-05-31 9:08 ` Beso
2008-05-31 11:40 ` Duncan
2008-05-31 15:53 ` Beso
2008-05-31 18:11 ` Duncan
2008-05-31 18:24 ` Beso
2008-05-31 18:48 ` Duncan
2008-05-31 19:25 ` Hemmann, Volker Armin
2008-05-31 19:34 ` David Leverton
2008-05-31 23:54 ` Duncan
2008-06-01 0:17 ` David Leverton
2008-06-01 7:57 ` Duncan
2008-06-01 1:54 ` Richard Freeman
2008-06-01 7:22 ` Duncan
2008-06-01 11:04 ` Beso
2008-06-01 18:59 ` Hemmann, Volker Armin
2008-06-02 10:51 ` Beso
2008-06-02 11:11 ` ionut cucu
2008-06-02 12:59 ` Mark Haney
2008-06-02 13:45 ` Beso
2008-06-02 14:09 ` Mark Haney
2008-06-02 16:35 ` Beso
2008-06-01 8:05 ` Duncan
2008-05-31 8:26 ` Beso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d257c3560805310843t605009b7x4ae908a4b1c6d46a@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox