| 1 |
Generally, that's true - as long as you have a PC with enough resources to |
| 2 |
handle everything. There are several considerations for wanting to stick |
| 3 |
to applications that are designed for a particular environment: |
| 4 |
|
| 5 |
1) Gnome and KDE make use of a rather large stack of runtime libraries that |
| 6 |
remain resident. If you are running a Gnome desktop and start up a KDE |
| 7 |
application, the first thing that happens is the stack of libraries for KDE |
| 8 |
loads up into the system and remain resident until you restart the X |
| 9 |
server. This requires a significant amount of resources. Same thing if you |
| 10 |
are running KDE and start up a Gnome application. |
| 11 |
|
| 12 |
2) Each environment has a number of dependencies. If you only have one |
| 13 |
environment installed, installing an application for the other requires that |
| 14 |
you also install all those libraries and dependencies. Maybe not a major |
| 15 |
issue for some, but a consideration none-the-less. |
| 16 |
|
| 17 |
3) Consistency. The desktop environment that the application is designed |
| 18 |
for has an impact on the application's interface, appearance, etc. Gnome |
| 19 |
and KDE even have slightly different paradigms for working with the |
| 20 |
clipboard. Yes, you can do some tweaking to get them to act consistent in |
| 21 |
some cases, but it's not as simple as using an application built for your |
| 22 |
chosen environment. |
| 23 |
|
| 24 |
I *do* see your point, and I generally follow it myself. I prefer the |
| 25 |
gnuStep environment myself, but the application selection for it is dismal, |
| 26 |
so I am usually in Gnome. Even with that, I also use a couple of KDE |
| 27 |
applications (k3b for one) simply because I require the features they have. |
| 28 |
But, then, I have a pretty beefy PC. |
| 29 |
|
| 30 |
.... HH |
| 31 |
|
| 32 |
|
| 33 |
On 1/10/07, b.n. <brullonulla@×××××.com> wrote: |
| 34 |
> |
| 35 |
> Lindsay Haisley ha scritto: |
| 36 |
> > even on Gnome, though |
| 37 |
> > it's primarily a KDE utililty. I'm just looking for a simple, solid CD |
| 38 |
> player |
| 39 |
> > UI that understands CDDB lookups, local and remote. |
| 40 |
> |
| 41 |
> In fact, I don't understand all this constant "I'm running Gnome/KDE so |
| 42 |
> I want a Gnome/KDE app" that is constant between Linux/Unix users. |
| 43 |
> Gnome-GTK and KDE apps work fine together. Why having to fuss for |
| 44 |
> wanting an app built with one toolkit instead of the other? Isn't |
| 45 |
> important that the app gets the job done? |
| 46 |
> |
| 47 |
> m. |
| 48 |
> |
| 49 |
> -- |
| 50 |
> gentoo-desktop@g.o mailing list |
| 51 |
> |
| 52 |
> |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
Harry Holt, PMP |
Archives