Hi M-A, On Sun, Oct 5, 2008 at 7:13 AM, Marc-Antoine Ruel <[EMAIL PROTECTED]>wrote:
> > BTW, If you look closely at some the classes name, you'll understand > that print preview was there but got removed, due to instability. > Don't worry, it'll be back. Do you have the code for the previous print preview implementation sitting around somewhere? At a particular revision, perhaps? It would be good for my understanding if I could take a look at it. > More below. > > 2008/10/5 Marshall Greenblatt <[EMAIL PROTECTED]>: > > Hi All, > > > > What changes would we like to see in a refactoring of printing support? > At > > a minimum, we need to... > > > > A) Move printing support into a separate module. > > I'm not sure of was you need except if it is to move it to base/ or > webkit/port/ & webkit/glue. Perhaps we should have the basic printing framework in base/ and the WebKit-specific implementation of print rendering in webkit/. Afterall, other parts of the application (like bookmarks, for instance) might benefit from the new printing framework but have their own print rendering logic. > M-A Regards, Marshall --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
