E17 is coming?? (Part 1)

[StinkingMonkey]

yeah you can emerge it , you have to add

x11-wm/e -*

to package.keywords. Remember e17 is still undergoing testing though and there isnt that much functionality, though if you want to see what it looks like by all means emerge it. Read this topic throughout though. Looks bloomin' nice though .

[hoschi]

sorry, stupid question
when will e17 finally release, spring 2005/summer 2005?

i dont want a exatly date, just a info

[jxn]

sorry, stupid question
when will e17 finally release, spring 2005/summer 2005?

the e team don't set release dates. "it's done when it's done."

typical. they're artists, not programmers.

[Fran]

I've just emerged it (zero problems on amd64 ) and.... I wish I hadn't done it. Now my FVWM looks like crap .

God, I can hardly wait till it's finished.

[nsahoo]

sorry, stupid question
when will e17 finally release, spring 2005/summer 2005?

the e team don't set release dates. "it's done when it's done."

typical. they're artists, not programmers.

i agree. very different style of managing a project. a little weird and interesting at the same time

[MusclePup]

This is the future of linux Yummm it looks good.

[Jengu]

Certainly not the past though. The fade effect for entrance alone is sluggish on my rage128...

[jxn]

Certainly not the past though. The fade effect for entrance alone is sluggish on my rage128...

really? odd. the new entrance cvs runs like an oiled ferrett through a tailpipe on my laptop which has some sort of really crappy generic old motherboard video support (the machine's 5 or 6 years old by now, at least). Are you using gl mode or something?

e17 still lags a little here 'n there, (dragging windows gives me a neat little trailing effect), but entrance renders everything realitime.

[Swoosh]

esmart-9999 doesn't compile for me (x86)

make[4]: *** [esmart_text_entry.lo] Error 1
make[4]: Leaving directory `/var/tmp/portage/esmart-9999/work/e17/libs/esmart/sr
c/lib/esmart_text_entry'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/esmart-9999/work/e17/libs/esmart/sr
c/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/esmart-9999/work/e17/libs/esmart/sr
c'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/esmart-9999/work/e17/libs/esmart/sr
c'
make: *** [all-recursive] Error 1
* This is a LIVE CVS ebuild.
* That means there are NO promises it will work.
* If it fails to build, FIX THE CODE YOURSELF
* before reporting any issues.

[u2mike]

Lol, I´ĺl skip the cvs on this one and wait for a final, we´ve waited a lifetime allready, a few more months will seem like nothing

[ebrostig]

It looks good and I'm sure it will be good when done (sometimes after the release of Duke Nukem Forever ).

However it is not a product ready to be used other as a demo of what is to come. If you acn emerge it and enjoy the eyecandy, have fun, but don expect to be able to do too much with it yet.

Erik

[nighty]

ive been following the project regulary. hopefully it was worth the wait and wont have the classical downfalls E16 has that "lesser" window managers like the *boxes dont have.

[jxn]

ive been following the project regulary. hopefully it was worth the wait and wont have the classical downfalls E16 has that "lesser" window managers like the *boxes dont have.

...such as?

[nighty]

if youve got the time to mess with E youll notice a few basic shortcomings. it has relatively poor configuration and documention. and its not as easilly extensive as other wms out there. E17 had no documention what so ever and it has binary config files which make no sense to me at least. but hey its still in alpha.

[vrln]

if youve got the time to mess with E youll notice a few basic shortcomings. it has relatively poor configuration and documention. and its not as easilly extensive as other wms out there. E17 had no documention what so ever and it has binary config files which make no sense to me at least. but hey its still in alpha.

It´s propably not even alpha yet (why should there be documentation at all at this stage?), although it is fairly usable already. I´ve been using e17 only for weeks already.

About your documentation concerns:

That´s why me, gimpel and some others from #edocumentation decided to help :) I see you haven´t read the entire thread so you missed this:

http://lude.net/edocs/

And this is about the binary config files question:

http://lude.net/edocs/eet_edb.htm

(no, I don´t really claim to understand why they chose binary config files of course, but I´m sure raster & co know what they´re doing)

E17 has a nice module architecture, so it can be as minimal or as bloated as you want it to be.

[nighty]

many thanks for the links.

[outspoken]

when i first started using a graphical linux i was using enlightenment, that was the most amazing desktop environment i had ever used at the time - with the nIx theme from litestep (i was using litestep with windows 2000 at the time as well). currently i am using fluxbox and when e17 is final i plan to give it a shot and would like to try porting over the nIx theme, cant wait!

[_SkeLeToN_]

Hi,

I was trying to get e17 cvs working (not using ebuilf) and I ran into a problem with evas.

I always get this error.

Code: Select all

gcc -I/opt/e17/include -o .libs/evas_software_x11_test evas_software_x11_test-evas_test_main.o evas_software_x11_test-evas_software_x11_main.o  -L/opt/e17/lib ../../src/lib/.libs/libevas.so /usr/lib/libfreetype.so -lpng -lz /usr/lib/libjpeg.so -L/usr/X11R6/lib -L/usr/lib32 -L/usr/lib /usr/lib/libGLU.so /usr/lib/opengl/nvidia/lib/libGL.so -lSM -lICE -lXmu -lXt -lXi -ldl -lpthread -lm -lX11 -lXext -Wl,--rpath -Wl,/opt/e17/lib -Wl,--rpath -Wl,/usr/lib/opengl/nvidia/lib
../../src/lib/.libs/libevas.so: undefined reference to `eet_data_image_header_read'
../../src/lib/.libs/libevas.so: undefined reference to `eet_data_image_read'
../../src/lib/.libs/libevas.so: undefined reference to `e_db_open_read'
../../src/lib/.libs/libevas.so: undefined reference to `eet_read'
../../src/lib/.libs/libevas.so: undefined reference to `eet_shutdown'
../../src/lib/.libs/libevas.so: undefined reference to `eet_close'
../../src/lib/.libs/libevas.so: undefined reference to `e_db_close'
../../src/lib/.libs/libevas.so: undefined reference to `eet_init'
../../src/lib/.libs/libevas.so: undefined reference to `eet_open'
../../src/lib/.libs/libevas.so: undefined reference to `e_db_data_get'
collect2: ld returned 1 exit status
make[4]: *** [evas_software_x11_test] Error 1
make[4]: Leaving directory `/home/hlacroix/cvs/e17/libs/evas/src/bin'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/hlacroix/cvs/e17/libs/evas/src/bin'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/hlacroix/cvs/e17/libs/evas/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/hlacroix/cvs/e17/libs/evas'
make: *** [all] Error 2

A friend of mine pull cvs around sametime and its working for him. not sure why.

I have both automake autoconf set.
[code[
WANT_AUTOCONF=2.5
WANT_AUTOMAKE=1.7
[/code]

Gcc version

Code: Select all

Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/specs
Configured with: /var/tmp/portage/gcc-3.3.4-r1/work/gcc-3.3.4/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/info --enable-shared --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,f77 --enable-threads=posix --enable-long-long --disable-checking --disable-libunwind-exceptions --enable-cstdio=stdio --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/g++-v3 --with-local-prefix=/usr/local --enable-shared --enable-nls --without-included-gettext --disable-multilib --enable-__cxa_atexit --enable-clocale=generic
Thread model: posix
gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)

[AnXa]

I've just emerged it (zero problems on amd64 ) and.... I wish I hadn't done it. Now my FVWM looks like crap .

God, I can hardly wait till it's finished.

Any successful builds on amd64 when building 64BIT BINARIES on 64BIT GENTOO? Thanks.

[feardapenguin]

Lol, I´ĺl skip the cvs on this one and wait for a final, we´ve waited a lifetime allready, a few more months will seem like nothing

A few more months? It'll be longer than that. Someone earlier joked about 2006. I bet we don't see a release candidate before that.

Nothing against Rasterman and company but this is the longest development life cycle I've ever seen for something as mundane as a desktop/window manager project. It may have been cutting-edge when it started, but...

<Rant mode disabled>

[mcdermottpa]

Lol, I´ĺl skip the cvs on this one and wait for a final, we´ve waited a lifetime allready, a few more months will seem like nothing

A few more months? It'll be longer than that. Someone earlier joked about 2006. I bet we don't see a release candidate before that.

Nothing against Raster and company but this is the longest development life cycle I've ever seen for something as mundane as a desktop/window manager project. It may have been cutting-edge when it started, but...

<Rant mode disabled>

I was in high school when I first heard "E17" and now I should be thinking about grad school.

[qtothemax]

To the people who can't get it to build...
I tried it using GCC 3.4 (~x86), which kept failing no matter what I did. GCC 3.3 worked, so that could be the cause of the problem for some of you.

[Fran]

I've just emerged it (zero problems on amd64 ) and.... I wish I hadn't done it. Now my FVWM looks like crap .

God, I can hardly wait till it's finished.

Any successful builds on amd64 when building 64BIT BINARIES on 64BIT GENTOO? Thanks.

You don't have to shout , I'm in x86-64 (look at my signature) and without multilib support. And yes, E17 worked ok. No problems emerging it or using it.

[Motoi-Sakuraba-Milfeuille]

so enlightenment 17 is finally starting to show itself! wow.... after I just compiled 16.7.2 too.... I"ve been waiting for 17 for years!!

[codezero]

I got an error when i compiled e17 from portage so i tried it from cvs.
But i get another error. This is what i got when compiling the last library 'ewl':

Code: Select all

../src/.libs/libewl.so: undefined reference to `ECORE_FB_EVENT_KEY_UP'
../src/.libs/libewl.so: undefined reference to `ECORE_FB_EVENT_MOUSE_BUTTON_DOWN'
../src/.libs/libewl.so: undefined reference to `ecore_fb_init'
../src/.libs/libewl.so: undefined reference to `ECORE_FB_EVENT_MOUSE_MOVE'
../src/.libs/libewl.so: undefined reference to `ecore_fb_shutdown'
../src/.libs/libewl.so: undefined reference to `ECORE_FB_EVENT_MOUSE_BUTTON_UP'
../src/.libs/libewl.so: undefined reference to `ECORE_FB_EVENT_KEY_DOWN'
collect2: ld returned 1 exit status
make[2]: *** [ewl_test] Fout 1
make[2]: Leaving directory `/home/codezero/e17/libs/ewl/test'
make[1]: *** [all-recursive] Fout 1
make[1]: Leaving directory `/home/codezero/e17/libs/ewl'
make: *** [all] Fout 2

I thought i forgot to compile the library 'ecore' so i recompiled it etc. but it doesn't help.
Can someone help me with this please?