I believe the original thinking was that we would have view specific implementations per platform and the code would change to go through a factory for creating the leaf node views instead of using constructors. All the platform specific code would exist in each of the platform specific implementations. Any place we're using windows specific code outside of the view classes would have to change to either be wrapped around a #define, or promoted to the view class in a platform neutral way.
-Scott On Mon, Dec 15, 2008 at 11:23 PM, joshthecoder <[email protected]> wrote: > > Currently the test_shell uses GTK to create a basic rendering for > Chromium. > > What are the plans so far on how to port the Views UI layout layer to > linux? > Will a widget toolkit such as GTK be used? Or maybe just use a more > direct approach such as XLib. > Using XLib to directly communicate with X server might provide some > extra speed much like using the Win32 API for the Windows version of > Views, but XLib might be a bit too low level. > > I'd like to see the wheels get rolling on porting Views over to linux. > This will be a major leap in getting Chrome running on linux. I'm > interesting in helping contribute code for porting views. So if anyone > has suggestions, ideas, or comments please post them. Let's get some > ideas flowing. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
