E17 is coming?? (Part 2)

Message

slackthumbz · Post by **slackthumbz** » Wed Jun 01, 2005 2:12 pm

is it actually possible to use enlightenment remote to display a list of all the modules that are available BUT NOT LOADED. I'm sitting here with the manual in front of me and it appears that there is no way to get a comprehensive list of all the modules installed on my system... how the hell is a user supposed to know what modules they ca or cannot use if there is no facility to find out?!

Edit: One way is to use

Code: Select all

 slocate modules | grep enlightenment | less

and that'll give a pretty comprehensive list of anything involving e17 modules

Pithlit · Post by **Pithlit** » Fri Jun 03, 2005 1:42 am

Code: Select all

enlightenment_remote -module-dirs-list

tells you what folders e looks in for modules. Just list them to find out anything of use.

*edit* your way isn't exactly good since one can have user defined module paths (i.e. /wuba/buba/) so your "slocate module" would miss it by far

. But as long as one keeps the default settings it's all dandy

.

broeman · Post by **broeman** » Fri Jun 03, 2005 7:10 am

I wish there were a way to disable keybindings or keyevents. Since it was implemented I didn't have the possibility to use ALT together with keys, e.g. I cannot make at-signs, explamationmarks and so on, since they require ALT on my Danish keyboard.

Anybody else had this problem? It only happens in e17, and all applications are "blocked"

Archangel1 · Post by **Archangel1** » Fri Jun 03, 2005 8:28 am

slackthumbz wrote:is it actually possible to use enlightenment remote to display a list of all the modules that are available BUT NOT LOADED. I'm sitting here with the manual in front of me and it appears that there is no way to get a comprehensive list of all the modules installed on my system... how the hell is a user supposed to know what modules they ca or cannot use if there is no facility to find out?!

Edit: One way is to use
Code: Select all
 slocate modules | grep enlightenment | less 
and that'll give a pretty comprehensive list of anything involving e17 modules

What's wrong with "ls /usr/lib/enlightenment/modules"? All of mine are in there.

pjesi · Post by **pjesi** » Sun Jun 05, 2005 9:10 pm

Esmart_Trans Error: Could not read root window pixmap property!
Esmart_Trans Error: Cannot create transparency pixmap: no valid wallpaper and no background color set.
am a system tray

I get this when I run engage. I have background by the way.

e-Gor · Post by **e-Gor** » Sun Jun 05, 2005 9:33 pm

Use the engage module, not the standalone one

Emerge e_modules, and use enlightenment_remote to load the module. Then add icons to it the same way as you would for the ibar or favourites.

You're getting that error because e17 handles the background differently to most window managers, so pseudo transparency (which the standalone engage uses) doesn't work. If you want to use pseudo transparent apps, use Esetroot to set the root background to the same as your current background.

Pithlit · Post by **Pithlit** » Sun Jun 05, 2005 10:24 pm

Archangel1 wrote:
slackthumbz wrote:is it actually possible to use enlightenment remote to display a list of all the modules that are available BUT NOT LOADED. I'm sitting here with the manual in front of me and it appears that there is no way to get a comprehensive list of all the modules installed on my system... how the hell is a user supposed to know what modules they ca or cannot use if there is no facility to find out?!

Edit: One way is to use
Code: Select all
 slocate modules | grep enlightenment | less 
and that'll give a pretty comprehensive list of anything involving e17 modules
What's wrong with "ls /usr/lib/enlightenment/modules"? All of mine are in there.

What's wrong with that is that it won't show any modules that you get with e_modules (they are in /usr/lib/enlightenment/modules_extra/) not to mention any possible custom modules that one might have put elsewhere.

pjesi · Post by **pjesi** » Sun Jun 05, 2005 11:13 pm

Is there any way to let window focus on click other than the titlebar?

[edit] And the cursor changes over to xorg cursor when not in e* app.

gimpel · Post by **gimpel** » Sun Jun 05, 2005 11:19 pm

pjesi wrote:Is there any way to let window focus on click other than the titlebar?

[edit] And the cursor changes over to xorg cursor when not in e* app.

focus on click somehow doesn't work right atm. the guys work on it...

and xcursor...well, make the e17 cursor a x cursor theme, and use that

oh, and if you do so, please link it here, hehe. i want it too then

pjesi · Post by **pjesi** » Sun Jun 05, 2005 11:29 pm

gimpel wrote:
and xcursor...well, make the e17 cursor a x cursor theme, and use that

oh, and if you do so, please link it here, hehe. i want it too then

That sounds cool.

ashtophet · Post by **ashtophet** » Mon Jun 06, 2005 7:52 am

About the xcursor, you can use yr. xcursor theme also when in e17 by copying over the pointer.png before compiling/installing e17... I do it because i like so much the xcursor's theme i use (pGentoo from kdelook or gnomelook, i don't remember).

cheers

tdi · Post by **tdi** » Mon Jun 06, 2005 5:22 pm

engage module crashed whole x server. do you also have it ?

Pithlit · Post by **Pithlit** » Mon Jun 06, 2005 5:40 pm

Update Engage. Actually update everything. Major changes in ecore. And btw, apparently there's a new building order. Check Get-E.org for it. I'm compiling with the new order now (should take another 45min) to see if it breaks anything.

Boblenain · Post by **Boblenain** » Mon Jun 06, 2005 5:43 pm

When i want to launch e17 , it say missing Extension XpExtension on display 0:0

Mon xorg.conf is right and rulez with other WM ( KDE, Fvwm ..)

tdi · Post by **tdi** » Mon Jun 06, 2005 5:47 pm

ive got the same
rm .e/e/config/* and should be ok

Boblenain · Post by **Boblenain** » Mon Jun 06, 2005 6:52 pm

And How-to add e17 in KDM ? I think it's with a e17.desktop in /usr/share/xsessions

Some can post his e17.desktop ?

e-Gor · Post by **e-Gor** » Mon Jun 06, 2005 7:29 pm

Boblenain wrote:Some can post his e17.desktop ?

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=e17
Comment=e17
Exec=enlightenment-0.17
Icon=
Type=Application

tdi · Post by **tdi** » Mon Jun 06, 2005 9:34 pm

engage started working after rebuilding with right order.
thanks

J^2 · Post by **J^2** » Thu Jun 09, 2005 8:42 am

Any ideas as to why switching to e17 would make my sound not work? I use alsa, so when my sound didn't work I ran alsamixer and got an error like this:

Code: Select all

function snd_ctl_open failed for default: Permission denied

gimpel · Post by **gimpel** » Thu Jun 09, 2005 10:10 am

J^2 wrote:Any ideas as to why switching to e17 would make my sound not work? I use alsa, so when my sound didn't work I ran alsamixer and got an error like this:
Code: Select all
function snd_ctl_open failed for default: Permission denied

what login manager are you using?

mazirian · Post by **mazirian** » Thu Jun 09, 2005 11:00 am

@j^2: This is probably a silly question but I'll ask it anyway: does you user belong to the audio group?

J^2 · Post by **J^2** » Thu Jun 09, 2005 4:35 pm

gimple: Entrance

mazirian: Not such a silly question since my users doesn't.

Why would this matter though? Sound works fine in gnome, e16, kde, yet fails in e17 because of this?

mazirian · Post by **mazirian** » Thu Jun 09, 2005 5:37 pm

Well you might try adding yourself to the audio group anyway. The permissions for several devices are set to rw for that group but not for all users. Did alsamixer or alsamixergui work for you in gnome? How about gnome-volume-control? What are the permissions set to for your sound devices in /dev/snd (or is it, /dev/sound?)?

J^2 · Post by **J^2** » Thu Jun 09, 2005 6:52 pm

[Edit: scrapped permissions]

Yes, alsamixer has worked fine everywhere. I added myself to the audio group and it worked. I think that's pretty strange, I don't see how changing to e17 did that but anyway, thanks for the help

Rosjahh · Post by **Rosjahh** » Thu Jun 09, 2005 11:51 pm

Since a couple of days I'm having trouble to use the e cvs ebuild:

It fails at the cvs checkout:

Code: Select all

 * Running  cvs -q -f -z3 -d ":pserver:anonymous@cvs.sourceforge.net:/cvsroot/enlightenment" update -dP e17/apps/e
cvs update: ignoring e17/apps/e (CVS/Repository missing)
cvs [update aborted]: no such directory `e17/apps'

Executing the same cvs command from the shell also fails. But all is well, when I excute the different cvs checkout command as stated on the enlightenment.org:

Code: Select all

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/enlightenment co e17/apps/e

A bit of fiddling shows that in my setup the "co" work, while "update -dP" does complain that the e17/apps directory is missing. Also the $DISTDIR/cvs-src/e17/apps/e directory just exists !

Am I the only one? Something wrong with my cvs?

E17 is coming?? (Part 2)

a list of AVAILABLE modules?

Re: a list of AVAILABLE modules?