1 |
On Monday 01 March 2010 22:28:42 Mick wrote: |
2 |
> > My pet peeve is Desktop. I have two monitors at work and use two X |
3 |
> > screens. KDE wants to create a Desktop and a Desktop-1 directory. I want |
4 |
> > it to just |
5 |
> > |
6 |
> > use the same set of files for both - background, icons, plasma widgets |
7 |
> > must be the same on both monitors, but actual app windows running there |
8 |
> > independent. This seems perfectly reasonable to me - e17 does it out the |
9 |
> > box - but thus far I have not found the magic voodoo spell that makes it |
10 |
> > happen. |
11 |
> |
12 |
> How does e17 compare in terms of resources to other WMs/DEs like *box, |
13 |
> LXDE, xface, these days? I had a look at it when it was all the rage |
14 |
> back when, but it looked too Gnomey to me at the time and I couldn't find |
15 |
> a reason for preferring it over say fluxbox. |
16 |
|
17 |
As of right now, I really couldn't say. About 6 months ago the e17 devs |
18 |
started ramping up for a release that was supposed to happen round about last |
19 |
xmas. Then Samsung and a French manufacturer of set-top boxes got in on the |
20 |
action, as a result the code changes faster than Paris Hilton changes her |
21 |
knickers. It stopped reliably building from one hour to the next ... :-) |
22 |
|
23 |
So I switched to KDE to get some stability and haven't tried again since. |
24 |
|
25 |
e17 has to be evaluated on it's own merits, like all other software. it's not |
26 |
"like" anything ... except perhaps e17 itself. It's claims to fame are |
27 |
twofold: |
28 |
|
29 |
1. Themeability. If you have every written a KDE or Gnome theme engine you |
30 |
will know what a serious ball-ache it is. Code mixed in with specs mixed in |
31 |
with image files.... e17 does it a different way with .edj files. You write an |
32 |
.edc spec file in a declarative style (as in you say *what* you want, not |
33 |
*how* it is done - that's the engine's job to figure that out) and supply your |
34 |
images to be used on the widgets. Then run it through a mini-compiler to |
35 |
produce an .edj, tell the wm to use it and voila! theme applied. It's not just |
36 |
a simple "replace all those .pngs with these .pngs" to get a different set of |
37 |
colours - you change the entire look and feel of the desktop and the engine |
38 |
just knows what to do with it. |
39 |
|
40 |
2. Configurability. Everything that can possibly be changeable is so, |
41 |
including stuff that really shouldn't be :-) It makes KDE look minimalist. |
42 |
Fortunately, a lot of the advanced stuff can be hidden in the config dialog |
43 |
which improves things. |
44 |
|
45 |
Resources - it's hard to write a wm these days that isn't a resource hog in |
46 |
some ways. If you want transparency and composition, be prepared to sell some |
47 |
cpu to get it. Having said that, e17 runs blindingly fast on ARM mobile |
48 |
devices when configured appropriately. It's nowhere near as minimalist as |
49 |
*box, those wm's are in a class where if they suit your needs, then nothing |
50 |
else will come close, especially not e17 which is designed to showcase graphic |
51 |
effects to a large degree. *box is the polar opposite of that |
52 |
|
53 |
-- |
54 |
alan dot mckinnon at gmail dot com |