Gustavo Sverzut Barbieri wrote: > On Tue, Jun 10, 2008 at 7:06 AM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: > >> On Tue, 10 Jun 2008 11:18:34 +0300 Alexander Semenov<[EMAIL PROTECTED]> >> babbled: >> >> >>> Hi all. >>> >>> I have a simple question about E17 architecture. Why the panel is >>> located within the same process as E17. When panel (or a module on it) >>> crashes, E17 crashes too. It resembles "explorer.exe" for me. Moreover, >>> some people would like to use the panel with other WMs but they can't. >>> Is this right all about this or I am misunderstanding something? >>> >> because the panel doesn't "crash" as such (modules that are badly written may >> cause crashes) and by having it modular but internal it is much more memory >> efficient as it re-cycles all of e's features and setup and existing loaded >> resources. this is how it is and isn't going to change as we no longer would >> be >> as efficient if we did it another way. >> > > hint: if you expect your module to break/freeze somehow, you can opt > to make that part another process, if it breaks, it doesn't crash > whole E17 as you said. This is the case for battery gadget and its > batget, or temperature and tempget. Of course you still have the > visual part as one process, but even with that you can create your own > process, with your own X window and reparent it to the shelf, just > take care to make the icon window shaped or ARGB so it doesn't suck. > > Thank you all for your answers.
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
