On Nov 21, 2:19 am, Andrew Miller <[EMAIL PROTECTED]> wrote: > > Have you tried using canvas? > > drawWindow will let you could use to draw the page to the canvas > (this window does not have to be visible, it could be the > contentWindow from an invisible iframe for example) > > getImageData could then be used to retrieve the image data off the > canvas (note: this might be harder to do if you aren't planning on doing > it from Javascript because canvas gets the arguments from XPConnect). > > Best regards, > Andrew >
Hey Andrew, Still not having much luck, I'm afraid. By Canvas, do you mean something such as a nsICanvasRenderingContextInternal? I'm very new to all of this, and I can't really seem to find any good general documentation on where one would start to develop an application using the mozilla libraries. There are a few neat examples (especially in the embedded subfolder), but these all seem to revolve around creating a window to draw to, using chrome and all that nice stuff. I'm very keen to create a full blown application using chrome and everything at some point, but for the moment I'm trying to create a bare-bones application that doesn't actually have a window and can (for instance) just dump the rendered document into a PNG file. I've had a look at all sorts of code (including DumpToPNG in the SeaMonkey source), and it all seems to be what I want to do, but there is always an elusive document or surface or surface or context that is passed into the function from _somewhere_, which I cannot re-create. Is there any documentation floating around, particularly for the interfaces present in the gfx sub-folder of the mozilla source, that I might have missed? It's starting to get frustrating, knowing that all the functionality is almost definitely there, but not being able to piece together a silly test-app that proves it. Thanks again, James _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
