Making xforms device independent in the sense
that it can render to both X and PostScript
is actually a lot simpler than one might think.
On the object level (FL_DRAW handling for example), X
is not really visible and drawing primitives
(fl_line, fl_poly, fl_drw_box, fl_drw_text etc.) are not that many.
fd2ps already has most of the ps supporting functions there
(ps_line, ps_poly, ps_draw_box, ps_draw_tex etc), I only need to
change fl_line, fl_drw_box etc. into a function pointer and switch
to flx_drw_box or ps_drw_box depending what the context
is (X or PostScript). What I don't like about this
is that it bloats xforms and I can't quite justify
addint it to the xforms proper, I mean how often do people want to
generate a postscript version of the GUI ? even if they do
fd2ps should be adequate. Of course, xyplot and
charts are kind of special, and adding a postscript
output option (say, fl_xyplot_dump(FL_OBJECT *, const char *ps_filename))
might not be too bad an idea.
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/