Questions about motif? Contact us
Submitted by Anonymous on Wed, 02/04/2004 - 09:14.
$(Subject) - feasible ?
Fri, 04/30/2004 - 08:16#1
integrating cairo with openmotif ?
From my point of view it isn't feasible, since most of Motif based applications using direct Xlib calls, and so if event Motif used Cairo for rendering, existing application won't be able to get benefits of the engine. Moreover Motif is based on Xt which doesn't support cairo extensions too.
However, possible, I'm wrong. Any ideas?
Sat, 05/01/2004 - 21:44#2
how about replacing the DrawingArea Widget with a
applicatin which needed 2D graphics could easly use the Cairo API
within the widget.
Wed, 05/12/2004 - 13:54#3
This was one of the points in my proposal that the Motif rendition system needs externalizing for 2.3.
At present, the rendition Realize methods of the widget classes, although chained in some respects, are static and singular, and assume Xt.
The proposal was to externalize via plug-in rendition methods. Principally, the concept is to separate the widget into two halves: the data repository, and the rendition engine.
This has a number of benefits:
(a) Alternative skins can be provided dynamically
(b) If you wanted to render the components via OpenGL or whatever, instead of Xt,
you could. Or even Cairo.
(c) this would also allow alternative toolkit rendition, so you could make Motif look like MFC/Mac Aqua if you so wished, by plugging in the appropriate rendition engine
(d) updating the Motif toolkit for whatever becomes the latest fashion and fad doesnt require modification of the base toolkit itself.
You dont need a new widget. You need alternative rendition techniques. Externalizing the rendition engine solves this issue once and for all.