Hi everyone,
Following Steve Clark's suggestion on the mozilla-layout NG, I had a look at
both mozilla/webshell/tests/viewer and mozilla/embedding/tests/gtkembed in
the CVS tree. I wish to assemble a simple HTML viewer into an existing
application which uses the Linux framebuffer as the display target; after
browsing throught the two test apps, and since I am not using any windowing
toolkit at all, I start to wonder what options I've got left, since I still
haven't found any demo of gecko rendering files to a target that doesn't
support a windowing toolkit.
Would it be possible for anyone to shortly describe the mechanism(s) by
which gecko can be "activated"/"called" by an application? The use of
gtk/MFC in the demos ends up obscuring the underlying mechanism a little; I
am still wondering how I can pass gecko a pointer to a mem area containing
the HTML code it should display, not to mention how one can "tell" gecko
what actual lower-level drawing/text-rendering functions to use; does one
just pass function pointers to gecko?
My personal naive representation of gecko's interface is something like this
geckoInit(int (*fpPutPixel)(int x, int y, struct_color color, alpha), int
(*fpRenderText) (const char *text, int x, int y, const char *font, int
size));
geckoRenderPage(const char *HTML, .. /*pointers to CSS/images files*/);
geckoClose();
I would expect that, by writing the PutPixel and RenderText functions and
passing them as pointers to gecko I would be giving it the necessary tools
to render a page when I invoked geckoRenderPage(); am I completely off
target?
Thank you for any information.
Best regards,
Mack Stev.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
