Dear developers,
a cairo support feature is now implemented as discussed with minimal support
API, its option --enable-cairo default is *disabled* so that no changes will be
observed from before the merge if not activated.
Here's an extract of the README.cairo file:
Cairo Support for fltk 1.3
===========================
It is now possible to integrate cairo rendering in your fltk application
more easily and transparently.
In 1.3, we provide minimum support for Cairo,
In particular, no "total" cairo rendering layer support is achieved,
as in fltk2.
Configuration:
-------------
All the changes are *inactive* as long as the new configuration
option --enable-cairo is not added to the configure command.
For non configure based platforms/ide, the HAVE_CAIRO preprocess var.
has to be defined.
All configure based build files has now this feature integrated,
also vc2005 build files have 2 new build modes "Release Cairo" and
"Debug Cairo".
Others IDE's will be updated progressively.
The current support consist in :
-------------------------------
- Adding a new Fl_Cairo_Window class permitting transparent and easy
integration of a Cairo draw callback without the need to achieve subclassing.
- Adding a Fl::cairo_make_current(Fl_Window*) function only providing
transparently a cairo context to your custom Fl_Window derived class.
This function is intended to be used in your overloaded draw() method.
- Adding an optional cairo autolink context mode support (disabled by default)
which permits complete & automatic synchronization of OS dependent graphical
context and cairo contexts, thus furthering a valid cairo context anytime,
in any current window.
This feature should be only necessary in the following cases:
- Intensive and almost systematic use of cairo contexts in an fltk
application
- Creation of a new cairo based scheme for fltk ...
- Other uses of cairo necessiting the flk internals instrumentation
to automatically making possible the use of a cairo context
in any fltk window.
- A new cairo demo that is available in the test subdirectory and has been
used as a testcase durings the multiplatform tests.
For more details, please have a look to the doxygen documentation,
in the Modules section.
Fabien.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
