Re: [E-devel] RFC: enlightenment_start -locked
On Fri, Nov 7, 2008 at 12:57 PM, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > Hi guys, > > During the conference my laptop suspend/resume decided to barf and I > have to shutdown and restart lots of time, having to wait for the > always slow boot process (mine is still not under 5s) and part of it > is loading entrance and e... > > But wait, most of users I know just have one single user in their > machine, including myself... so why use entrance at all? We should > have a way to ask enlightenment to start with the desktop lock on, > some command line option like "-locked" so I'm still safe, but as soon > as I type my password I have something ready and working, possible my > autostart apps are fully working and everything. And all of that > without special hacks like Gnome guys did to have GDM to preload gnome > session before... > > To me it's plain simple, but before I dig into code to have that > working, do you see any problems with that approach? So at least 3 guys answered to me in IRC with positive feedback (being in the same situation as I am). Do anyone see a problem with such approach? Does anyone know better what's required for user switch? Maybe it would be good to change Entrance when it's fixed/rewrite so we have a way to do autostart as well, in that case Entrance would start itself as the minimum smart session end monitor that it uses once users logs in. That way it doesn't impact boot times and it is still possible for people to change users later. Maybe that can be added to E desktop lock, since when I see multiple users running on the same machine I see they using multiple X sessions, so it's just a matter of spawning a new server... but I'm not sure about coordination between those... or those with the login manager, but KDE/KDM does keep track of such information (at least if you want to shutdown it will first show that there are other users logged in and confirm you want to proceed). -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" <[EMAIL PROTECTED]> wrote: > On Fri, Nov 7, 2008 at 12:57 PM, Gustavo Sverzut Barbieri > <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > During the conference my laptop suspend/resume decided to barf and I > > have to shutdown and restart lots of time, having to wait for the > > always slow boot process (mine is still not under 5s) and part of it > > is loading entrance and e... > > > > But wait, most of users I know just have one single user in their > > machine, including myself... so why use entrance at all? We should > > have a way to ask enlightenment to start with the desktop lock on, > > some command line option like "-locked" so I'm still safe, but as > > soon as I type my password I have something ready and working, > > possible my autostart apps are fully working and everything. And > > all of that without special hacks like Gnome guys did to have GDM > > to preload gnome session before... > > > > To me it's plain simple, but before I dig into code to have that > > working, do you see any problems with that approach? > > So at least 3 guys answered to me in IRC with positive feedback (being > in the same situation as I am). Do anyone see a problem with such > approach? > > Does anyone know better what's required for user switch? Maybe it > would be good to change Entrance when it's fixed/rewrite so we have a > way to do autostart as well, in that case Entrance would start itself > as the minimum smart session end monitor that it uses once users logs > in. That way it doesn't impact boot times and it is still possible for > people to change users later. > Maybe that can be added to E desktop lock, since when I see > multiple users running on the same machine I see they using multiple X > sessions, so it's just a matter of spawning a new server... but I'm > not sure about coordination between those... or those with the login > manager, but KDE/KDM does keep track of such information (at least if > you want to shutdown it will first show that there are other users > logged in and confirm you want to proceed). > I was sitting here thinking about this and just remembered that Entrance already has the ability to do autologin. It's not exactly trivial, but if you look at the build_config.sh in the entrance/data/config directory you should be able to find how it does the automatic login. I recall setting this up for gOS and I believe it works. There are two types of auto login, one that is meant to be silent, but doesn't actually work last I tried and one that will popup the theme and then immediately login and fade it out. The latter did work although it's not as desireable. This of course doesn't solve your problem exactly, but Entrance does store the username from the last login so the only thing you usually have to type in is your password anyway which is pretty much the same effect with a couple more seconds to wait while E loads. E doesn't take so long to load that this is unbearable though. And the fast user switching stuff would be interesting to implement. Trying to juggle multiple screens is probably a bunch of fun :) > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
Nick Hughart wrote: > On Sat, 8 Nov 2008 06:19:46 -0200 > "Gustavo Sverzut Barbieri" <[EMAIL PROTECTED]> wrote: > >> On Fri, Nov 7, 2008 at 12:57 PM, Gustavo Sverzut Barbieri >> <[EMAIL PROTECTED]> wrote: >>> Hi guys, >>> >>> During the conference my laptop suspend/resume decided to barf and I >>> have to shutdown and restart lots of time, having to wait for the >>> always slow boot process (mine is still not under 5s) and part of it >>> is loading entrance and e... >>> >>> But wait, most of users I know just have one single user in their >>> machine, including myself... so why use entrance at all? We should >>> have a way to ask enlightenment to start with the desktop lock on, >>> some command line option like "-locked" so I'm still safe, but as >>> soon as I type my password I have something ready and working, >>> possible my autostart apps are fully working and everything. And >>> all of that without special hacks like Gnome guys did to have GDM >>> to preload gnome session before... >>> >>> To me it's plain simple, but before I dig into code to have that >>> working, do you see any problems with that approach? >> So at least 3 guys answered to me in IRC with positive feedback (being >> in the same situation as I am). Do anyone see a problem with such >> approach? >> >> Does anyone know better what's required for user switch? Maybe it >> would be good to change Entrance when it's fixed/rewrite so we have a >> way to do autostart as well, in that case Entrance would start itself >> as the minimum smart session end monitor that it uses once users logs >> in. That way it doesn't impact boot times and it is still possible for >> people to change users later. >> Maybe that can be added to E desktop lock, since when I see >> multiple users running on the same machine I see they using multiple X >> sessions, so it's just a matter of spawning a new server... but I'm >> not sure about coordination between those... or those with the login >> manager, but KDE/KDM does keep track of such information (at least if >> you want to shutdown it will first show that there are other users >> logged in and confirm you want to proceed). >> > > I was sitting here thinking about this and just remembered that > Entrance already has the ability to do autologin. It's not exactly > trivial, but if you look at the build_config.sh in the > entrance/data/config directory you should be able to find how it does > the automatic login. I recall setting this up for gOS and I believe it > works. There are two types of auto login, one that is meant to be > silent, but doesn't actually work last I tried and one that will popup > the theme and then immediately login and fade it out. The latter did > work although it's not as desireable. > > This of course doesn't solve your problem exactly, but Entrance does > store the username from the last login so the only thing you usually > have to type in is your password anyway which is pretty much the same > effect with a couple more seconds to wait while E loads. E doesn't > take so long to load that this is unbearable though. > > And the fast user switching stuff would be interesting to implement. > Trying to juggle multiple screens is probably a bunch of fun :) ConsoleKit is meant as a tool to help managing several sessions. So it would be best to wait until it stabilizes before doing much work on this. Sebastian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Sat, Nov 8, 2008 at 6:19 AM, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > On Fri, Nov 7, 2008 at 12:57 PM, Gustavo Sverzut Barbieri > <[EMAIL PROTECTED]> wrote: >> Hi guys, >> >> During the conference my laptop suspend/resume decided to barf and I >> have to shutdown and restart lots of time, having to wait for the >> always slow boot process (mine is still not under 5s) and part of it >> is loading entrance and e... >> >> But wait, most of users I know just have one single user in their >> machine, including myself... so why use entrance at all? We should >> have a way to ask enlightenment to start with the desktop lock on, >> some command line option like "-locked" so I'm still safe, but as soon >> as I type my password I have something ready and working, possible my >> autostart apps are fully working and everything. And all of that >> without special hacks like Gnome guys did to have GDM to preload gnome >> session before... >> >> To me it's plain simple, but before I dig into code to have that >> working, do you see any problems with that approach? > > So at least 3 guys answered to me in IRC with positive feedback (being > in the same situation as I am). Do anyone see a problem with such > approach? > > Does anyone know better what's required for user switch? Maybe it > would be good to change Entrance when it's fixed/rewrite so we have a > way to do autostart as well, in that case Entrance would start itself > as the minimum smart session end monitor that it uses once users logs > in. That way it doesn't impact boot times and it is still possible for > people to change users later. >Maybe that can be added to E desktop lock, since when I see > multiple users running on the same machine I see they using multiple X > sessions, so it's just a matter of spawning a new server... but I'm > not sure about coordination between those... or those with the login > manager, but KDE/KDM does keep track of such information (at least if > you want to shutdown it will first show that there are other users > logged in and confirm you want to proceed). Ok, hacked it yesterday night before I went to sleep, it works but you see the background before the desklock shows, I see no easy way to 'fix' this as it depends on messages being processed (I guess, since it just show the window when main loop begins), but it should be safe, no other content should be read/accessible before user logins. I did lots of reorganization, fix some typos and fixed some bugs (it was pushing one "init" instead of "shutdown"), no incremental patches since this SVN is a sucker and does not makes it easy and I had no time to play with that myself. It would be good if raster or someone else that knows well E init requirements and dependencies to look at reorganization. It's working, please try it. As soon as I'm back from Amsterdam I'll commit it to SVN. PS: it would be great to have 1-2 macros to handle initalization, e_main.c is way too boring! -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Tue, Nov 11, 2008 at 7:05 AM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" > <[EMAIL PROTECTED]> babbled: > > (sorry - travelling...) > > um - i think it's a great idea. makes sense for auto-logins like with gsm (or > if enrance gets one) or even more so for embedded devices - like phone/pda's > etc. where the thing boots straight into x and e.. and you want to lock it > with > a pin # (desklock needs a way of adding some way to enter a password/pin > number > other than via a keyboard - a pin #, a virtual keyboard, or maybe some special > shape you draw... main point is to make it flexible). Yes, for that I guess it's easier to abstract desklock or use an external desklock app (already supported, but I never tried). The former is better as it's faster and lower on resources. A virtual number keyboard would do for most devices. > as such user-switching i think is best left to whatever launches e. leave that > out of e. nb - i would say that this is best done as a config option in > e_config > > "lock_on_start" and that should do quite nicely :) add to the desklock config yes, it's easy doable, but I guess fixing the show wallpaper is a worse problem ATM. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" <[EMAIL PROTECTED]> babbled: (sorry - travelling...) um - i think it's a great idea. makes sense for auto-logins like with gsm (or if enrance gets one) or even more so for embedded devices - like phone/pda's etc. where the thing boots straight into x and e.. and you want to lock it with a pin # (desklock needs a way of adding some way to enter a password/pin number other than via a keyboard - a pin #, a virtual keyboard, or maybe some special shape you draw... main point is to make it flexible). as such user-switching i think is best left to whatever launches e. leave that out of e. nb - i would say that this is best done as a config option in e_config "lock_on_start" and that should do quite nicely :) add to the desklock config > On Fri, Nov 7, 2008 at 12:57 PM, Gustavo Sverzut Barbieri > <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > During the conference my laptop suspend/resume decided to barf and I > > have to shutdown and restart lots of time, having to wait for the > > always slow boot process (mine is still not under 5s) and part of it > > is loading entrance and e... > > > > But wait, most of users I know just have one single user in their > > machine, including myself... so why use entrance at all? We should > > have a way to ask enlightenment to start with the desktop lock on, > > some command line option like "-locked" so I'm still safe, but as soon > > as I type my password I have something ready and working, possible my > > autostart apps are fully working and everything. And all of that > > without special hacks like Gnome guys did to have GDM to preload gnome > > session before... > > > > To me it's plain simple, but before I dig into code to have that > > working, do you see any problems with that approach? > > So at least 3 guys answered to me in IRC with positive feedback (being > in the same situation as I am). Do anyone see a problem with such > approach? > > Does anyone know better what's required for user switch? Maybe it > would be good to change Entrance when it's fixed/rewrite so we have a > way to do autostart as well, in that case Entrance would start itself > as the minimum smart session end monitor that it uses once users logs > in. That way it doesn't impact boot times and it is still possible for > people to change users later. > Maybe that can be added to E desktop lock, since when I see > multiple users running on the same machine I see they using multiple X > sessions, so it's just a matter of spawning a new server... but I'm > not sure about coordination between those... or those with the login > manager, but KDE/KDM does keep track of such information (at least if > you want to shutdown it will first show that there are other users > logged in and confirm you want to proceed). > > > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -- > MSN: [EMAIL PROTECTED] > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Tue, 11 Nov 2008 17:28:42 -0200 "Gustavo Sverzut Barbieri" <[EMAIL PROTECTED]> babbled: > On Tue, Nov 11, 2008 at 7:05 AM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: > > On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" > > <[EMAIL PROTECTED]> babbled: > > > > (sorry - travelling...) > > > > um - i think it's a great idea. makes sense for auto-logins like with gsm > > (or if enrance gets one) or even more so for embedded devices - like > > phone/pda's etc. where the thing boots straight into x and e.. and you want > > to lock it with a pin # (desklock needs a way of adding some way to enter a > > password/pin number other than via a keyboard - a pin #, a virtual > > keyboard, or maybe some special shape you draw... main point is to make it > > flexible). > > Yes, for that I guess it's easier to abstract desklock or use an > external desklock app (already supported, but I never tried). The > former is better as it's faster and lower on resources. A virtual > number keyboard would do for most devices. > > > > as such user-switching i think is best left to whatever launches e. leave > > that out of e. nb - i would say that this is best done as a config option > > in e_config > > > > "lock_on_start" and that should do quite nicely :) add to the desklock > > config > > yes, it's easy doable, but I guess fixing the show wallpaper is a > worse problem ATM. yeah. the problem is - the desktop container is created and shown and filled with a bg pixmap - before the pin window can do anything, so it's a matter of either deferring the draw of the desktop until later, or creating, or having an "early show" hook. that forces something to be shown before anything else. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
On Wed, Nov 12, 2008 at 6:41 AM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Tue, 11 Nov 2008 17:28:42 -0200 "Gustavo Sverzut Barbieri" > <[EMAIL PROTECTED]> babbled: > >> On Tue, Nov 11, 2008 at 7:05 AM, The Rasterman Carsten Haitzler >> <[EMAIL PROTECTED]> wrote: >> > On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" >> > <[EMAIL PROTECTED]> babbled: >> > >> > (sorry - travelling...) >> > >> > um - i think it's a great idea. makes sense for auto-logins like with gsm >> > (or if enrance gets one) or even more so for embedded devices - like >> > phone/pda's etc. where the thing boots straight into x and e.. and you want >> > to lock it with a pin # (desklock needs a way of adding some way to enter a >> > password/pin number other than via a keyboard - a pin #, a virtual >> > keyboard, or maybe some special shape you draw... main point is to make it >> > flexible). >> >> Yes, for that I guess it's easier to abstract desklock or use an >> external desklock app (already supported, but I never tried). The >> former is better as it's faster and lower on resources. A virtual >> number keyboard would do for most devices. >> >> >> > as such user-switching i think is best left to whatever launches e. leave >> > that out of e. nb - i would say that this is best done as a config option >> > in e_config >> > >> > "lock_on_start" and that should do quite nicely :) add to the desklock >> > config >> >> yes, it's easy doable, but I guess fixing the show wallpaper is a >> worse problem ATM. > > yeah. the problem is - the desktop container is created and shown and filled > with a bg pixmap - before the pin window can do anything, so it's a matter of > either deferring the draw of the desktop until later, or creating, or having > an > "early show" hook. that forces something to be shown before anything else. let's draw desklock earlier, the faster the response the better! attached is a new patch with config dialog. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC: enlightenment_start -locked
Sorry, my machine lost *.patch mime type from /etc/mime.types On Thu, Nov 13, 2008 at 10:07 AM, Iván Briano (Sachiel) <[EMAIL PROTECTED]> wrote: > On Thu, Nov 13, 2008 at 8:41 AM, Gustavo Sverzut Barbieri > <[EMAIL PROTECTED]> wrote: >> On Wed, Nov 12, 2008 at 6:41 AM, The Rasterman Carsten Haitzler >> <[EMAIL PROTECTED]> wrote: >>> On Tue, 11 Nov 2008 17:28:42 -0200 "Gustavo Sverzut Barbieri" >>> <[EMAIL PROTECTED]> babbled: >>> On Tue, Nov 11, 2008 at 7:05 AM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" > <[EMAIL PROTECTED]> babbled: > > (sorry - travelling...) > > um - i think it's a great idea. makes sense for auto-logins like with gsm > (or if enrance gets one) or even more so for embedded devices - like > phone/pda's etc. where the thing boots straight into x and e.. and you > want > to lock it with a pin # (desklock needs a way of adding some way to > enter a > password/pin number other than via a keyboard - a pin #, a virtual > keyboard, or maybe some special shape you draw... main point is to make > it > flexible). Yes, for that I guess it's easier to abstract desklock or use an external desklock app (already supported, but I never tried). The former is better as it's faster and lower on resources. A virtual number keyboard would do for most devices. > as such user-switching i think is best left to whatever launches e. leave > that out of e. nb - i would say that this is best done as a config option > in e_config > > "lock_on_start" and that should do quite nicely :) add to the desklock > config yes, it's easy doable, but I guess fixing the show wallpaper is a worse problem ATM. >>> >>> yeah. the problem is - the desktop container is created and shown and filled >>> with a bg pixmap - before the pin window can do anything, so it's a matter >>> of >>> either deferring the draw of the desktop until later, or creating, or >>> having an >>> "early show" hook. that forces something to be shown before anything else. >> >> let's draw desklock earlier, the faster the response the better! >> >> attached is a new patch with config dialog. >> > Nope, nothing is attached. > >> -- >> Gustavo Sverzut Barbieri >> http://profusion.mobi embedded systems >> -- >> MSN: [EMAIL PROTECTED] >> Skype: gsbarbieri >> Mobile: +55 (19) 9225-2202 >> >> - >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> ___ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> >> > -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 Index: src/bin/e_config.c === --- src/bin/e_config.c (revision 37472) +++ src/bin/e_config.c (working copy) @@ -538,6 +538,7 @@ E_CONFIG_VAL(D, T, desklock_background, STR); E_CONFIG_VAL(D, T, desklock_auth_method, INT); E_CONFIG_VAL(D, T, desklock_login_box_zone, INT); + E_CONFIG_VAL(D, T, desklock_start_locked, INT); E_CONFIG_VAL(D, T, desklock_autolock_screensaver, INT); E_CONFIG_VAL(D, T, desklock_autolock_idle, INT); E_CONFIG_VAL(D, T, desklock_autolock_idle_timeout, DOUBLE); @@ -838,6 +839,7 @@ e_config->desklock_background = NULL; e_config->desklock_auth_method = 0; e_config->desklock_login_box_zone = -1; + e_config->desklock_start_locked = 0; e_config->desklock_autolock_screensaver = 0; e_config->desklock_autolock_idle = 0; e_config->desklock_autolock_idle_timeout = 300.0; @@ -1201,6 +1203,10 @@ IFCFG(0x0129); e_config->default_system_menu = NULL; IFCFGEND; + + IFCFG(0x012a); + e_config->desklock_start_locked = 0; + IFCFGEND; e_config->config_version = E_CONFIG_FILE_VERSION; Index: src/bin/e_config.h === --- src/bin/e_config.h (revision 37472) +++ src/bin/e_config.h (working copy) @@ -33,7 +33,7 @@ /* increment this whenever a new set of config values are added but the users * config doesn't need to be wiped - simply new values need to be put in */ -#define E_CONFIG_FILE_GENERATION 0x0129 +#define E_CONFIG_FILE_GENERATION 0x012a #define E_CONFIG_FILE_VERSION((E_CONFIG_FILE_EPOCH << 16) | E_CONFIG_FILE_GENERATION) #defi
Re: [E-devel] RFC: enlightenment_start -locked
On Thu, Nov 13, 2008 at 8:41 AM, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > On Wed, Nov 12, 2008 at 6:41 AM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: >> On Tue, 11 Nov 2008 17:28:42 -0200 "Gustavo Sverzut Barbieri" >> <[EMAIL PROTECTED]> babbled: >> >>> On Tue, Nov 11, 2008 at 7:05 AM, The Rasterman Carsten Haitzler >>> <[EMAIL PROTECTED]> wrote: >>> > On Sat, 8 Nov 2008 06:19:46 -0200 "Gustavo Sverzut Barbieri" >>> > <[EMAIL PROTECTED]> babbled: >>> > >>> > (sorry - travelling...) >>> > >>> > um - i think it's a great idea. makes sense for auto-logins like with gsm >>> > (or if enrance gets one) or even more so for embedded devices - like >>> > phone/pda's etc. where the thing boots straight into x and e.. and you >>> > want >>> > to lock it with a pin # (desklock needs a way of adding some way to enter >>> > a >>> > password/pin number other than via a keyboard - a pin #, a virtual >>> > keyboard, or maybe some special shape you draw... main point is to make it >>> > flexible). >>> >>> Yes, for that I guess it's easier to abstract desklock or use an >>> external desklock app (already supported, but I never tried). The >>> former is better as it's faster and lower on resources. A virtual >>> number keyboard would do for most devices. >>> >>> >>> > as such user-switching i think is best left to whatever launches e. leave >>> > that out of e. nb - i would say that this is best done as a config option >>> > in e_config >>> > >>> > "lock_on_start" and that should do quite nicely :) add to the desklock >>> > config >>> >>> yes, it's easy doable, but I guess fixing the show wallpaper is a >>> worse problem ATM. >> >> yeah. the problem is - the desktop container is created and shown and filled >> with a bg pixmap - before the pin window can do anything, so it's a matter of >> either deferring the draw of the desktop until later, or creating, or having >> an >> "early show" hook. that forces something to be shown before anything else. > > let's draw desklock earlier, the faster the response the better! > > attached is a new patch with config dialog. > Nope, nothing is attached. > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -- > MSN: [EMAIL PROTECTED] > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
