E17 is coming?? (Part 2)

[CitizenErased]

Hi,

I just installed e17 and liking it a lot.
Previously I was running gnome as used this link to enable japanese input:
http://forums.gentoo.org/viewtopic-t-263174.html
I'm wondering if anyone has been able to get input running in e17 yet?

Thanks
Tony

[vrln]

Hey vrln...

You lately updated the FAQ on get-e.org, but there is a thing i still don't understand.

You wrote:

E17 does real transparency without any special X.org extensions like composite

and later on:

In order to have a transparent window that shows the background layer behind it, you would need to use the X.org composite extension, which is not supported by E17 at this point.

?


So, if i want real transparency for my urxvt for example, what do i have to do now?
I know how to set up fake transparency with e17setroot... but what about real transparency, which should be build in?

"E17 does real transparency without any special X.org extensions like composite, within the same canvas, but it does not do transparency between multiple windows for example. In other words, modules that render to the background layer can have real transparency, but it's only for the background layer. It's impossible to have a module (the IBar or Engage for example) be "above" a window, and show the contents of the window via transparency. It is possible to have an EFL application that does real transparency within its window - for example if you drag an icon, the icon may be transparent to the other content inside the same window. Same goes to modules. "

I agree it's a bit unclearly said, I'll rewrite it later today. The important part is the first line - E17 real transparency only works within the same canvas. A canvas can be the background layer or a single window. E17 cannot mix these canvases in any way. An EFL application that displays many boxes etc running inside one window may be transparent, but NOT to the background layer (just anything inside the window can be transparent to anything else running inside the window). The same model applies to the background layer. This is why you can never have Engage be over a window for example.

E17 cannot do real transparency between two windows, it's limited to a single canvas, the "drawing area". Real transparency between windows (for example a transparent terminal) would require compositing, which is something that cannot be done with the Xorg composite extension, which E17 does NOT support right now (you can still enable it and use xcompmgr/transset though... works here at least, but your mileage may vary).

Quick answer: you cannot get that type of real transparency for your terminal in E17. Only fake transparency. If someone would write a terminal program with EFL, that would render to the background layer, that would be just as transparent as the other modules, but you could never have something like that inside a window that displays other windows/the background via transparency.

[saty]

Ok... thx a lot. (pithlit and vrln)


So I'll give fake transparency a try, for my term.

Are there plans for inter-module/canvas/whatever-transparency?

[ppurka]

E17 cannot do real transparency between two windows, it's limited to a single canvas, the "drawing area". Real transparency between windows (for example a transparent terminal) would require compositing, which is something that cannot be done with the Xorg composite extension, which E17 does NOT support right now (you can still enable it and use xcompmgr/transset though... works here at least, but your mileage may vary).

Perhaps this link illustrates what vrln wanted to clarify.

[vrln]

Ok... thx a lot. (pithlit and vrln)


So I'll give fake transparency a try, for my term.

Are there plans for inter-module/canvas/whatever-transparency?

Modules can all be "really transparent", as they all render to the "background layer" anyway. Inter-canvas/window transparency is, in practise, impossible technology wise, without compositing. There's no way E17 can "know" what's inside the windows, it doesn't control that. If E17 supported the composite extension, this would be possible. There may be composite (the new xorg extension) support in the future (if not in E17, perhaps in E18), but not until it's fast/stable enough. I'm not the right person to ask this question though.

Anyways, what I meant with the "not until it's fast/stable enough", is that for example currently E17's dropshadows are miles faster than anything you can do with composite.

[insertfunkhere]

you CAN, however, run composite with E17, and it looks very nice, with all the real transparency your heart could desire - you just have to use transset and xcompmgr, there's no way to set it up within E17. Problem is, the composite extension itself isn't too stable, and doesn't play nice with some apps. For example, i use nedit for simple gui text editing, and with composite enabled, the text in a nedit wiindow will repeat over and over when you scroll, only revealing the true content when you highlight it - until you dare use the scrollbar again. I can definitely understand why raster, et. al don't plan on adding composite support for a while.

[saty]

Much more clearer now guys... thanks for enlightening.

It was just pure interest in understanding the facts.

Indeed i find transparency for most windows not very usable... except for terms with some shading/tinting.
Or for window-borders maybe, like it was (is) possible in E16. (... with fake transparency.)

[Pithlit]

...snip... the new xorg extension) support in the future (if not in E17, perhaps in E18), ...snip...

Please don't start with E18 just yet... you're gonna make people wonder (considering the gap between E16 and E17)

[jxn]

Please don't start with E18 just yet... you're gonna make people wonder (considering the gap between E16 and E17) [/quote]
Yeah, speaking of that gap... I wonder when we'll finally get a beta from e17?

[CitizenErased]

Well I just followed the same instructions as for gnome and the input bar has appeared at the end of my engage bar

Tony.

Hi,

I just installed e17 and liking it a lot.
Previously I was running gnome as used this link to enable japanese input:
http://forums.gentoo.org/viewtopic-t-263174.html
I'm wondering if anyone has been able to get input running in e17 yet?

Thanks
Tony

[Pithlit]

jxn: NEVER! Its gonna go straight from CVS to release. /me giggles

I don't think any e17 users care for a beta or anything else. It's running stable for most people as it is.

[vrln]

jxn: NEVER! Its gonna go straight from CVS to release. /me giggles

I don't think any e17 users care for a beta or anything else. It's running stable for most people as it is.

Agreed - personally I don't care that much about a release, except I do hope one so that EFL would become more popular, but other than that, I'm fine with things as they are now.

[slugworth]

Do the backgrounds on get-e.org animate? or is there just one that animates, the firey-brush looking one.

i want an e background like the ones that have that slowly animates so it takes time to notice.

[gimpel]

Do the backgrounds on get-e.org animate? or is there just one that animates, the firey-brush looking one.

i want an e background like the ones that have that slowly animates so it takes time to notice.

see the discriptions there.... 'White', 'Shiny reflection' and 'Layered sky' are animated, also one guy posted a nice one with a spinning dna on forum here and edevelop.org/forum

[JoeG]

Do the backgrounds on get-e.org animate? or is there just one that animates, the firey-brush looking one.

i want an e background like the ones that have that slowly animates so it takes time to notice.

You can find out how to make your own here. You can even use the cheesy one I made .

Enjoy.

[linerminator]

i just have to say...
i just installed e17, and im amazed! seems to be just the perfect combination of great looks and functionality, at least as far as im concerned.
from what ive read, theres no official release date, but maybe you have some more accurate info?

regards

[saty]

but maybe you have some more accurate info?

regards

Just check some signatures here...

http://get-e.org

[cuciferus]

Code: Select all

akefile.am:1: `intl' should not be in SUBDIRS when AM_GNU_GETTEXT([external]) is used
src/bin/Makefile.am: installing `./depcomp'
Makefile.am:1: `intl' should not be in SUBDIRS when AM_GNU_GETTEXT([external]) is used
Generating gettext enlightenment.pot template
Unrecognized option: C

usage: xgettext [-adnuv] [-c<flag>] [-m<tag>] [-o<default>]
            ... [-p<path>] [-x<xlist>] - | file
       xgettext -h (HELP)
enlightenment: No such file or directory

This is happening for a week now from cvscompiling e...i remove the cvs-src/ dir and again and nothing tried the exoprt and autogen part and still the same....do u have any ideas?

[Cinder6]

Is there a problem with the current CVS? Getting this error, which makes me very sad. Very much want to try E17!

Code: Select all

In file included from e_includes.h:14,
                 from e.h:82,
                 from e_user.c:4:
e_border.h:220: error: parse error before "Ecore_X_Sync_Alarm"
e_border.h:220: warning: no semicolon at end of struct or union
e_border.h:220: warning: no semicolon at end of struct or union
e_border.h:221: warning: no semicolon at end of struct or union
e_border.h:221: warning: no semicolon at end of struct or union
e_border.h:224: error: parse error before '}' token
e_border.h:224: error: 'sync' redeclared as different kind of symbol
/usr/include/gentoo-multilib/amd64/unistd.h:879: error: previous declaration of 'sync' was here
e_border.h:224: error: 'sync' redeclared as different kind of symbol
/usr/include/gentoo-multilib/amd64/unistd.h:879: error: previous declaration of 'sync' was here
e_border.h:224: warning: data definition has no type or storage class
e_border.h:261: error: parse error before '}' token
e_border.h:261: warning: data definition has no type or storage class
e_border.h:263: error: parse error before '}' token
e_border.h:263: warning: data definition has no type or storage class
e_border.h:267: error: parse error before ':' token
e_border.h:268: error: parse error before ':' token
e_border.h:269: error: parse error before ':' token
e_border.h:270: error: parse error before ':' token
e_border.h:271: error: parse error before ':' token
e_border.h:272: error: parse error before ':' token
e_border.h:273: error: parse error before ':' token
e_border.h:274: error: parse error before ':' token
e_border.h:275: error: parse error before ':' token
e_border.h:276: error: parse error before ':' token
e_border.h:277: error: parse error before ':' token
e_border.h:278: error: parse error before ':' token
e_border.h:279: error: parse error before ':' token
e_border.h:280: error: parse error before ':' token
e_border.h:281: error: parse error before ':' token
e_border.h:282: error: parse error before ':' token
e_border.h:283: error: parse error before ':' token
e_border.h:284: error: parse error before ':' token
e_border.h:285: error: parse error before ':' token
e_border.h:286: error: parse error before ':' token
e_border.h:287: error: parse error before ':' token
e_border.h:288: error: parse error before ':' token
e_border.h:289: error: parse error before ':' token
e_border.h:290: error: parse error before ':' token
e_border.h:293: error: parse error before ':' token
e_border.h:294: error: parse error before ':' token
e_border.h:295: error: parse error before ':' token
e_border.h:296: error: parse error before ':' token
e_border.h:297: error: parse error before ':' token
e_border.h:298: error: parse error before ':' token
e_border.h:299: error: parse error before ':' token
e_border.h:300: error: parse error before ':' token
e_border.h:301: error: parse error before ':' token
e_border.h:302: error: parse error before ':' token
e_border.h:303: error: parse error before ':' token
e_border.h:304: error: parse error before ':' token
e_border.h:305: error: parse error before ':' token
e_border.h:306: error: parse error before ':' token
e_border.h:307: error: parse error before ':' token
e_border.h:308: error: parse error before ':' token
e_border.h:309: error: parse error before ':' token
e_border.h:310: error: parse error before ':' token
e_border.h:311: error: parse error before ':' token
e_border.h:312: error: parse error before ':' token
e_border.h:313: error: parse error before ':' token
e_border.h:314: error: parse error before ':' token
e_border.h:315: error: parse error before ':' token
e_border.h:316: error: parse error before ':' token
e_border.h:320: error: parse error before ':' token
e_border.h:375: error: parse error before '}' token
e_border.h:496: error: parse error before "alarm"
make[3]: *** [e_user.o] Error 1
make[3]: *** Waiting for unfinished jobs....

Then it quits.

[vrln]

Is there a problem with the current CVS? Getting this error, which makes me very sad. Very much want to try E17!

Code: Select all

In file included from e_includes.h:14,
                 from e.h:82,
                 from e_user.c:4:
e_border.h:220: error: parse error before "Ecore_X_Sync_Alarm"
e_border.h:220: warning: no semicolon at end of struct or union
e_border.h:220: warning: no semicolon at end of struct or union
e_border.h:221: warning: no semicolon at end of struct or union
e_border.h:221: warning: no semicolon at end of struct or union
e_border.h:224: error: parse error before '}' token
e_border.h:224: error: 'sync' redeclared as different kind of symbol
/usr/include/gentoo-multilib/amd64/unistd.h:879: error: previous declaration of 'sync' was here
e_border.h:224: error: 'sync' redeclared as different kind of symbol
/usr/include/gentoo-multilib/amd64/unistd.h:879: error: previous declaration of 'sync' was here
e_border.h:224: warning: data definition has no type or storage class
e_border.h:261: error: parse error before '}' token
e_border.h:261: warning: data definition has no type or storage class
e_border.h:263: error: parse error before '}' token
e_border.h:263: warning: data definition has no type or storage class
e_border.h:267: error: parse error before ':' token
e_border.h:268: error: parse error before ':' token
e_border.h:269: error: parse error before ':' token
e_border.h:270: error: parse error before ':' token
e_border.h:271: error: parse error before ':' token
e_border.h:272: error: parse error before ':' token
e_border.h:273: error: parse error before ':' token
e_border.h:274: error: parse error before ':' token
e_border.h:275: error: parse error before ':' token
e_border.h:276: error: parse error before ':' token
e_border.h:277: error: parse error before ':' token
e_border.h:278: error: parse error before ':' token
e_border.h:279: error: parse error before ':' token
e_border.h:280: error: parse error before ':' token
e_border.h:281: error: parse error before ':' token
e_border.h:282: error: parse error before ':' token
e_border.h:283: error: parse error before ':' token
e_border.h:284: error: parse error before ':' token
e_border.h:285: error: parse error before ':' token
e_border.h:286: error: parse error before ':' token
e_border.h:287: error: parse error before ':' token
e_border.h:288: error: parse error before ':' token
e_border.h:289: error: parse error before ':' token
e_border.h:290: error: parse error before ':' token
e_border.h:293: error: parse error before ':' token
e_border.h:294: error: parse error before ':' token
e_border.h:295: error: parse error before ':' token
e_border.h:296: error: parse error before ':' token
e_border.h:297: error: parse error before ':' token
e_border.h:298: error: parse error before ':' token
e_border.h:299: error: parse error before ':' token
e_border.h:300: error: parse error before ':' token
e_border.h:301: error: parse error before ':' token
e_border.h:302: error: parse error before ':' token
e_border.h:303: error: parse error before ':' token
e_border.h:304: error: parse error before ':' token
e_border.h:305: error: parse error before ':' token
e_border.h:306: error: parse error before ':' token
e_border.h:307: error: parse error before ':' token
e_border.h:308: error: parse error before ':' token
e_border.h:309: error: parse error before ':' token
e_border.h:310: error: parse error before ':' token
e_border.h:311: error: parse error before ':' token
e_border.h:312: error: parse error before ':' token
e_border.h:313: error: parse error before ':' token
e_border.h:314: error: parse error before ':' token
e_border.h:315: error: parse error before ':' token
e_border.h:316: error: parse error before ':' token
e_border.h:320: error: parse error before ':' token
e_border.h:375: error: parse error before '}' token
e_border.h:496: error: parse error before "alarm"
make[3]: *** [e_user.o] Error 1
make[3]: *** Waiting for unfinished jobs....

Then it quits.

Recompile all EFL/E17 in the correct order.

[JoeG]

Is there a problem with the current CVS?

Recompile all EFL/E17 in the correct order.

For an easy way to recompile in the correct order, check mazirian's e17-pkg script on page 6 of this very thread. Hasn't failed me yet!

[vrln]

Is there a problem with the current CVS?

Recompile all EFL/E17 in the correct order.

For an easy way to recompile in the correct order, check mazirian's e17-pkg script on page 6 of this very thread. Hasn't failed me yet!

I see little reason to use any script for that in gentoo, especially when you can just:

emerge eet db imlib2 evas ecore epeg epsilon embryo edje esmart emotion etox ewl e engrave e_utils e_modules engage entice elicit eclair

[JoeG]

I see little reason to use any script for that in gentoo, especially when you can just:

emerge eet db imlib2 evas ecore epeg epsilon embryo edje esmart emotion etox ewl e engrave e_utils e_modules engage entice elicit eclair

You never typo? Personally, I do. Lots. Besides, it's easier to remember than which packages, and in which order, to update. There's more'n one way to skin a cat. I'm just trying to point out an easier way. All I do now is:

Code: Select all

e17-pkg update

[vrln]

I see little reason to use any script for that in gentoo, especially when you can just:

emerge eet db imlib2 evas ecore epeg epsilon embryo edje esmart emotion etox ewl e engrave e_utils e_modules engage entice elicit eclair

You never typo? Personally, I do. Lots. Besides, it's easier to remember than which packages, and in which order, to update. There's more'n one way to skin a cat. I'm just trying to point out an easier way. :D All I do now is:

Code: Select all

e17-pkg update

I have that line in emerge.txt in my home directory :P

[JoeG]

I have that line in emerge.txt in my home directory

So, you cheat too.