From Free Pascal wiki
Jump to navigationJump to search

English (en) español (es)

Acerca de

CEF4Delphi es un envoltorio, una interfaz, en Pascal para el "Chromium Embedded Framework". Este permite a Lazarus para embeber un navegador web basado en la maquinaria de Chromium.

En estos momentos está soportado para aplicaciones creadas con Lazarus para Windows y Linux(GTK-2) con objetivo x86_64 (para i386 están pendientes las pruebas).

Desde la versión 2.1 (trunk) de Lazarus hay soportr para Cocoa x86_64. (Cocoa no incluye toda la funcionalidad del modo OSR, pero en modo normal de ventanas todas las funciones están disponibles).

CEF4Delphi está basado en fpCEF3


The CEF4Delphi documentation can be found at https://www.briskbard.com/index.php?lang=en&pageid=cef

Forum: https://www.briskbard.com/forum/

The CEF documentation is at https://magpcss.org/ceforum/apidocs3/

Forum: https://magpcss.org/ceforum/


CEF4Delphi is available in the Online Package Manager.

In order to get the full feature set, you may need to install from the "external repository".

The git repository can be found here: https://github.com/salvadordf/CEF4Delphi

The framework binaries can be found here: https://cef-builds.spotifycdn.com/index.html

There version need to match the version expected by the CEF4Delphi package. See git commit log https://github.com/salvadordf/CEF4Delphi/commits/master

The version check can be disabled for basic testing: "GlobalCEFApp.CheckCEFFiles := false;". However this should not be done for releases or more complex projects.


The usage is described in the documentation at https://www.briskbard.com/index.php?lang=en&pageid=cef

Quick Starters

The simplest way is to look at the following 2 demos:

A demo to show how to use a browser that will exist for the life-time of the application. (I.e. the browser is only closed, when the application exits)
A demo that shows how to dynamically create and close browsers in your application

Make sure to read:

  • the part of the documentation (link) on downloading and installing the "CEF binaries".
  • The README.txt in each demo-app's folder

Before writing your own app, read the comments on top of uCEFBrowesWindow.pas

Optionally explore the settings in each demo-app's GlobalCefApplication.pas

Event properties

Many events (OnSomeEvent), including many of those assignable from the Object-Inspector will be executed in threads created by CEF. Events in threads are not allowed to access any components (Forms, Button, entire LCL...), and also restricted in what calls they may make to the OS. For other data they may need CriticalSections or similar. See the linked documentation.

Some events are executed in a different Process. They can not even share Global variables. See the DOM demos on how communication is done.

You can check the CEF documentation for each event.


On Linux CEF must be setup before the application creates any threads. Since gtk may create threads, CEF must be initialized before the LCL widgetset initializes gtk2.

This requires modifications to the project.lpr file.

In the demos, this is done by including a unit in the "uses" clause, before the "unit interfaces". In that unit is a "initialization" section, and that runs before the widgetset (if units are used in the correct order)

macOS (Cocoa) - NSPrincipalClass

On macOS the application Info.plist file must be modified to set NSPrincipalClass to TCrCocoaApplication.

There are scripts provided to do that. The scripts also put the "Helper apps" in place. (Assuming you compile them first / See the README.txt files).

Under Lazarus 2.1 (trunk) the NSPrincipalClass can be set in the "Project options".

Cocoa on Lazarus 2.0.12

In order to use CEF4Delphi with Cocoa x86_64 you must patch your Lazarus 2.0.12 version: Patch.

Human readable Patch.