On 03/14/2012 03:26 PM, Robert O'Callahan wrote:
> On Wed, Mar 14, 2012 at 9:02 PM, Julian Viereck<
> julian.viereck@goog...>  wrote:
>
>> the PDF.JS team is dealing with printing support on the web. I looked at
>> what's currently possible with the browser and shared some thoughts about
>> it here:
>>
>>    https://gist.github.com/1953505#file_gistfile1.md
>>
>> There are some comments on this G+ post:
>>
>>         https://plus.google.com/u/0/115228539776721208421/posts/LbVDmfALeey
>>
>> Based on that feedback, I've started on a new WebPrint API proposal, that
>> you can find here:
>>
>>     https://wiki.mozilla.org/WebAPI/WebPrintAPI
>>
>> There isn't too much yet. So far I have scratched out the basic API and
>> started some very basic implementation work. However, I hope this is enough
>> to get some discussion about this proposed API going and I'd like to get
>> some feedback what people think about it.
>>
>
> We need to implement the CSS3 stuff anyway. How about:
> -- Implement CSS3 Paged Media sufficient to make headers/footers and
> margins go away, select page orientation and size. That shouldn't be too
> hard.
> -- Add an event to canvas that fires per-page during printing to render
> that canvas content while we're printing the page it's on. This event would
> provide a special canvas context that's compatible with the 2d interface
> but internally renders at higher resolution (or possibly emits PS/PDF
> directly).
> Then you could create a print document that's just a series of canvases,
> with the appropriate CSS to remove headers/footers/margins etc, and as we
> print each page we'll run the callback on each canvas to paint it more
> accurately. Any temporary resources could be thrown away after painting
> that page.

That's clever, I like it.

zw
_______________________________________________
dev-tech-layout mailing list
dev-tech-layout@list...
https://lists.mozilla.org/listinfo/dev-tech-layout