Re: Call-return interface for file choosers? (and: security using powerboxes)

2005-11-25 Thread Mike Hearn 
Hi Mark,

I've looked briefly at this before. A few thoughts:

 * Rather than messing around with LD_PRELOAD and X proxies you really
   just want to build your own patched copy of GTK+. This sort of change
   is fundamental and not something you should try and layer over an
   existing system. For X security you need to look at SE-X, which is
   SELinux but for the X server.

 * This problem is a specific form of a more general one, which is how to
   separate submodules of an existing monolithic C/C++ codebase into
   separate processes which run in separate security contexts. Not
   co-incidentally, this is the subject of my university dissertation.

   I'm intending to make the resulting RPC framework available under an 
   appropriate license once I have finished my degree. So far the RPC API 
   is quite simple and easy to integrate with existing apps (it's a
   typeless/IDL-less system) and I think a PowerBox implementation for GTK+
   would be a good application of it. This goes some way towards solving
   the problem of proxying gtk_window* calls to the remote process.

 * A Plash independent way to do this is have the PowerBox open the file
   itself, then send the file descriptor across the RPC connection. Then
   get_filename can return /proc/self/fd/$x and everything should work as
   normal except that displaying the filename in the title bar etc
   wouldn't operate correctly.



___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

Re: Usage of GTK+ headers

2005-10-13 Thread Mike Hearn 
On Wed, 12 Oct 2005 14:55:32 -0400, Dan Winship wrote:
> Evolution switched from using the main headers to using specific headers a
> few years ago to speed up the compile time (substantially). I think some
> other apps do this as well.

These days the opposite will be true - you can precompile the GTK+ headers
all in one go and include them as a binary header. I've tried this and it
works well.

One caveat is that you can only include one binary header. But, you can
make a custom header file that simply includes gtk.h, and any other
headers a particular part of your program needs and precompile that.

The savings can be significant (on the order of 30-40% speedup in my own
tests).

thanks -mike

___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list