pascal/CEF4Delphi
1
0
Fork 0
mirror of https://github.com/salvadordf/CEF4Delphi.git synced 2025-06-12 22:07:39 +02:00
Code Issues Actions Releases Activity

Added more comments to JSExtension

Browse Source 
- MiniBrowser shows the name of the loaded frames.
- Fixed MiniBrowser Chromium1TextResultAvailable declaration.
This commit is contained in:
Salvador Díaz Fau
2018-06-27 10:17:34 +02:00
parent 5f82e1ace3
commit 55aa9965df
3 changed files with 46 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
demos/JavaScript/JSExtension/uJSExtension.pas
View File

@ -134,36 +134,49 @@ uses
// The CEF3 document describing extensions is here :
// https://bitbucket.org/chromiumembedded/cef/wiki/JavaScriptIntegration.md
// The Chromium project document describing Chromium's architecture is here :
// http://www.chromium.org/developers/design-documents/multi-process-architecture
// This demo has a JavaScript extension class that is registered in the
// GlobalCEFApp.OnWebKitInitialized event when the application is initializing.
// The extension in this demo is called "myextension" and it has 2 functions called "mouseover" and "sendresulttobrowser".
// When the JavaScript code uses those functions it executes the TTestExtensionHandler.Execute function in uTestExtensionHandler.pas
// The extension in this demo is called "myextension" and it has 2 functions called
// "mouseover" and "sendresulttobrowser".
// The TTestExtensionHandler.Execute function is executed in the renderer process and it can use the
// TCefv8ContextRef.Current.Browser.SendProcessMessage(PID_BROWSER, msg) to send a message with the results to the browser process.
// When the JavaScript code uses those functions it executes the TTestExtensionHandler.Execute
// function in uTestExtensionHandler.pas.
// TCefv8ContextRef.Current returns the v8 context for the frame that is currently executing JavaScript,
// TCefv8ContextRef.Current.Browser.SendProcessMessage sends a message to the right browser even
// if you have created several browsers in one app.
// When you run this demo and you select the "Set the mouseover event" menu option, the
// TChromium.OnContextMenuCommand event is triggered and it adds an event listener to the
// document's body. That listener calls one of the functions available in the registered
// extension called "myextension.mouseover".
// The TTestExtensionHandler.Execute function is executed in the renderer process and it
// can use the TCefv8ContextRef.Current.Browser.SendProcessMessage(PID_BROWSER, msg) function
// to send a message with the results to the browser process.
// TCefv8ContextRef.Current returns the v8 context for the frame that is currently
// executing JavaScript, TCefv8ContextRef.Current.Browser.SendProcessMessage sends a message
// to the right browser even if you have created several browsers in one app.
// That message is received in the TChromium.OnProcessMessageReceived event.
// Even if you create several TChromium objects you should have no problem because each of them will have its own
// TChromium.OnProcessMessageReceived event to receive the messages from the extension.
// Even if you create several TChromium objects you should have no problem because each of
// them will have its own TChromium.OnProcessMessageReceived event to receive the messages
// from the extension.
// When run this demo and you select the "Set the mouseover event" menu option, the Chromium1ContextMenuCommand event
// is triggered and it adds an event listener to the document's body. That listener calls one of the functions
// available in the registered extension called "myextension.mouseover".
// TChromium.OnProcessMessageReceived receives that message and shows the information in
// the status bar.
// TChromium.OnProcessMessageReceived receives that message and shows the information in the status bar.
// If you have to debug the code executed by the extension you will need to use the debugging methods described in
// If you have to debug the code executed by the extension you will need to use the
// debugging methods described in
// https://www.briskbard.com/index.php?lang=en&pageid=cef
// Destruction steps
// =================
// 1. FormCloseQuery sets CanClose to FALSE calls TChromium.CloseBrowser which triggers the TChromium.OnClose event.
// 2. TChromium.OnClose sends a CEFBROWSER_DESTROY message to destroy CEFWindowParent1 in the main thread, which triggers the TChromium.OnBeforeClose event.
// 1. FormCloseQuery sets CanClose to FALSE calls TChromium.CloseBrowser which triggers
// the TChromium.OnClose event.
// 2. TChromium.OnClose sends a CEFBROWSER_DESTROY message to destroy CEFWindowParent1
// in the main thread, which triggers the TChromium.OnBeforeClose event.
// 3. TChromium.OnBeforeClose sets FCanClose := True and sends WM_CLOSE to the form.
procedure GlobalCEFApp_OnWebKitInitialized;