fix READMEs; add screenshot;
This commit is contained in:
parent
56462145ee
commit
0e4c00499a
3 changed files with 7 additions and 8 deletions
|
|
@ -10,13 +10,10 @@ See "trafficlight/" for an example of integrating a Qt/C++ application.
|
|||
NOTES
|
||||
=====
|
||||
|
||||
This offers the same possibilities as found in the "Qt_EQL/" example,
|
||||
but with a better, more dynamic workflow, and without the restriction of
|
||||
"CONFIG += no_keywords" in your "*.pro" file.
|
||||
|
||||
So, integrating any existing Qt/C++ project is straightforward, since you can
|
||||
call any property/method/slot/signal of any Qt class (see QFIND-CHILD,
|
||||
QFIND-CHILDREN, QFUN+).
|
||||
Integrating with existing Qt/C++ projects should be straightforward, since
|
||||
you can call all standard methods/slots/signals of any Qt class (see
|
||||
QFIND-CHILD, QFIND-CHILDREN, QFUN+), and additionally make your own C++
|
||||
functions callable by declaring them Q_INVOKABLE.
|
||||
|
||||
Calling Lisp from C++ through "eql_fun()" is easy, and you can use any Qt
|
||||
class/type supported by EQL, see examples in "cpp_calling_lisp/lib.cpp".
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
You'll need cl-opengl (see Quicklisp)
|
||||
|
||||
Run it: eql run.lisp
|
||||
Run it:
|
||||
|
||||
eql5 run.lisp
|
||||
|
|
|
|||
BIN
screenshots/examples.png
Normal file
BIN
screenshots/examples.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 119 KiB |
Loading…
Add table
Reference in a new issue