Re: Why not to split gmc and other gnome applications into threads?

[redhog mini dhs org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think it would be better to have each gmc window as a separate process.
Ok that would be a little bit more expensive, but it would pay. They could
then communicate with some back-end that coordinated them. Then any app
would be able to connect to that back-end and ask it to fire up a
gmc-window, or icon-box (As in the root-window case) inside some of (its)
(existing) X window... That, I think would be much easier to implement,
since it would only requere to replace all code in gmc that handles the
creation of a new window, with some backend-communication code, and to
create a back-end.

<A Href="http://www.tekmetrics.com/transcript.shtml?pid=29943">TekMetrics Online Public Transcript (e-certifications[tm])</A><Br>
<A Href="http://mini.dhs.org/PGP%20Public%20key.asc">PGP Public key</A><Br>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.9 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4JgxMHeQ6HSAJlUwRAn00AJ40pRXbLGNJHeBBVcBxb+AhLpo0IgCfVdtM
MU3VyQKPxYG+/5TI8S8hwGs=
=OJnl
-----END PGP SIGNATURE-----