EQL5/Qt_EQL_plugin at master - mirrors/EQL5

mirror of https://gitlab.com/eql/EQL5.git synced 2025-12-05 18:20:28 -08:00

History

polos 3501d8e5ac plugin example: change template from 'dll' to 'plugin'		2019-02-28 20:32:02 +01:00
..
Qt	add module :webengine (tested with Qt 5.8)	2017-03-25 17:03:58 +01:00
ini.lisp	port of EQL/Qt4 to Qt5	2016-11-25 23:30:38 +01:00
qt_plugin.cpp	unix: add "make install" option for exe, lib, modules (refactor file locations)	2017-04-28 12:05:59 +02:00
qt_plugin.h	for MinGW: change "Q_OS_WIN" to "Q_CC_MSVC" (otherwise MinGW won't link plugins)	2017-02-21 10:06:50 +01:00
qt_plugin.pro	plugin example: change template from 'dll' to 'plugin'	2019-02-28 20:32:02 +01:00
README.txt	port of EQL/Qt4 to Qt5	2016-11-25 23:30:38 +01:00

README.txt

*** N.B: MS folks: You'll need Windows >= 7 ***


INTRO / DESCRIPTION
===================

This is a very basic example of using EQL in a Qt plugin.
So, if some 3rd party Qt application offers a way to integrate Qt plugins, you
can use EQL for your plugin.

We assume that the 3rd party application offers us a QWidget as parent for
our plugin. In this example it's a QDockWidget, which is bound to
eql:*qt-main* in Lisp.



BUILD / RUN
===========

- build dummy application in "Qt/"
- build plugin in this directory
- run the "qt_application" executable



NOTES
=====

See also the function "set-data" in "ini.lisp": it shows a simple way for data
exchange between the application and the plugin.
It uses a dynamic Qt property, which can be accessed from both sides, C++ and
Lisp, since the property is added to the plugin parent widget of the application:
"pluginWidget" in C++, "*qt-main*" in Lisp.