On Tue, Nov 18, 2008 at 11:02 AM, Amanda Walker <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 18, 2008 at 1:54 PM, Brett Wilson <[EMAIL PROTECTED]> wrote: >> No matter what we do each platform should have its own font and form >> control rendering. I don't think unifying these has ever been on the >> table. When I talk about unifying I mean the overall architecture. >> Each platform will have some of its own code to render fonts and form >> controls into the underlying buffer. > > Hmm, OK. Why are images different, then? I'm missing something--the > architecture's already unified--NativeImagePtr is just a WebKit > platform-specific type that's typedefed inconveniently at the moment.
This is not platform-specific on any other architecture, and it doesn't need to be. The difference is that font and form control rendering have to be native for us to look correct. This is not the case for images or any other part of GraphicsContext. Brett --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
