On Fri, 23 Mar 2012 15:40:10 -0300 Lucas De Marchi <lucas.demar...@profusion.mobi> said:
> On Fri, Mar 23, 2012 at 2:23 AM, Enlightenment SVN > <no-re...@enlightenment.org> wrote: > > Log: > > add -cleanvt > > > > > > > > Author: raster > > Date: 2012-03-22 22:23:44 -0700 (Thu, 22 Mar 2012) > > New Revision: 69575 > > Trac: http://trac.enlightenment.org/e/changeset/69575 > > > > Modified: > > trunk/exquisite/ChangeLog trunk/exquisite/src/bin/main.c > > > > Modified: trunk/exquisite/ChangeLog > > =================================================================== > > --- trunk/exquisite/ChangeLog 2012-03-23 03:46:36 UTC (rev 69574) > > +++ trunk/exquisite/ChangeLog 2012-03-23 05:23:44 UTC (rev 69575) > > @@ -0,0 +1,10 @@ > > +2012-02-10 Carsten Haitzler (The Rasterman) > > + > > + 1.0.0 release > > + > > +2012-03-23 Carsten Haitzler (The Rasterman) > > + > > + * add -cleanvt to enable clean "fade out" animation before giving > > + up the VT. > > IMO it's much better to tell X to run on the same VT (i.e. the first > one), start X with "background none" and use the same background. Then > you have a flicker free boot and user has the feeling that boot was > much faster then it really was. x will not be able to own that vt because exquisite already owns it. also remember that the driver will most likely reconfigure the gfx chip - possibly with a different resolution (this definitely happens on nvidia drivers in many cases as the kernels vesa support often can't detect the correct resolution). all this does is allow exquisite to do its "fade out" or finish anim when something else wants to take the vt instead of just instantly exiting. :) > Unrelated question about exquisite: why aren't you using an abstract > socket to communicate with exquisite? i'm actually using fifos mostly to cut down the overhead of writing status updates as it needs much simpler tools. :) > "2. You need a /tmp directory for the UNIX socket that is used to talk to > exquisite. The exquisite-write utility sends messages to exquisite via a UNIX > domain socket created in /tmp. This needs to be writable for exquisite to > start." > > This implies that you need to have /tmp mounted or a writable / early > on boot sequence. If you use abstract sockets you can start exquisite > earlier. With dietsplash I use this and run the run the splash even > before handing off to the init process. exqusitie needs a lot of infra - eina, ecore, evas, edje, an edje file, embryo etc. etc. to get up and running. these in turn need modules. using /tmp isn't a tall order :) also i think i wrote this before abstract socket support was in ecore_con or very early after it was added. i did it then never touched it again as it worked. > Lucas De Marchi > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > 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 ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
