CapeSoft Chrome Explorer
Documentation

• Introduction
• Webinars
• Requirements
• Features
• Support
• Installing  VERSION 1.0x  - Important - Read this
  • RED file requirements
• Converting From CapeSoft File Explorer
• Acknowledgements
• License & Copyright
• Chromium Embedded Framework (CEF)
  • Support for Audio and Video
• ChromeExplorerProcess.Exe
• CK Editor
• ACE Code Editor
• Shipping / Distribution
• Browser Settings
  • Cache Path
  • Ignore Certificate Errors
  • Locale
  • Log File
  • Log Severity
  • User Agent
• Adding Chrome Explorer to Your Application
  • Global Extension
  • Global Properties - Legacy (Clarion) Templates
  • Web Browser Control Template
  • Navigation Buttons Control Template
  • Search Control Template
  • HTML Editor Control Template
• String Encoding
• Common Techniques
  • Loading Something into the Control
  • Binding a String or Blob to a Control
  • Retrieving the Contents of an HTML Page
  • Running JavaScript on the Page
  • Calling A JavaScript Function with a Return Value
  • Navigation
  • Printing
  • Print to PDF
  • Resizing
  • Hide and Unhide
  • Prevent Navigation to a URL
  • Redirect Navigation to a Different URL
  • Inspecting Request Data
  • Click an Element on the Page
  • Set a Value on the page
  • Sending an Event to an Element on the Page
  • Drag and Drop onto the Control
  • Right-Click Popup Menu
  • Proxy Servers
  • PDF Command Line
  • Developer Tools
• Downloads
• POST, GET, PUT, DELETE
• HTML Editor
  • On Form Procedure
  • On Window Procedure
  • Downloading a Custom Version (CK Editor)
  • Assigning a Custom Version (CK Editor)
    
  • Changing the Editor Language (CK Editor)
    
  • Manipulating the Text in the Control
  • Trapping Errors After Calling SaveFile
  • Setting a Theme (Ace Editor)
  • Setting a Language(Ace Editor)
  • Setting a Options(Ace Editor)
• Examples
• Hand-Coding
• Selectors
• Template Reference
  • Activate ChromeExplorer Global Extension
  • ChromeControl Control Template
  • ChromeControl Navigation Control Template
  • ChromeEditControl Control Template
• Structure Reference
• Class Reference
• Trouble Shooting / FAQ
• Version History

ChromeExplorer requires StringTheory 3 or later.

ChromeExplorer allows you to include a Chromium based browser control in your application. You use a control template to simply place an HTML control on your window.

An HTML Editor class is also included (based on the CKEditor 4 control.) This allows your user to edit HTML in a WYSIWYG way.

First Release Webinar on ClarionLive is at https://www.clarionlive.com/BrowseEpisodes/ww!553 (Start at 19:40 because there is a long introduction of other things)

Another Webinar (https://www.clarionlive.com/BrowseEpisodes/ww!615) after the 1.30 release discusses the embed code in the example in detail, and looks at new features like the ACE Code editor, using the ACE editor with the CK editor, and calling JavaScript.

Interacting with web pages, and web sites can become complicated because of String Encoding issues. If you are not familiar with the notion of string encoding, then the webinar #583 is strongly recommended. https://www.clarionlive.com/BrowseEpisodes/ww!583

For a practical look at how String Encoding affects Chrome Explorer see https://www.clarionlive.com/BrowseEpisodes/ww!584

To compile, ChromeExplorer requires StringTheory 3 or later.

If you are using Resize And Split then make sure you are on build 5.03 or later of that. Failure to do this will result in your program disappearing when the ChromeExplorer window is opened (and other explained "funnies".)

To run, ChromeExplorer requires Windows Vista or later. ChromeExplorer may work, but is not supported on Windows XP.

The Chrome browser does not need to be installed on the computer. If the Chrome browser is installed on the computer, it does not affect your program.

• Add a Web Browser control to a Clarion window
  • Multiple controls per window are supported
  • Can display any file your browser can display, including HTML, PDF and so on
  • Load URL's from web, or Files from disk, or Memory from String or Blob
  • Bind a Field (STRING, CSTRING or BLOB) to the Control
  • Update controls automatically on Browse New Selection
  • Get HTML Source for the displayed page
  • Execute JavaScript on a web page.
  • Address Bar and Page Title fields can auto-sync as the user navigates
• Add an HTML Editor Control to a Clarion Window
  • Multiple controls per window are supported
  • Bind a Field (STRING, CSTRING or BLOB) to the Control.
  • Use on a Form just like any other form field.
• All source code (except for the Chromium Engine itself.) - No Clarion compiled DLL's
• Independent of the Chrome Browser (which may, or may not, be installed.)

Your questions, comments and suggestions are welcome. Check our web page (https://www.capesoft.com/accessories/downloads.htm) for new versions. You can also contact us in one of the following ways.

CapeSoft Support
Email
Telephone	+27 87 828 0123 (087) 828 0123

• Run the supplied installation file.

IMPORTANT

1. Open the \clarion\accessory\ChromeExplorerProcess\ChromeExplorerProcess.Sln solution and compile it. See ChromeExplorerProcess.

RED File Requirements

Because of the intrinsic differences between the File Explorer OCX approach and the separate-process approach used by Chromium, it is not practical to create a "simple" upgrade from File Explorer to Chrome Explorer.

Fortunately most applications do not use lots of File Explorer controls, so converting from FileExplorer is simply a case of removing the File Explorer control, and adding the Chrome Explorer control to the window.

On the Clarion side, all the hard work in this product has been developed by Dries Driessen. It is thanks to his skill and tenacity that this product exists.

The Chromium Embedded Framework is Copyright (c) 2008-2020 Marshall A. Greenblatt. Portions Copyright (c) 2006-2009 Google Inc. All rights reserved. It is included here under the terms of the license (https://bitbucket.org/chromiumembedded/cef/src/master/LICENSE.txt)
Please take a moment to read this license as it may affect your own product documentation requirements.

The CKEditor 4 is Copyright 2003-2020 by CKSource and Frederico Knabben. It is included in this product under the terms of their license options at https://ckeditor.com/legal/ckeditor-oss-license/ . If you are using the CKEditor you should be aware of their Terms of Use - https://ckeditor.com/legal/terms-of-use/
You can create a custom version of the editor, using your own choice of features and plugins at https://ckeditor.com/cke4/builder .

The ACE Code Editor  is Copyright (c) 2010 by Ajax.org B.V. It is included here under the terms of the BSD license.

The template and classes in this product are Copyright 2021 by CapeSoft Software CC.

Each developer needs his own license to use Chrome Explorer. (Need to buy more licenses?)

The ChromeExplorerProcess Exe is copyright 2021 by CapeSoft Software CC. It can be distributed without restriction with any program that uses the Chrome Explorer classes.

This product is provided as-is. Use it entirely at your own risk. Use of this product implies your acceptance of this, along with the recognition of copyright stated above. In no way will CapeSoft Software CC, their employees, contractors, contributors or affiliates be liable in any way for any damages or business losses you may incur as a direct or indirect result of using this product.

CKEditor 4 is Copyright 2003-2021 by CKSource and Frederico Knabben. It is included in this product under the terms of their license options at https://ckeditor.com/legal/ckeditor-oss-license/ . If you are using the CKEditor you should be aware of their Terms of Use - https://ckeditor.com/legal/terms-of-use/

The CEF Engine is  Copyright (c) 2008-2021 Marshall A. Greenblatt. Portions Copyright (c)  2006-2009 Google Inc. All rights reserved.

The ACE Code Editor  is Copyright (c) 2010 by Ajax.org B.V.

The Chromium Embedded Framework 3 (CEF) is based on open-source code which is the code that underlies many of today's browsers including Chrome, Opera and Edge.

The files shipped with Chrome Explorer are self-contained. The user does not need to have the Chrome browser installed, and if they do have the Chrome browser installed then this behaves separately to that.

Because the Chromium engine is updated on an almost continuous basis it is expected that regular Chrome Explorer updates will happen as well. In order for your application to use the latest Chromium engine you should plan to update your Chrome Explorer version more or less every quarter. Of course older engines will continue to function, probably for a long period of time, but staying more-or-less up to date can limit surprises with sites that require the most modern browser features.

The full text of the CEF License is available at https://bitbucket.org/chromiumembedded/cef/src/master/LICENSE.txt

The important parts to know are;

The CEF Engine is  Copyright (c) 2008-2021 Marshall A. Greenblatt. Portions Copyright (c)  2006-2009 Google Inc. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are  met:

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
• Neither the name of Google Inc. nor the name Chromium Embedded Framework nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
• THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
  // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  

Support for Audio and Video

The CEF code runs in a separate process, using the supplied utility (ChromeExplorerProcess.Exe). This means that even if the Chromium engine code should crash for some reason, your application will not.

After installing ChromeExplorer you should compile the ChromeExplorerProcess program. To do this;

1. Open the IDE
2. Load \Clarion\Accessory\ChromeExplorerProcess\ChromeExplorerProcess.Sln
3. Click on the "build Solution" button
4. Close the Solution.

To provide HTML editing functionality the CK Editor, version 4, is included with Chrome Explorer. The latest version of the editor can be downloaded from https://ckeditor.com/ckeditor-4/download/.

Important: The editor contains an enormous slew of functions, probably more than you expect or imagine. It is worth taking the time to see what features are available, so you can best decide which features to include in the control in your application. Advanced features like View/Edit the HTML source directly as well as Paste-From-Word and Paste-From-Excel can easily be included, or excluded from the editor.

The editor is available in 3 versions - the difference being the complexity of the toolbar that the user will see. Chrome Explorer ships with all three versions, so you can choose which one(s) to use in your application. The Control template lets you select which one will be used.

You can also create, and download, one or more Custom versions of the editor from the downloads link. The control template supports you selecting your preferred version, or your custom version.

The ones shipping with Chrome Explorer are as follows;

• Basic: CK Editor Basic (Bold, Italic, Lists, Links)  + "Color Button" + "Font-Size & Family" + "HTML Output Writer"
• Standard: CK Editor Standard + "Color Button" + "Font-Size & Family"
• Full: CK Editor Full

You can read more at HTML Editor .

Note 1
The Chrome Explorer shipping folders (\clarion\accessory\bin\...) with the CKEditor component contain all the languages, and all the skins supported by the editor. You can reduce the size of the install by limiting the languages and skins you ship. If you do not use the HTML Editor in your program you do not need to ship these files at all.

Note 2
The CKEditor version 4 is chosen over version 5 because of the license restrictions of version 5. If you wish to use version5, and have a license to do so, then it is fairly straight-forward to construct your CkEditor5.Htm file, and ship it with the CK Editor 5.

Chrome Explorer provides code editing using the ACE Code editor.the latest version of this editor can be downloaded from https://ace.c9.io/

The ACE editor is a full-featured source editor which supports over 35 themes, and over  160 programming languages (and no, Clarion is not one of them.)
While the vast majority of languages won't be terribly useful in a Clarion program, supported languages include Ascii, INI, Text, Markdown, XML, JSON, HTML, CSS, JavaScript, PHP, Powershell, SQL, SQL Server, MySQL, pgSQL, and Powershell all of which could easily be useful in a program.

Apart from the theme and language (what ACE calls the mode) there are also many other features and options, way too many to detail here. For a "kitchen sink" example of the editor where you can see every possible option, and experiment with it, see https://ace.c9.io/build/kitchen-sink.html .

You can read more at HTML Editor .

Note 1
The Chrome Explorer shipping folder (\clarion\accessory\bin\ace\src-noconflict) contains mode files for all the supported programming languages, and theme files for all supported themes. If you do not need all these in your application then you can reduce the size of your install by removing files that are not needed.

As mentioned earlier, the CEF engine is a completely self-contained browser. Because of this there is a fair amount of items that need to be included in the install file you create for your program.

Web Browser Control

Web Editor Control

The following Browser settings are set when the program starts. These settings are made on the Chrome Explorer extension template, on the Settings tab. Although you can use expressions here (ie variables) instead of fixed values, these expressions are used once, on program startup, so any variables used would need to be primed early, before these variables are used. An embed point Before Chrome Explorer Settings is provided for this purpose.

Note that in Multi-DLL setups, if ABC, then these settings, and code, go in the Data DLL. If a Legacy app then it goes into the Exe app.

• Cache Path
• Ignore Certificate Errors
• Locale
• Log File
• Log Severity
• User Agent

Cache Path

Ignore Certificate Errors

Locale

Log File

Log Severity

User Agent

Global Extension

Global Properties - Legacy (Clarion) Templates

Web Browser Control Template

Navigation Buttons Control Template

Search Control Template

HTML Editor Control Template

For a primer on string encoding, and why it matters, see webinar #583 https://www.clarionlive.com/BrowseEpisodes/ww!583

It is not uncommon for web sites to include characters that are non-ASCII characters on the page, or in entry fields. When you programmatically interact with these pages, those characters have to be encoded so that your program can understand them.

For example;

GetHTMLSource let's you get the source code for the page currently being displayed. That source code may contain, say, Spanish characters. Once the source code ends up in a string in your program, the encoding of the string will matter.

For this reason, methods that interact with the raw text of the page have optional parameters which let you specify the encoding, and if necessary, the code page you wish to use.

There are three primary encodings supported. UTF-8 and UTF-16 are Unicode encodings. As at the time of writing this (Clarion 11), Clarion does not have native support for strings encoded as UTF-8 or UTF-16. That said, you can work with these strings, using StringTheory or similar.

To display the data on a Clarion screen, or report, you will need to convert it to ANSI. This could result in some data loss because ANSI makes use of code pages to encode the string. So if the web site was say in Spanish, then you would use the Spanish Code Page in your Clarion program.

You can store UTF-8 data in STRING or CSTRING variables. (You can't display it, but you can store it.) UTF-16 data can be stored in a STRING, but it CAN NOT be stored in a CSTRING variable.

When calling the various methods you can determine which encoding you prefer. You are then free of course to further convert this encoding on your own if you wish to do so. Once the Clarion USTRING data type becomes available, you may choose to keep the data encoded as UTF-16.

The following methods in the CEF_Class all have support for specifying the encoding. In all cases the default encoding is ANSI, with the code page that matches the System{prop:Charset} of your application.

• BindSource
• Load
• LoadFromBlob
• LoadFromString
• GetHTMLSource
• GetTextSource
• Script
• SetValue
  

The following methods in the CEF_EditorClass have support for specifying the encoding;

• BindSource
• InsertHTML
• InsertText
• ReplaceText

The HTML Editor Control Template contains template settings for setting the encoding, and code page, of the data for the control.

You can specify the Code Page to use. Any Windows code page number is valid, for a subset see StringTheory.Inc
The most commonly used ones are;
st:CP_WINDOWS_1250  ! Central / Eastern Europe
st:CP_WINDOWS_1251  ! Cyrillic
st:CP_WINDOWS_1252  ! Western Europe / Scandinavia
st:CP_WINDOWS_1253  ! Greek
st:CP_WINDOWS_1254  ! Turkish
st:CP_WINDOWS_1255  ! Hebrew
st:CP_WINDOWS_1256  ! Arabic
st:CP_WINDOWS_1257  ! Baltic
st:CP_WINDOWS_1258  ! Vietnamese
st:CP_WINDOWS_874   ! Thai
st:CP_Big5          ! ANSI/OEM Traditional Chinese (Taiwan; Hong Kong SAR, PRC); Chinese Traditional (Big5)
st:CP_WINDOWS_936   ! NSI/OEM Simplified Chinese (PRC, Singapore); Chinese Simplified (GB2312)

• Loading Something into the Control
• Binding a String or Blob to a Control
• Retrieving the Contents of an HTML Page
• Running JavaScript on the Page
• Calling a JavaScript Function with a Return Value
• Navigation
• Printing
• Resizing
• Hide and Unhide
• Prevent Navigation to a URL
• Redirect Navigation to a Different URL
• Inspecting Request Data
• Click an Element on the Page
• Set a Value on the page
• Sending an Event to an Element on the Page
• Drag and Drop onto the Control
• Right-Click Popup Menu
• Proxy Servers

Loading Something into the Control

Binding a String or Blob to a Control

Retrieving the Contents of the HTML Page

Running JavaScript on the Page

Calling a JavaScript Function with a Return Value

Navigation

Printing

Resizing

Hide and Unhide

Prevent Navigation to a URL

Redirect Navigation to a Different URL

Inspecting Request Data

Click an Element on the Page

Set the value of an Element on the Page

Send an Event to an Element on the Page

Drag and Drop onto the Control

Right-Click Popup Menu

ProxyServers

PDF Command Line

Developer Tools

Downloads on a Chrome Explorer Control are set to OFF by default. To allow downloads set the Allow Downloads checkbox on the control actions (Downloads tab.)

You can specify the download location, or you can allow the user to choose the location. This is also done via the template settings.

Methods are supplied which allow you to oversee the files being downloaded, and to take action after the file has been downloaded; StartDownload, OnBeforeDownload, OnDownloadUpdated, OnDownloadComplete and onDownloadCancel.

The Control template now has a Progress Control which automatically unhides, and progresses, as a download occurs.

This section discusses making an arbitrary request from the browser control. It is not about intercepting requests. For details on that see....

Using Chrome Explorer it is possible to make an explicit request from the control, even if the page currently being viewed does not specifically contain a button, or link to make this request. There are four methods, which correspond to the four most common HTTP request verbs; Post, Get, Put and Delete .

The result of the request will appear in the control on the window.

NOTE: Although the page being viewed does not need to include a link to the server you wish to talk to, a valid page MUST be loaded into the control before this request can be made. Setting the URL to about:blank will load a valid (blank) page if you are not currently on a page..

Note: Requests are asynchronous . So each request needs to wait until the response is received before another request can be made. If requests are simply made after each other, then only the final request will actually execute.

A request consists of up to 5 parts;
 

Form Field Data

Specific Headers

Cookies

URL

Method

Examples

• On Form Procedure
• On Window Procedure
• Downloading a Custom Version (CK Editor)
• Assigning a Custom Version (CK Editor)
  
• Changing the Editor Language (CKEditor)
  
• Manipulating the Text in the Control
• Trapping Errors After Calling SaveFile
• Setting a Theme (Ace Editor)
• Setting a Language(Ace Editor)
• Setting a Options(Ace Editor)

The HTML Editor functionality makes use of the CEF_EditorClass, and the ChromeEditControl Control Template.

The CKEditor 4 HTML editor (in either Basic, Standard, Full or Custom mode) and the ACE Code editor are supported. You can create a custom version of the editor, using your own choice of features and plugins at https://ckeditor.com/cke4/builder .

Unless noted in the documentation below, the instructions for the editors are the same.

On Form Procedure

On Window Procedure

Downloading a Custom Version (CK Editor)

Assigning a Custom Version (CK Editor)

Changing the Editor Language (CKEditor)

Manipulating the Text in the Control

Trapping Errors after calling SaveFile

Setting a Theme (ACE Editor)

Setting a Language (ACE Editor)

Setting an Option (ACE Editor)

Examples are located in the location you chose for them during the install. This section lists the shipping examples, and what their purpose is.

Example	Description
\examples\ChromeExplorer\ABC	The main demo app, using ABC templates, demonstrating most of the common features.
\examples\ChromeExplorer\Legacy	The main demo app, using Clarion (Legacy) templates, demonstrating most of the common features.
\examples\ChromeExplorer\NetOAuth\ABC	ABC version of an example (from NetTalk) of using OAuth Logins using the ChromeExplorer Control instead of the fileExplorer Control. The OauthLogin procedure is affected.
\examples\ChromeExplorer\NetOAuth\Legacy	The Legacy version of an example (from NetTalk) of using OAuth Logins using the ChromeExplorer Control instead of the fileExplorer Control. The OauthLogin procedure is affected.
\examples\ChromeExplorer\MultiDLL\ABC\	ABC version of multi-dll example. Classes exported from Data DLL, Functions and Exe apps as well.
\examples\ChromeExplorer\MultiDLL\Legacy\	Legacy version of multi-dll example. Classes exported from Data DLL, Functions and Exe apps as well.

Using the various Extension and Control Templates is the easiest way to use Chrome Explorer in a program. However it is also possible to use Chrome Explorer on a hand-coded window in a hand-coded application.

when interacting (clicking, setting values etc) with a loaded page you need to be able to identify the item that you want to interact with. For example, if you wish to click on a submit button, then you need a way to identify the button you wish to click. This is done using Selectors.

Selectors allow you to identify one (or more) items on the page that meet your specification - ideally you can narrow your specification to a single item, and then interact with that. If you can't reduce the list to a single item, then you can use an Index parameter to indicate which item in the list is being acted on. The first item in the list has the index 0, the next index 1 and so on.

All selectors are Case Sensitive.

Selector	Example	Example Description
.class	.name	selects all elements that have, as one of their CSS classes, the class called name
.class1.class2	.name1.name2	Selects all elements that have both name1 and name2 in their CSS class list
.class1 .class2	.name1 .name2	selects all elements with a CSS class name2, which is also a descendant of an element with a CSS class name2
#id	#savebutton	Selects the element where the ID is set to savebutton
*	*	Selects everything on the page. (Everything!)
element	a	Selects all the <a> elements on the page
element.class	a.green	Selects all the <a> elements that also have a CSS class green in their CSS list.
element , element	div, span	Selects all div elements and all span elements
element > element	div span	Selects all span elements that are inside div elements
element + element	div + span	Selects all span elements that are immediately after a div element
element1~element2	span ~ div	Selects every div element that is preceded by a span element
[attribute]	[target]	Selects all elements that have an attribute called target
[attribute=value]	[target=_blank]	selects all elements that have an attribute called target, and where that attribute is set to _blank
[attribute~=value]	[title~=flower]	selects all elements that have an attribute called title, and where that attribute contains the word flower in a space separated list. (ie not the letters flower, but the distinct word flower separated by spaces from the other words)
[attribute|=value]	lang|=en	Finds elements that start a dash-separated list. So in this case, find all elements that have an attribute called lang, where the value starts with en-
[attribute^=value]	a[href^="https"]	selects all <a> elements that have an attribute called href, and where that attribute starts with  https
[attribute$=value]	a[href$=".pdf"]	selects all <a> elements that have an attribute called href, and where that attribute ends with .pdf
[attribute*=value]	a[href*="cef"]	selects all <a> elements that have an attribute called href, and where that attribute contains the substring cef

This is only a partial list of supported selectors. For more information see https://www.w3schools.com/cssref/css_selectors.asp

• Activate ChromeExplorer Global Extension
• ChromeControl Control Template
• ChromeControl Navigation Control Template
• ChromeControl Search Control template
• ChromeEditControl Control Template

Templates

Activate ChromeExplorer Global Extension

Templates

ChromeControl Control Template

Templates

ChromeControl Navigation Control Template

Templates

ChromeControl Search Control Template

Templates

ChromeEditControl Control Template

• CEF_PdfPrintSettings

CEF_PdfPrintSettings

• CEF_BaseClass
  • CEF_ProcessClass
    • CEF_GlobalClass
    • CEF_Class
      • CEF_EditorClass
• CEF_EA_BaseEventArgsClass
• CEF_EA_LoadingStateChangeEventArgsClass
• CEF_BaseResponseClass
• CEF_ScriptResponseClass

Classes

CEF_BaseClass

Classes

CEF_ProcessClass

Classes

CEF_GlobalClass

Classes

CEF_Class

Classes

CEF_EditorClass

Classes

CEF_EA_BaseEventArgsClass

Classes

CEF_EA_LoadingStateChangeEventArgsClass

Classes

CEF_BaseResponseClass

Classes

CEF_ScriptResponseClass

1. Any of the following warnings during compiling;

• v8_context_snapshot.bin was not copied to the target directory because it could not be found via redirection lookup
• snapshot_blob.bin was not copied to the target directory because it could not be found via redirection lookup
• natives_blob.bin was not copied to the target directory because it could not be found via redirection lookup
• cef_extensions.pak was not copied to the target directory because it could not be found via redirection lookup
• cef_200_percent.pak was not copied to the target directory because it could not be found via redirection lookup
• cef_100_percent.pak was not copied to the target directory because it could not be found via redirection lookup
• cef.pak was not copied to the target directory because it could not be found via redirection lookup

Your RED file has not been set correctly.

22. The following warning during compilation

ChromeExplorerProcess.Exe was not copied to the target directory because it could not be found via redirection lookup

Compile the project which is in \clarion\accessory\ChromeExplorerProcess
See ChromeExplorerProcess.Exe

3. Program does not start. Debugview Shows something like;

FATAL:v8_initializer.cc(176)] Failed to open V8 file 'C:\Clarion11\Examples\ChromeExplorer\ABC\natives_blob.bin' (reason: -4)

The necessary BIN and PAK files are missing from the application directory. See Shipping / Distribution.

4. Program does not start. Debugview shows something like;

[ERROR:icu_util.cc(183)] Couldn't mmap icu data file

The necessary DAT file is missing from the application directory. See Shipping / Distribution.

5. Program starts, but displays message "ChromeExplorerProcess.Exe is missing".

The necessary EXE file is missing from the application directory. See Shipping / Distribution.

6. Program Starts, but controls do not display. Debugview shows something like;

ERROR:browser_gpu_channel_host_factory.cc(138)] Failed to launch GPU process.

ChromeExplorerProcess.Exe is missing from your application folder. See Shipping / Distribution.

7. Program starts, but when opening a control you see

ChromeExplorerProcess.Exe or one of it's DLL's was linked to a Clarion RTL Version older than xxx.

Rebuild ChromeExplorerProcess.Exe. See Shipping / Distribution.

8. When Right-Mouse clicking on the control, a blank popup appears.

The Locales folder is missing. See Shipping / Distribution..

9. When Right-Mouse clicking on the control a popup in the wrong language appears.

You can set the "Locale" of the browser using the Global Template option. See Locale.

10. When running the program, the following error message appears.

Procedure entrypoint SymFromAddr not found in DLL-library libcef.dll

Look for a file in application folder called DbgHelp.Dll and delete it.

• Version 1.31 - 13 July 2021
  Don't Forget to Rebuild \Accessory\ChromeExplorerProcess
  Add: Template option to copy ACE Editor (on by default)
  Fix: ACE Editor folder was  not included in CopyChrome.Bat
  Fix: Code in OnLoaded event was being generated before the parent call, switched to after.
  Fix: InitEditor should not run if EditorLoaded is false
  
  
  
• Version 1.31 - 8 July 2021
  Add: OnScriptFailure sends a line to Debugview by default.
  Add: Cef_Class methods PrintPDF, OnPDFPrintFinished
  Add: ChromeControl Navigation Control Template now has new PrintPDF button.
  Update: Editor: JavaScript editorSaveText function updated to return edited text.
  Update: HTML Editor switched from using Script to CallScript method when saving.
  Update: GetFrameNames does a JOIN on the passed p_Names parameter.
  Change: PrintPage method returns cef:ok and cef:notok, not true / false.
  Fix: Possible incorrect frame use when  no frame name passed.
  Fix: Delayed loads in editor could cause editor content to refresh from source.
  Fix: UpdateSource assumed that an Event:Completed was always underway.
  
  
• Version 1.30 - 14 June 2021
  Update: CEF version updated to 88.2.9, Chromium to 88.0.4324.182
  Update: CKEditor4 from 4.14.0 to 4.16.1
  Add: ACE Code Editor.
  Add: Calling A JavaScriptFunction with a Return Value
  Add: Support for WebGL2
  Add: Support for Proxy servers
  Add: Support for Developer Tools
  Add: CKEditor: Support for themes (skins). All the skins are included in the CKEditor folders. All languages are included in the CKEditor folders.
  Distribution: natives_blob.bin removed
  Distribution: Optional devtools_resources.pak added.
  Distribution: swiftshader folder added
  Fix: When changing tabs, the control was not always being displayed correctly.
  Documentation: PDF Command Line
  
  
• Version 1.22 - 25 May 2021
  Clarion 11.1 Install
  
  
• Version 1.21 - 20 April 2021
  Fix: ChromeControl extension would generate an Event:CEFUpdate even if (all) extensions were set to not "Update Control on Browse NewSelection".
  
  
• Version 1.20 - 14 April 2021
  Fix: HTML Editor Replace method generated wrapped base64 encodings.
  
  
• Version 1.19 - 6 April 2021
  Fix: HTML Editor Replace method.
  Fix: PrintContent returns a value
  
  
• Version 1.18 - 19 November 2020
  Add: Cef_EditorClass: PrintContent method added.
  
  
• Version 1.17 - 3 November 2020
  Fix: Regression in Click event. In some cases the click event is not sufficient, so reverted to calling the click function.
  
  
• Version 1.16 - 2 November 2020
  Add: Ability to control right-click menu. See Right-Click Popup Menu.
  Add: Template option to enable, or disable right-click menus.
  Add: OnBeforeContextMenu, RunContextMenu, PreventContextMenu
  
  
• Version 1.15 - 26 October 2020
  Fix: Get, Put, Post and Delete used parameters in the wrong order
  Fix: Erratic occasional GPF
  Change: Header manipulation possible for GET as well as POST & PUT.
  
  
• Version 1.14 - 26 October 2020
  Add: Option to make the browse control accept Drag and Drop files. Note that this was ON by default in previous builds, with this option it is now OFF by default. See Drag and Drop onto the Control
  Add: Ability to send Cookies with POST requests, and store cookies from POST requests. This is on by default. See Get, Post, Put, Delete .
  
  
• Version 1.13 - 20 October 2020
  Remove: Blur, PostAccepted methods.
  Add: PostEvent method.
  Fix: Event method.
  Fix: Possible memory leak in DeleteCookie method.
  
  
• Version 1.12 - 12 October 2020
  Add: Support for Unicode and Ansi String Encoding.
  
  
• Version 1.11 - 28 August 2020
  Add: GetBodyHTML, GetDocumentHTML, GetElementAttributeValue, GetElementHTML, GetElementValue, GetHeadHTML  methods
  Fix: InsertText, InsertHtml and ReplaceText methods were not sync'd with the code in the FeEditor.Htm file.
  
  
• Version 1.10 - 5 August 2020
  Fix: Unresolved External on ON_FIND_RESULT
  
  
• Version 1.09 - 1 August 2020
  Add: ChromeControl Search Control template
  Add: SetAllowPopups, Display, Find, StopFind, FindNext, OnFindResult methods.
  Add: Event:CefSelected is sent to a control when it gets "selected"
  Fix: If the window with the control lost the focus to another thread, then regained the focus, the control was not repainted.
  Fix: If the Window was closed, while the control was still constructing, a GPF could occur
  Fix: Template did not suppress call to Kill when template was disabled.
  
  
• Version 1.08 - 13 June 2020
  Fix: In some Multi-DLL cases the close-down could be unreliable. On some occasions the destruct order was different, and so the ChromeExplorerProcesses did not close correctly, causing the exe to not close correctly.
  
  
• Version 1.07 - 10 June 2020
  Update: GET is now working
  Add: IgnoreCertificateErrors global setting
  Add: Insecure Tab to Control template options.
  Fix: Another Multi-DLL Export bug.
  
  
• Version 1.06 - 9 June 2020
  Add: Support for Downloads. Download procedure added to examples.
  Add: Downloads Tab to Control Template
  Add: Various Browser Settings to Global Extension.
  Add: InsertHTML, InsertText and ReplaceText methods to Editor Class.
  Add: POST, GET, PUT, DELETE .  (NOTE: GET is not working yet) GET requires build 1.07
  Add: Progress Control to Control Template.
  Add: Template check for StringTheory.
  Change: Default behavior for BeforeOnPopup changed. New tabs now open by default into the same control.
  Fix: CkEditor.Htm file in CkEditor4Standard folder had an extra line, which caused it to not work.
  Fix: Multi-DLL support was not right. Especially for Legacy apps.
  Add: Multi-DLL Legacy example
  
  
• Version 1.05 - 30 April 2020
  Add: Settings tab to global extension.
  AAdd: BindSource(StringTheory), OnUpdatedSource methods.
  Add: Editor now takes up the full height of the control, and resizes when the control is resized.
  Add: Editor SaveToDisk, OnSaved  methods.
  Add: HtmlFileEditor procedure to example.
  Change: Margin on CKEditor4.Htm page removed. HTML Editor now aligns to the edge of the control on the window.
  Change: CKEditor4 Basic now includes PasteFromWord button, Font-Family and Font-Size plugins.
  Fix: Compile error if not use variable associated with the Edit control.
  Fix: SDI Windows don't see new control size when resizing. Extra event (Event:CefResize)  added.
  Internal: Mild reformatting of SettingsClass , GlobalClass.
  Documentation: CEF_EditorClass reference added. Section on HTML Editor added.
  
  
• Version 1.04 - 24 April 2020
  Fix: When placed on a tab, control does not bleed through to other tabs
  Fix: Display settings with high-DPI, and Font-Size settings of > 100%
  Fix: Enter-To-Accept didn't work on some controls.
  Fix: Default HTML Editor Class name was not right.
  
  
• Version 1.03 - 14 April 2020
  Add: Drive Web window to ABC example
  Fleshed out Doc on Click and SetValue a bit.
  Added: Blur method (same as click)
  
• Version 1.02 - 25 March 2020
  Add: Click and SetValue methods.
  Add: Template Documentation
  Add: HTML Editor template for Legacy
  Add: Multi-DLL support and example
  Add: Accept Enter on URL to trigger refresh template option.
  Fix: Code changed so it compiles in Clarion 8 and Clarion 9
  Fix: Icons added to \accessory\images during install.
  Fix: All classes (and interfaces) read by template class parser.
  
  Outstanding issues;
  Unicode support for GetHTML method.
  Visual artifacts when Windows Font Size > 100%
  Get return values from executed JavaScript code
  Support ResizeAndSplit (currently incompatible.)
  Where do downloaded files go?
  Allow settings for cookies / temp files
  
  
• Version 1.01 - 18 March 2020
  Add: Cef:Stop and Cef:Go equates for use in OnBeforeBrowse method.
  Add: MESSAGE displayed on startup if ChromeExplorerProcess.Exe is missing.
  Add: New OAuth Examples using NetTalk 10+.
  Fix: Template did not include CW20 family, and so could not be added to Legacy apps.
  Fix: Multiple calls to load, before browser finished initializing, could cause a program crash.
  Removed: Spurious error "File does not exist" when generating the first time.
  Debug Logging turned off by default.
  
  
• Version 1.00 - 17 March 2020
  Initial Release.
  TODO:
  Legacy template and examples
  NetOAuthExample
  auto-build ChromeExplorerProcess.exe ?
  Legacy, doesn't like resizing with multiple controls on the same window.
  GPU Cache settings folder