From 367f908d8ed5a3464b9676223a26ddf4e11bdb5b Mon Sep 17 00:00:00 2001 From: Michael R Sweet Date: Thu, 7 Jan 1999 16:36:11 +0000 Subject: "Final" changes for first draft of 1.0 documentation. git-svn-id: file:///fltk/svn/fltk/trunk@187 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- documentation/forms.html | 327 ++++++++++++++++++++++++++--------------------- 1 file changed, 184 insertions(+), 143 deletions(-) (limited to 'documentation/forms.html') diff --git a/documentation/forms.html b/documentation/forms.html index 1d6614581..c1c69cf0e 100644 --- a/documentation/forms.html +++ b/documentation/forms.html @@ -3,182 +3,193 @@

E - Forms Compatibility

-Fluid (the Fast Light User Interface Designer) -can read the .fd files put out by all versions of Forms and XForms -fdesign. However, it will mangle them a bit, but it prints a warning -message about anything it does not understand. Fluid cannot write -fdesign files, so you should save to a new name so you don't write -over the old one. +This appendix describes the Forms compatibility included with FLTK. + +

Importing Forms Layout Files

+ +FLUID can read the .fd files put out by all +versions of Forms and XForms fdesign. However, it will mangle them a +bit, but it prints a warning message about anything it does not +understand. FLUID cannot write fdesign files, so you should save to a +new name so you don't write over the old one.

You will need to edit your main code considerably to get it to link -with the output from fluid. If you are not interested in this you may -have more immediate luck with the forms compatability header, +with the output from FLUID. If you are not interested in this you may +have more immediate luck with the forms compatibility header, <FL/forms.H>. -

You should be able to compile existing Forms or XForms source code -by changing the -I switch to your compiler so that the forms.h file -supplied with FLTK is included. Take a look at forms.h to see how it -works, but the basic trick is lots of inline functions. -Most of the XForms demo programs work without changes. +

Using the Compatibility Header File

+ +You should be able to compile existing Forms or XForms source code +by changing the include directory switch to your compiler so that the +forms.h file supplied with FLTK is included. Take a look at +forms.h to see how it works, but the basic trick is lots of +inline functions. Most of the XForms demo programs work without +changes. + +

You will also have to compile your Forms or XForms program using a +C++ compiler. The FLTK library does not provide C bindings or header +files.

Although FLTK was designed to be compatable with the GL Forms library (version 0.3 or so), XForms has bloated severely and it's interface is -X specific. Therefore, XForms compatability is no longer a goal of -FLTK. Compatability was limited to things that were free, or that -would add code that would not be linked in if the feature is unused. -I did not add anything that would make the FLTK widgets bigger, or that -used X types as arguments. +X-specific. Therefore, XForms compatibility is no longer a goal of +FLTK. Compatibility was limited to things that were free, or that +would add code that would not be linked in if the feature is unused, +or that was not X-specific.

To use any new features of FLTK, you should rewrite your code to not -use the inline functions and instead use "pure" FLTK. This -will make it a lot cleaner and make it easier to figure out how to -call the FLTK functions. Unfortunately this conversion is harder than I -expeceted and even our inhouse code still uses forms.H a lot. +use the inline functions and instead use "pure" FLTK. This will make +it a lot cleaner and make it easier to figure out how to call the FLTK +functions. Unfortunately this conversion is harder than expected and +even Digital Domain's inhouse code still uses forms.H a lot.

Problems you will encounter

-