On Jan 28, 8:56 pm, Evan Martin <e...@chromium.org> wrote:
> In fact, the various toolkits (Qt, Gtk, Wx, etc.) do pretty much
> exactly what views does while also including the widgets that views
> tries to wrap. If you're unfamiliar with the Windows API, you should
> know it doesn't provide any standard way of doing resizable layouts;
> apps typically implement custom code for it. Similarly for
> double-buffering. If you're unfamiliar with the Linux toolkit APIs,
> you should know that all of this stuff is built-in.
That was the first thing I thought when I started to learn how
Chromium i made.
I know Windows developers have "their ways", but if you want to do a
good port
make it look like Linux app (on the inside and outside)
> Options, as I see them:
> 1) As close to Windows as possible, porting views.
> 2) As close to native as possible, avoiding views.
> 3) Something in the middle, hacking views.
IMHO the only right way to do it is 2) with the little of 3) if
necessary.
> I think our mandate is to make something awesome that Linux devotees
> will also think is awesome. With that in mind, I think the people
> working on the Linux port are exactly the target audience of this
> thing...
Exactly! If you want do it right, do something that Linux community
will accept.
And IMO the best way to do it is to make it as native as possible.
Because if it will not feel native, it will be rejected, so why to
even bother making
a port that is defective by design. Chromium should look native and
use current user theme,
otherwise no one will really like it. And it would be real loss for
Linux, because chromium is
a great piece of software. And if done right, Linux port will rock! :)
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
