On Wed, Feb 11, 2009 at 1:51 PM, Alberto Ruiz <[email protected]> wrote: > One thing to note is, this API won't make it for the 2.x series > because it involves API breackage (we did a really bad work with the > old API). But will get there eventually for 3.0.
Yes, and given the delay between distro releases etc. we'd be unable to depend on it for years. But it'd be nice for it to at least be possible to someone else to do this sort of thing... >> - If there was some way to get the theme engine to preload all of its >> resources from an in-memory buffer, that would allow better disk-based >> sandboxing. >> - If there was a way to run a theme engine without loading GTK at all >> (we'd like to keep our renderer processes light). > > I will bring both suggestions. The first one is a really nice > suggestion for the new engines, specially when loading pixbufs. The > second one I'm pretty sure is doable Just to be clear, in the first case we'd ideally be able to query some system for what files it might potentially want to access, as well as be able to hook when it wants to load a file. > We are going to have folks from Qt Software and Mozilla in the > hackfest, I'm pretty sure they would love such features as well. Let's > see what can we do. Thanks! > PS: Evan, do you actually work at Google? > > Some companies are helping us funding the development of Gtk+ 3.0 > (Sun, Intel, Imendio, Canonical, Mozilla Corp, Nokia) and I was > wondering if you guys wanted to/could support us on this ongoing > effort so that you make sure that Gtk+ 3.0 can suit your future needs > for future Linux desktop applications. The new theming API would be an > area where we certainly could use some help. Yes, I do, but I am a lowly code monkey. I can forward along your message. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
