diff options
| author | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-13 19:28:54 +0000 |
|---|---|---|
| committer | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-13 19:28:54 +0000 |
| commit | d7b88a3bcc7e76f38ee5799be7722fd5a10781ef (patch) | |
| tree | d8984d45424c9b2cdb199c1918f38bfea4a8211d /documentation/forms.html | |
| parent | 30fa233681467b82b165e7d42cd0bea778b93768 (diff) | |
Updated all links so they work between files.
Revision 1.
git-svn-id: file:///fltk/svn/fltk/trunk@219 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/forms.html')
| -rw-r--r-- | documentation/forms.html | 467 |
1 files changed, 198 insertions, 269 deletions
diff --git a/documentation/forms.html b/documentation/forms.html index c1c69cf0e..6fd5282d7 100644 --- a/documentation/forms.html +++ b/documentation/forms.html @@ -1,271 +1,200 @@ -<HTML> -<BODY> - -<H1 ALIGN=RIGHT><A NAME="forms">E - Forms Compatibility</A></H1> - -This appendix describes the Forms compatibility included with FLTK. - +<HTML><BODY> +<H1 ALIGN=RIGHT><A NAME=forms>E - Forms Compatibility</A></H1> + This appendix describes the Forms compatibility included with FLTK. <H2>Importing Forms Layout Files</H2> - -<a href="#FLUID">FLUID</a> 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. - -<p>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 compatibility header, -<tt><FL/forms.H></tt>. - +<A href=fluid.html#FLUID>FLUID</A> 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. +<P>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 compatibility header, <TT> +<FL/forms.H></TT>. </P> <H2>Using the Compatibility Header File</H2> - -You should be able to compile existing Forms or XForms source code -by changing the include directory switch to your compiler so that the -<tt>forms.h</tt> file supplied with FLTK is included. Take a look at -<tt>forms.h</tt> to see how it works, but the basic trick is lots of -inline functions. Most of the XForms demo programs work without -changes. - -<p>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. - -<p>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 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. - -<p>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 expected and -even Digital Domain's inhouse code still uses <tt>forms.H</tt> a lot. - -<h2>Problems you will encounter</h2> - -<p>Many parts of XForms use X-specific structures like <tt>XEvent</tt> -in their interface. I did not emulate these! Unfortunately these -features (such as the "canvas" widget) are needed by most large -programs. You will need to rewrite these to use FLTK subclasses. - -<p><a href="#Fl_Free"><tt>Fl_Free</tt></a> widgets emulate the -<i>old</i> Forms "free" widget. It may be useful for porting programs -that change the <tt>handle()</tt> function on widgets, but you will -still need to rewrite things. - -<p><a href="#Fl_Timer"><tt>Fl_Timer</tt></a> widgets are provided to -emulate the XForms timer. These work, but are quite inefficient and -inaccurate compared to using <a -href="#add_timeout"><tt>Fl::add_timeout()</tt></a>. - -<p><i>All instance variables are hidden.</i> -If you directly refer to the x, y, w, h, label, or other fields of -your Forms widgets you will have to add empty parenthesis after each -reference. The easiest way to do this is to globally replace "->x" -with "->x()", etc. Replace "boxtype" with "box()". - -<p><tt>const char *</tt> arguments to most FLTK methods are simply -stored, while Forms would <tt>strdup()</tt> the passed string. This is -most noticable with the label of widgets. Your program must always -pass static data such as a string constant or malloc'd buffer to -<tt>label()</tt>. If you are using labels to display program output -you may want to try the <a href="#Fl_Output"><tt>Fl_Output</tt></a> widget. - -<p>The default fonts and sizes are matched to the older GL version of -Forms, so all labels will draw somewhat larger than an XForms program -does. - -<p>fdesign outputs a setting of a "fdui" instance variable to the main -window. I did not emulate this because I wanted all instance variables -to be hidden. You can store the same information in the -<tt>user_data()</tt> field of a window. To do this, search through -the fdesign output for all occurances of "->fdui" and edit to use -"->user_data()" instead. This will require casts and is not trivial. - -<p>The prototype for the functions passed to <tt>fl_add_timeout()</tt> -and <tt>fl_set_idle_callback()</tt> callback are different. - -<p><b>All the following XForms calls are missing:</b><p> - -<ul> - <li><tt>FL_REVISION</tt>, <tt>fl_library_version()</tt> - <li><tt>FL_RETURN_DBLCLICK</tt> (use <tt>Fl::event_clicks()</tt>) - <li><tt>fl_add_signal_callback()</tt> - <li><tt>fl_set_form_atactivate()</tt> & <tt>fl_set_form_atdeactivate()</tt> - <li><tt>fl_set_form_property()</tt> - <li><tt>fl_set_app_mainform()</tt>, <tt>fl_get_app_mainform()</tt> - <li><tt>fl_set_form_minsize()</tt>, <tt>fl_set_form_maxsize()</tt> - <li><tt>fl_set_form_event_cmask()</tt>, <tt>fl_get_form_event_cmask()</tt> - <li><tt>fl_set_form_dblbuffer()</tt>, <tt>fl_set_object_dblbuffer()</tt> (use an - <tt>Fl_Double_Window</tt> instead) - <li><tt>fl_adjust_form_size()</tt> - <li><tt>fl_register_raw_callback()</tt> - <li><tt>fl_set_object_bw()</tt>, <tt>fl_set_border_width()</tt> - <li><tt>fl_set_object_resize()</tt>, <tt>fl_set_object_gravity()</tt> - <li><tt>fl_set_object_shortcutkey()</tt> - <li><tt>fl_set_object_automatic()</tt> - <li><tt>fl_get_object_bbox()</tt> (maybe FLTK should do this) - <li><tt>fl_set_object_prehandler()</tt>, <tt>fl_set_object_posthandler()</tt> - <li><tt>fl_enumerate_fonts()</tt> - <li>Most drawing functions - <li><tt>fl_set_coordunit()</tt> (FLTK uses pixels all the time) - <li><tt>fl_ringbell()</tt> - <li><tt>fl_gettime()</tt> - <li><tt>fl_win*()</tt> (all these functions) - <li><tt>fl_initialize(argc,argv,x,y,z)</tt> ignores last 3 arguments - <li><tt>fl_read_bitmapfile()</tt>, <tt>fl_read_pixmapfile()</tt> - <li><tt>fl_addto_browser_chars()</tt> - <li><tt>FL_MENU_BUTTON</tt> just draws normally - <li><tt>fl_set_bitmapbutton_file()</tt>, <tt>fl_set_pixmapbutton_file()</tt> - <li><tt>FL_CANVAS</tt> objects - <li><tt>FL_DIGITAL_CLOCK</tt> (comes out analog) - <li><tt>fl_create_bitmap_cursor()</tt>, <tt>fl_set_cursor_color()</tt> - <li><tt>fl_set_dial_angles()</tt> - <li><tt>fl_show_oneliner()</tt> - <li><tt>fl_set_choice_shortcut(a,b,c) - <li>command log - <li>Only some of file selector is emulated - <li><tt>FL_DATE_INPUT</tt> - <li><tt>fl_pup*()</tt> (all these functions) - <li>textbox object (should be easy but I had no sample programs) - <li>xyplot object -</ul> - -<h2>Additional Notes</h2> - -These notes were written for porting programs written with the older -IRISGL version of Forms. Most of these problems are the same ones -encountered when going from old Forms to XForms: - -<h3>Does Not Run In Background</h3> - -The IRISGL library always forked when you created the first window, unless -"foreground()" was called. FLTK acts like "foreground()" is called all -the time. If you really want the fork behavior do "if (fork()) -exit(0)" right at the start of your program. - -<h3>You Cannot Use IRISGL windows or fl_queue</h3> - -If a Forms (not XForms) program if you wanted your own window for -displaying things you would create a IRISGL window and draw in it, -periodically calling Forms to check if the user hit buttons on the -panels. If the user did things to the IRISGL window, you would find -this out by having the value FL_EVENT returned from the call to Forms. - -<p>None of this works with FLTK. Nor will it compile, the necessary -calls are not in the interface. - -<p>You have to make a subclass of <a -href="#Fl_Gl_Window"><tt>Fl_Gl_Window</tt></a> and write a <tt>draw()</tt> -method and <tt>handle()</tt> method. This may require anywhere from a trivial -to a major rewrite. - -<p>If you draw into the overlay planes you will have to also write a -<tt>draw_overlay()</tt> method and call <tt>redraw_overlay()</tt> on the -OpenGL window. - -<p>One easy way to hack your program so it works is to make the -<tt>draw()</tt> and <tt>handle()</tt> methods on your window set some -static variables, storing what event happened. Then in the main loop -of your program, call <tt>Fl::wait()</tt> and then check these -variables, acting on them as though they are events read from -<tt>fl_queue</tt>. - -<h3>You Must Use OpenGL to Draw Everything</h3> - -<p>The file <tt><FL/gl.h></tt> defines replacements for a lot of -IRISGL calls, translating them to OpenGL. There are much better -translators available that you might want to investigate. - -<h3>You Cannot Make Forms Subclasses</h3> - -Programs that call <tt>fl_make_object</tt> or directly setting the -handle routine will not compile. You have to rewrite them to use a -subclass of <tt>Fl_Widget</tt>. It is important to note that the -<tt>handle()</tt> method is not exactly the same as the -<tt>handle()</tt> function of Forms. Where a Forms <tt>handle()</tt> -returned non-zero, your <tt>handle()</tt> must call -<tt>do_callback()</tt>. And your <tt>handle()</tt> must return non-zero -if it "understood" the event. - -<p>An attempt has been made to emulate the "free" widget. This -appears to work quite well. It may be quicker to modify your subclass -into a "free" widget, since the "handle" functions match. - -<p>If your subclass draws into the overlay you are in trouble and will -have to rewrite things a lot. - -<h3>You Cannot Use <device.h></h3> - -If you have written your own "free" widgets you will probably get a -lot of errors about "getvaluator". You should substitute: - -<table border=1> -<tr> - <th align=center>Forms</th> - <th align=center>FLTK</th> -</tr> -<tr> - <td>MOUSE_X</td> - <td>Fl::event_x_root()</td> -</tr> -<tr> - <td>MOUSE_Y</td> - <td>Fl::event_y_root()</td> -</tr> -<tr> - <td>LEFTSHIFTKEY,RIGHTSHIFTKEY</td> - <td>Fl::event_shift()</td> -</tr> -<tr> - <td>CAPSLOCKKEY</td> - <td>Fl::event_capslock()</td> -</tr> -<tr> - <td>LEFTCTRLKEY,RIGHTCTRLKEY</td> - <td>Fl::event_ctrl()</td> -</tr> -<tr> - <td>LEFTALTKEY,RIGHTALTKEY</td> - <td>Fl::event_alt()</td> -</tr> -<tr> - <td>MOUSE1,RIGHTMOUSE</td> - <td>Fl::event_state()&FL_BUTTON3</td> -</tr> -<tr> - <td>MOUSE2,MIDDLEMOUSE</td> - <td>Fl::event_state()&FL_BUTTON2</td> -</tr> -<tr> - <td>MOUSE3,LEFTMOUSE</td> - <td>Fl::event_state()&FL_BUTTON1</td> -</tr> -</table> - -Anything else in <tt>getvaluator</tt> and you are on your own... - -<h3>Font Numbers Are Different</h3> - -The "style" numbers have been changed because I wanted to insert -bold-italic versions of the normal fonts. If you use Times, Courier, -or Bookman to display any text you will get a different font out of -FLTK. If you are really desperate to fix this use the following code: - -<ul><pre> -fl_font_name(3,"*courier-medium-r-no*"); -fl_font_name(4,"*courier-bold-r-no*"); -fl_font_name(5,"*courier-medium-o-no*"); -fl_font_name(6,"*times-medium-r-no*"); -fl_font_name(7,"*times-bold-r-no*"); -fl_font_name(8,"*times-medium-i-no*"); -fl_font_name(9,"*bookman-light-r-no*"); -fl_font_name(10,"*bookman-demi-r-no*"); -fl_font_name(11,"*bookman-light-i-no*"); -</pre></ul> - -</BODY> -</HTML> + You should be able to compile existing Forms or XForms source code by +changing the include directory switch to your compiler so that the <TT> +forms.h</TT> file supplied with FLTK is included. Take a look at <TT> +forms.h</TT> to see how it works, but the basic trick is lots of inline +functions. Most of the XForms demo programs work without changes. +<P>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. </P> +<P>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 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. </P> +<P>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 expected and +even Digital Domain's inhouse code still uses <TT>forms.H</TT> a lot. </P> +<H2>Problems you will encounter</H2> +<P>Many parts of XForms use X-specific structures like <TT>XEvent</TT> + in their interface. I did not emulate these! Unfortunately these +features (such as the "canvas" widget) are needed by most large +programs. You will need to rewrite these to use FLTK subclasses. </P> +<P><A href=Fl_Free.html#Fl_Free><TT>Fl_Free</TT></A> widgets emulate +the <I>old</I> Forms "free" widget. It may be useful for porting +programs that change the <TT>handle()</TT> function on widgets, but you +will still need to rewrite things. </P> +<P><A href=Fl_Timer.html#Fl_Timer><TT>Fl_Timer</TT></A> widgets are +provided to emulate the XForms timer. These work, but are quite +inefficient and inaccurate compared to using <A href=functions.html#add_timeout> +<TT>Fl::add_timeout()</TT></A>. </P> +<P><I>All instance variables are hidden.</I> If you directly refer to +the x, y, w, h, label, or other fields of your Forms widgets you will +have to add empty parenthesis after each reference. The easiest way to +do this is to globally replace "->x" with "->x()", etc. Replace +"boxtype" with "box()". </P> +<P><TT>const char *</TT> arguments to most FLTK methods are simply +stored, while Forms would <TT>strdup()</TT> the passed string. This is +most noticable with the label of widgets. Your program must always +pass static data such as a string constant or malloc'd buffer to <TT> +label()</TT>. If you are using labels to display program output you +may want to try the <A href=Fl_Output.html#Fl_Output><TT>Fl_Output</TT></A> + widget. </P> +<P>The default fonts and sizes are matched to the older GL version of +Forms, so all labels will draw somewhat larger than an XForms program +does. </P> +<P>fdesign outputs a setting of a "fdui" instance variable to the main +window. I did not emulate this because I wanted all instance variables +to be hidden. You can store the same information in the <TT>user_data()</TT> + field of a window. To do this, search through the fdesign output for +all occurances of "->fdui" and edit to use "->user_data()" instead. + This will require casts and is not trivial. </P> +<P>The prototype for the functions passed to <TT>fl_add_timeout()</TT> + and <TT>fl_set_idle_callback()</TT> callback are different. </P> +<P><B>All the following XForms calls are missing:</B></P> +<P> +<UL> +<LI><TT>FL_REVISION</TT>, <TT>fl_library_version()</TT></LI> +<LI><TT>FL_RETURN_DBLCLICK</TT> (use <TT>Fl::event_clicks()</TT>) </LI> +<LI><TT>fl_add_signal_callback()</TT></LI> +<LI><TT>fl_set_form_atactivate()</TT> <TT>fl_set_form_atdeactivate()</TT> +</LI> +<LI><TT>fl_set_form_property()</TT></LI> +<LI><TT>fl_set_app_mainform()</TT>, <TT>fl_get_app_mainform()</TT></LI> +<LI><TT>fl_set_form_minsize()</TT>, <TT>fl_set_form_maxsize()</TT></LI> +<LI><TT>fl_set_form_event_cmask()</TT>, <TT>fl_get_form_event_cmask()</TT> +</LI> +<LI><TT>fl_set_form_dblbuffer()</TT>, <TT>fl_set_object_dblbuffer()</TT> + (use an <TT>Fl_Double_Window</TT> instead) </LI> +<LI><TT>fl_adjust_form_size()</TT></LI> +<LI><TT>fl_register_raw_callback()</TT></LI> +<LI><TT>fl_set_object_bw()</TT>, <TT>fl_set_border_width()</TT></LI> +<LI><TT>fl_set_object_resize()</TT>, <TT>fl_set_object_gravity()</TT></LI> +<LI><TT>fl_set_object_shortcutkey()</TT></LI> +<LI><TT>fl_set_object_automatic()</TT></LI> +<LI><TT>fl_get_object_bbox()</TT> (maybe FLTK should do this) </LI> +<LI><TT>fl_set_object_prehandler()</TT>, <TT>fl_set_object_posthandler()</TT> +</LI> +<LI><TT>fl_enumerate_fonts()</TT></LI> +<LI>Most drawing functions </LI> +<LI><TT>fl_set_coordunit()</TT> (FLTK uses pixels all the time) </LI> +<LI><TT>fl_ringbell()</TT></LI> +<LI><TT>fl_gettime()</TT></LI> +<LI><TT>fl_win*()</TT> (all these functions) </LI> +<LI><TT>fl_initialize(argc,argv,x,y,z)</TT> ignores last 3 arguments </LI> +<LI><TT>fl_read_bitmapfile()</TT>, <TT>fl_read_pixmapfile()</TT></LI> +<LI><TT>fl_addto_browser_chars()</TT></LI> +<LI><TT>FL_MENU_BUTTON</TT> just draws normally </LI> +<LI><TT>fl_set_bitmapbutton_file()</TT>, <TT>fl_set_pixmapbutton_file()</TT> +</LI> +<LI><TT>FL_CANVAS</TT> objects </LI> +<LI><TT>FL_DIGITAL_CLOCK</TT> (comes out analog) </LI> +<LI><TT>fl_create_bitmap_cursor()</TT>, <TT>fl_set_cursor_color()</TT></LI> +<LI><TT>fl_set_dial_angles()</TT></LI> +<LI><TT>fl_show_oneliner()</TT></LI> +<LI><TT>fl_set_choice_shortcut(a,b,c) </TT></LI> +<LI>command log </LI> +<LI>Only some of file selector is emulated </LI> +<LI><TT>FL_DATE_INPUT</TT></LI> +<LI><TT>fl_pup*()</TT> (all these functions) </LI> +<LI>textbox object (should be easy but I had no sample programs) </LI> +<LI>xyplot object </LI> +</UL> +<H2>Additional Notes</H2> + These notes were written for porting programs written with the older +IRISGL version of Forms. Most of these problems are the same ones +encountered when going from old Forms to XForms: +<H3>Does Not Run In Background</H3> + The IRISGL library always forked when you created the first window, +unless "foreground()" was called. FLTK acts like "foreground()" is +called all the time. If you really want the fork behavior do "if +(fork()) exit(0)" right at the start of your program. +<H3>You Cannot Use IRISGL windows or fl_queue</H3> + If a Forms (not XForms) program if you wanted your own window for +displaying things you would create a IRISGL window and draw in it, +periodically calling Forms to check if the user hit buttons on the +panels. If the user did things to the IRISGL window, you would find +this out by having the value FL_EVENT returned from the call to Forms. +<P>None of this works with FLTK. Nor will it compile, the necessary +calls are not in the interface. </P> +<P>You have to make a subclass of <A href=Fl_Gl_Window.html#Fl_Gl_Window> +<TT>Fl_Gl_Window</TT></A> and write a <TT>draw()</TT> method and <TT> +handle()</TT> method. This may require anywhere from a trivial to a +major rewrite. </P> +<P>If you draw into the overlay planes you will have to also write a <TT> +draw_overlay()</TT> method and call <TT>redraw_overlay()</TT> on the +OpenGL window. </P> +<P>One easy way to hack your program so it works is to make the <TT> +draw()</TT> and <TT>handle()</TT> methods on your window set some +static variables, storing what event happened. Then in the main loop +of your program, call <TT>Fl::wait()</TT> and then check these +variables, acting on them as though they are events read from <TT> +fl_queue</TT>. </P> +<H3>You Must Use OpenGL to Draw Everything</H3> +<P>The file <TT><FL/gl.h></TT> defines replacements for a lot of IRISGL +calls, translating them to OpenGL. There are much better translators +available that you might want to investigate. </P> +<H3>You Cannot Make Forms Subclasses</H3> + Programs that call <TT>fl_make_object</TT> or directly setting the +handle routine will not compile. You have to rewrite them to use a +subclass of <TT>Fl_Widget</TT>. It is important to note that the <TT> +handle()</TT> method is not exactly the same as the <TT>handle()</TT> + function of Forms. Where a Forms <TT>handle()</TT> returned non-zero, +your <TT>handle()</TT> must call <TT>do_callback()</TT>. And your <TT> +handle()</TT> must return non-zero if it "understood" the event. +<P>An attempt has been made to emulate the "free" widget. This appears +to work quite well. It may be quicker to modify your subclass into a +"free" widget, since the "handle" functions match. </P> +<P>If your subclass draws into the overlay you are in trouble and will +have to rewrite things a lot. </P> +<H3>You Cannot Use <device.h></H3> + If you have written your own "free" widgets you will probably get a +lot of errors about "getvaluator". You should substitute: +<TABLE border=1> +<TR><TH align=center>Forms</TH><TH align=center>FLTK</TH></TR> +<TR><TD>MOUSE_X</TD><TD>Fl::event_x_root()</TD></TR> +<TR><TD>MOUSE_Y</TD><TD>Fl::event_y_root()</TD></TR> +<TR><TD>LEFTSHIFTKEY,RIGHTSHIFTKEY</TD><TD>Fl::event_shift()</TD></TR> +<TR><TD>CAPSLOCKKEY</TD><TD>Fl::event_capslock()</TD></TR> +<TR><TD>LEFTCTRLKEY,RIGHTCTRLKEY</TD><TD>Fl::event_ctrl()</TD></TR> +<TR><TD>LEFTALTKEY,RIGHTALTKEY</TD><TD>Fl::event_alt()</TD></TR> +<TR><TD>MOUSE1,RIGHTMOUSE</TD><TD>Fl::event_state()</TD></TR> +<TR><TD>MOUSE2,MIDDLEMOUSE</TD><TD>Fl::event_state()</TD></TR> +<TR><TD>MOUSE3,LEFTMOUSE</TD><TD>Fl::event_state()</TD></TR> +</TABLE> + Anything else in <TT>getvaluator</TT> and you are on your own... +<H3>Font Numbers Are Different</H3> + The "style" numbers have been changed because I wanted to insert +bold-italic versions of the normal fonts. If you use Times, Courier, +or Bookman to display any text you will get a different font out of +FLTK. If you are really desperate to fix this use the following code: +<UL> +<PRE> +fl_font_name(3,"*courier-medium-r-no*"); +fl_font_name(4,"*courier-bold-r-no*"); +fl_font_name(5,"*courier-medium-o-no*"); +fl_font_name(6,"*times-medium-r-no*"); +fl_font_name(7,"*times-bold-r-no*"); +fl_font_name(8,"*times-medium-i-no*"); +fl_font_name(9,"*bookman-light-r-no*"); +fl_font_name(10,"*bookman-demi-r-no*"); +fl_font_name(11,"*bookman-light-i-no*"); +</PRE> +</UL> +</BODY></HTML>
\ No newline at end of file |