On Sun, 18 Jun 2017 14:31:16 +0200 michael bouchaud <michael.bouch...@gmail.com> said:
> No I don't use a dm today, I'm a single user on my laptop. same for me... :) > And the plan is what raster ask and explain, e have got what we need to > make a great login manager for e. aaah indeed. this would have been next - to convince you to go this way... no need then. this absolutely makes the most sense when considering moving to wayland as it otherwise would mean a LOT more work for the login manager. > What I have done is just make experiment with imfos module (into my branch) > and try what we could do with security when logged. I do a little > bootsplash with entrance code and go to the login screen without blinking > at startup. But it was really hacky to make it works. i'm sure it can be done. we need to figure out how to "make it clean". > What we need to do is make a hook at e startup. To check if we are run as > root and look if a "login" module is present. "login" could be defined by > the type of the module. The login module proceed to log the user, place env > vars and restart e. With this we could catch about all devices login > procedures. desktop, tablet and phone. > The config module could embed some widget from e_modules but with limited > access (no file manager and limited setting panel). A note module could be > great to let a "friendly" message to a user. my thoughts are that we do need a special "mode". i'd make it a cmdine argument that suspends ALL rendering UNTIL someone unblocks it (the imfos module would unblock it once it's loaded and ready). this might suspend any other things like the compositor emitting a signal/fading in like it normally would do. we might want to make this actually a standard thing. if you have one specific module loaded it is ITS job to say "we're all good to go now"... :) (if this module is not loaded it won't suspend anything on startup). > About the bootsplash we need to make a little app to start quickly and > require a minimum set of dependencies. Maybee the bootsplash could pass an > ecore_evas buffer to e and start it early in boot process. yeah. this is different. i actually made one that already has a pipe for sending commands to etc. exquisite. it's still in the old svn e repos. it has a little exquisite-write to be "called form login scripts" to update progress/status... but TBH these days i'd go for something very simple - display a static image... if anything goes wrong, drop back to text mode. when login manager starts, boot splash simply fades to black, then login manager starts. everyone "agrees" to fade in/out from black. that way we have the least amount of glitches. also if using kmv - don't "restore mode" on shutdown. leave fb with the last frame rendered (a black frame) and let it stay there until the next app takes over and sends a new buffer... the first buffer should be black (fading in from there). > The gui code of entrance could be a good startup for a new login module. > But the rest of code :(, just picking some here and there. So I hope now > you understand why my interrest into entrance is low since 2-3 years. makes sense. :) > 2017-06-18 11:48 GMT+02:00 Simon Lees <sfl...@suse.de>: > > > > > > > On 18/06/17 06:51, William L. Thomson Jr. wrote: > > > On Sat, 17 Jun 2017 19:37:24 +0200 > > > michael bouchaud <michael.bouch...@gmail.com> wrote: > > > > > >> Nothing about this fork, it's a great news and me too, I will enjoy > > >> an e login manager ! > > > > > > I take it you are not using entrance now. What are you using then to > > > log into E? To me having DM is pretty important. I typically have used > > > ones bound to their desktop env like GDM and KDM, which KDM was dropped > > > for SDDM. But according to KDE SDDM is their official DM. > > > > > > What is the official DM for E? Any? Seems to be a confusing situation. > > > many working on different things. > > > > > > > Like every desktop outside gnome/kde there isn't one, none have ever > > reached a state where we could declare them stable and official but its > > known that lightdm, gdm and sddm all launch enlightenment correctly, > > atleast under X11. I know gdm has launched it under wayland as well at > > one point although I never got to the bottom of who's fault it was > > xwayland wasn't working. > > > > -- > > > > Simon Lees (Simotek) http://simotek.net > > > > Emergency Update Team keybase.io/simotek > > SUSE Linux Adelaide Australia, UTC+10:30 > > GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > > > > > > ------------------------------------------------------------ > > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > -- > Michaël Bouchaud > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
