On Thursday 16 October 2008 8:04:19 pm Evan Martin wrote: > What we discussed today is the leftover bits: those not covered by > CHROMIUM but potentially by GTK (for example, font drawing). What I > think we concluded was that any place that would call into GTK would > likely need a connection to the X server (for example again, font > drawing) and our renderers will not have that access. So it seems > we'll be better off not setting PLATFORM(GTK) and instead using a > mixture of CHROMIUM and whatever more unix-specific bits we can. > (We'll still be linking to GTK for theme drawing.)
Some of us were talking about this topic on #chromium-dev earlier and I think we came to the same conclusion. The bits that are in WebCore/platform do not really need GTK API for implementation. For font handling you can even use harfbuzz directly. In fact, I would suggest you don't even need GTK for theme drawing. It seems silly to me to link WebKit with all of GTK for the sole purpose of drawing forms in webpages according to the GTK theme. Moreover, the trend among web developers is to style these controls themselves using CSS. I would suggest that an elegant solution for Chromium on Linux (and perhaps for Chromium altogether on all platforms) is to implement a custom form drawing theme that would directly use WebKit rendering API's. In other words, you could create a RenderThemeCrossPlatform that would use WebCore::GraphicsContext API to manually draw various form controls. In fact, I have a basic start of such a theme and would be happy to share it and continue implementing the rest of the form controls. Cheers, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
