The plan that we have been operating under so far is to have Chromium render form controls and fonts in a manner that is most appropriate for each platform. I think this is an important element of making a browser feel right on each platform. -Darin
On Fri, Oct 17, 2008 at 11:23 AM, Marshall Greenblatt < [EMAIL PROTECTED]> wrote: > On Fri, Oct 17, 2008 at 1:58 PM, Adam Treat <[EMAIL PROTECTED]> wrote: > >> >> 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. > > > I would have to disagree with the idea of a single chromium theme for forms > across all platforms, as I consider it important on most platforms to match > the native look and feel. This is especially relevant when you consider how > different Windows 2000, Windows XP and Windows Vista look from each other. > There's also a limit on what can be accomplished with CSS. One of the most > annoying aspects of Microsoft's WebBrowser2 control, for instance, is that > it doesn't honor the platform theme, and so you see Windows 2000 style > buttons on all platforms (imagine how that looks when all of the other > buttons in an application are Vista-themed). And we all know how militant > Mac users are about their UI. > > Just my 2 cents :-) > > > >> 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 > > > Regards, > Marshall > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
