151
edits
Gfx glue layer removal: Difference between revisions
Jump to navigation
Jump to search
m
s/Cairo/cairo/, added Category:Mozilla 2
m (s/Cairo/cairo/, added Category:Mozilla 2) |
|||
| Line 4: | Line 4: | ||
* All code calls <tt>gfx/thebes</tt> interfaces directly | * All code calls <tt>gfx/thebes</tt> interfaces directly | ||
** mostly this is <tt>nsIFrame::Paint</tt> methods, but there are others | ** mostly this is <tt>nsIFrame::Paint</tt> methods, but there are others | ||
* Not possible to implement a non- | * Not possible to implement a non-cairo rendering backend anymore | ||
** I believe this is already not possible; several <tt>nsIFrame::Paint</tt> methods already call <tt>gfx*</tt> interfaces directly | ** I believe this is already not possible; several <tt>nsIFrame::Paint</tt> methods already call <tt>gfx*</tt> interfaces directly | ||
** Non-Thebes <tt>gfx/src/*</tt> backends should be deleted early in the process, to remove false hits from automated scans for code needing conversion | ** Non-Thebes <tt>gfx/src/*</tt> backends should be deleted early in the process, to remove false hits from automated scans for code needing conversion | ||
| Line 120: | Line 120: | ||
:::: <tt>nsColorNames</tt>, <tt>nsCUPSShim</tt>, <tt>nsPSPrinterList</tt>, <tt>nsITheme</tt> (where is the implementation?) | :::: <tt>nsColorNames</tt>, <tt>nsCUPSShim</tt>, <tt>nsPSPrinterList</tt>, <tt>nsITheme</tt> (where is the implementation?) | ||
[[Category:Mozilla 2]] | |||