On Tue, Dec 16, 2008 at 12:10 PM, Scott Violet <s...@chromium.org> wrote: > > 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.
Yes--this is why most of the view classes have associated "model" classes that encapsulate the state and behavior. This way, view classes can use platform facilities for drawing (GTK, GDI, Cocoa, etc.), but the bulk of the logic behind the view can be platform neutral. I don't think that any of the current Windows view classes were ever intended to be "ported" per se. --Amanda --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
