Proxy authetication methods.
What proxy authentication methods are available in mozilla? How to make use of it? (how to show mozilla dialogs? how to use it without prompting user?). I modified MFCEmbed, but can't log into proxy. Maybe cause is that, I compiled Mozilla w/o --enable-crypto? ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozilla-embedding
Re: Trying to incorporate the Lizard, but it keeps bitting me.
That's Nick Bradbury's code (http://www.bradsoft.com/), not mine. :) Dave Murray Glasgow, UK PGP KeyID: 0x838592B3 Remove NOSPAM from my email address to reply. Tom Peters wrote: View Source Code - Awesome code, but doesn't give you the stuff outside of the tag: --- Additional Comment #2 From irongut 2004-12-06 18:41 --- View source workaround: I worked around this by looking for the tag and returning the innerHtml from it, like this: Var elm : IHTMLElement; iCol : IHTMLElementCollection; iDoc : IHTMLDocument2; i, nLen : integer; Begin Result := ''; iDoc := IHTMLDocument2(FBrowserMZ.Document); // first extract body, in case html scan fails below elm := iDoc.body; if Assigned(elm) then Result := elm.innerHTML; // now extract collection of all elements, then scan for iCol := iDoc.all; if Assigned(iCol) then begin nLen := iCol.length; for i := 0 to nLen - 1 do begin elm := IHTMLElement(iCol.item(i, varEmpty)); if SameText(elm.tagName, 'html') then begin // found , so extract html source and exit Result := elm.innerHTML; exit; end; end; end; ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozilla-embedding
Re: off-screen rendering (that old chestnut)
Hi, Boris I have a question about rendering plugin as well. I implemented a windowless plugin which can use the HDC passed from nsObjectFrame to draw something (like rect, line) in the plugin. In order to draw a bitmap in the plugin, I'd like to call nsIRenderingContext's method (my image is in imgIContainer). But when I use the nsIRenderingContext ptr obtained from nsIViewManager* vm = mView->GetViewManager(); vm->GetWidgetForView(mView, getter_AddRefs(widget)); mRenderingCtx = widget->GetRenderingContext(); and call DrawImage or DrawScaledImage, the image does not appear in the plugin. When I resize the browser window, I can see the image is flashing. I did the other test: 1. use the DC got from widget->GetNativeData(NS_NATIVE_GRAPHIC) to draw a rect. 2. use the DC passed in from nsObjectFrame to draw a rect. The 1st rect is not shown either, when resize the browser, I can see it is flashing. The 2nd rect can be shown correctly and steadily. Since there is ONLY one widget in the browser, I don't know why two DCs from it will make such a difference. Can you nice guys give me some guide? And how to solve this problem? And is there any document about the principle of double-buffered rendering? Thank you very much. "Boris Zbarsky" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Sam Deane wrote: >> I'm not clear from the discussions that I've read whether the Gecko >> rendering is double-buffered, or whether it just splashes things >> straight into a window. > > It's usually double-buffered, at least for painting of the non-plugin > content. The one exception, I believe, is on Mac on pages where plugins > are present. Mac plugins apparently throw a fit when you try to > double-buffer those pages... > >> In particular, I'm wondering what happens with >> plug-ins - do they get rendered 'directly' into the window for >> efficiency and/or compliance with the underlying APIs that they call >> (again, Quicktime, Flash etc)? > > This may depend on whether the plugin is in windowless mode or not... :( > >> I've seen references to buffering / offscreen rendering in the >> archives along the lines of "it doesn't do it yet", but they are all >> fairly old so I'm crossing my fingers and hoping that they might now >> be out of date. > > No, those are up to date. There's code floating about to do it, but it's > not in the tree yet > > -Boris ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozilla-embedding
Re: off-screen rendering (that old chestnut)
Sam Deane wrote: I'm not clear from the discussions that I've read whether the Gecko rendering is double-buffered, or whether it just splashes things straight into a window. It's usually double-buffered, at least for painting of the non-plugin content. The one exception, I believe, is on Mac on pages where plugins are present. Mac plugins apparently throw a fit when you try to double-buffer those pages... In particular, I'm wondering what happens with plug-ins - do they get rendered 'directly' into the window for efficiency and/or compliance with the underlying APIs that they call (again, Quicktime, Flash etc)? This may depend on whether the plugin is in windowless mode or not... :( I've seen references to buffering / offscreen rendering in the archives along the lines of "it doesn't do it yet", but they are all fairly old so I'm crossing my fingers and hoping that they might now be out of date. No, those are up to date. There's code floating about to do it, but it's not in the tree yet -Boris ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozilla-embedding
off-screen rendering (that old chestnut)
Apologies if this is a faq - I've searched through the archives and seen various mentions of the topic but no definitive answers. I have an application which requires rendering a web page, capturing the resulting image and doing something with the bitmap data (sending it to a socket for example). Plug-ins (Quicktime, Flash etc) need to be supported (although not any sort of interactivity), and I need to be able to keep up with any animations at a rate which would allow real time playback at the 'other end'. Finally, I'd like to do this on a Windows machine. No, let me rephrase that... I'd _like_ to do it on a Mac, but my client would like to do it on a Windows machine :) I'm not clear from the discussions that I've read whether the Gecko rendering is double-buffered, or whether it just splashes things straight into a window. In particular, I'm wondering what happens with plug-ins - do they get rendered 'directly' into the window for efficiency and/or compliance with the underlying APIs that they call (again, Quicktime, Flash etc)? I've seen references to buffering / offscreen rendering in the archives along the lines of "it doesn't do it yet", but they are all fairly old so I'm crossing my fingers and hoping that they might now be out of date. Anyone care to comment? The obvious hack would be to try to capture the image 'back' from the window, but I'd prefer to avoid it for obvious reasons (cleanliness, performance, etc). ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozilla-embedding
