Re: [E-devel] E17 panel within the same process as a whole E17

[Gustavo S. B. <bar...@pr...>]

On Tue, Jun 10, 2008 at 7:06 AM, The Rasterman Carsten Haitzler
<ra...@ra...> wrote:
> On Tue, 10 Jun 2008 11:18:34 +0300 Alexander Semenov <boh...@gm...>
> 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.

-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: bar...@gm...
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202