On Thu, Jan 15, 2009 at 2:04 PM, Evan Martin <[email protected]> wrote: > > On Thu, Jan 15, 2009 at 10:37 AM, cpu <[email protected]> wrote: >> When Dean and Evan say that they don't mind reviewing patches for Qt >> ports, what we are saying is that >> we don't mind having two UI versions of Chromium on linux? >> >> How would this work in the long term? UI tests times 2? you get to >> choose what Chromium to install? > > I figured it would be unsupported. > >> If somebody asked me that they want to contribute a port of chrome on >> Windows UI using MFC, I would say no. I just don't see the cost/ >> benefit. > > Here's an analogy. Say I argued we should only target GTK because it > runs on Windows just fine, so we'd be able to share UI test code > between Windows and Mac. You'd (hopefully) say it'd be terrible > because it's non-native. > > That's the situation between GTK and Qt these days. The OS underneath > is the same, but running apps targeting one in an environment > targeting the other in terms of user experience feels much like GTK > apps feel on Windows. > > Unfortunately we don't have the resources to target both, but if > someone else is willing to provide the patches I'm willing to review > them. >
That isn't really the situation for Qt though. Arora is a good example of how Qt can intigrate very well in Gnome. Using the gtkstyle theme qt uses the native GTK theme to render widgets, detecting Gnome it will automatically select that theme, use Gnome shortcuts, and Gnome styled icons. Lastly using QDesktopServices it will ask Gnome to perform actions like open this folder and does not explicitly use Konq. The same can not be said of a Gnome app these days. Some screenshots of Arora in different desktops show off the visual integration: http://code.google.com/p/arora/wiki/Screenshots. And there are file dialog hooks, I don't know if the gtkstye uses the Gnome file dialog, but it can. Qt has put a lot of time and effort into working well on KDE and Gnome so application developers don't have to. But I guess it all depends upon what you want it to do for you. For Chrome the browser applications there are definite advantages. For chromium the webkit rendering engine there might be stuff that can be shared with QtWebKit (or at least used as comparison or copy) such as clipboard, fonts, paint etc. Using Qt and taking advantage of that fact that Qt already has a working an tested (insert feature here) for X11 that can integrate with Webkit is a win. -Benjamin Meyer --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
