notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Moved FTLK docs.

Browse source
This commit is contained in:
William Kendrick 2007-08-11 17:40:34 +00:00
parent 5ee55b039c
commit 332bf57b32
5 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

467
win32/libdocs/fltk/ANNOUNCEMENT Normal file
View file

@ -0,0 +1,467 @@
----TEXT----
The second release candidate for FLTK 1.1.4 is now available for
download and testing. You now have until August 12th, 2003 to
report any problems with this release candidate using the
software trouble report form at the following URL:
http://www.fltk.org/str.php
If no priority 4 or 5 STRs are received and confirmed before
this date, FLTK 1.1.4 will be released.
Note: Since problems reported on the FLTK newsgroups or mailing
lists are *not* automatically entered as STRs, it is important
that you report any problems using the STR form.
---- Draft FLTK 1.1.4 Release Announcement ----
The FLTK Team is proud to announce the release of FLTK 1.1.4,
a cross-platform C++ GUI toolkit for UNIX(r)/Linux(r) (X11),
Microsoft(r) Windows(r), and MacOS(r) X. FLTK provides
modern GUI functionality without the bloat and supports 3D
graphics via OpenGL(r) and its built-in GLUT emulation.
The FLTK 1.1.4 release is primarily a bug-fix release including
fixes to FLUID and the Fl_File_Chooser, Fl_Help_View,
Fl_Text_Display, and Fl_Text_Editor widgets. The new release
also adds a find method to Fl_Help_View.
FLTK is provided under the GNU Library Public License with
exceptions that allow for static linking.
Changes since FLTK 1.1.3 include:
- The fl_read_image() function was not implemented on
OSX (STR #161)
- VC++ 7.1 didn't like how the copy operators were
disabled for the Fl_Widget class; now include inline
code which will never be used but makes VC++ happy
(STR #156)
- Fixed an IRIX compile problem caused by a missing
#include (STR #157)
- FLUID didn't write color/selection_color() calls using
the symbolic names when possible, nor did it cast
integer colors to Fl_Color (STR #146)
- Fl_File_Chooser was very close for multiple file
selection in large directories (STR #140)
- Fl_Text_Display/Editor did not disable the current
selection when focus was shifted to another widget
(STR #131)
- Fl_Choice didn't use the normal focus box when the
plastic scheme was in use (STR #129)
- Fl_Text_Editor didn't use selection_color()
consistently (STR #130)
- The fltk_forms, fltk_gl, and fltk_images DSO's and
HP-UX shared libraries are now linked against the fltk
shared library to provide complete dependency
resolution (STR #118)
- The configure.in file did not work with autoconf 2.57.
- FLUID didn't redraw widgets when changing the X, Y, W,
or H values in the widget panel (STR #120)
- Fl_Window::show(argc, argv) wasn't calling
Fl::get_system_colors() as documented (STR #119)
- DSO (shared library) building wasn't quite right for
some platforms (STR #118)
- OSX: some changes to make ProjectBuilder compiles
possible.
- OSX: FLTK would not know where a window was positioned
by the OS. As a result, popup menus could open at
wrong positions.
- Fl_Window::show(argc,argv) incorrectly opened the
display prior to parsing the arguments; this prevented
the "-display foo" option from working (STR #111)
- Images were not clipped properly on MacOS X (STR #114)
- Fl::reload_scheme() and Fl::scheme("foo") incorrectly
called Fl::get_system_colors(). This prevented an
application from setting its own color preferences
(STR #115)
- The 'Enter' key event on OS X would not set Fl::e_text
(STR #???)
- Changed behaviour of fluid to always paste into
a selected group (STR #88)
- Menuitem now changes font, even if fontsize
is not set (STR #110)
- Swapped shortcut labels in OS X (STR #86)
- Non-square Fl_Dial would calculate angle from user
input wrong (STR #101)
- Updated documentatiopn of fl_draw (STR #94)
and Fl_Menu_::add() (STR #99)
- Fluid collapse triangle events were not offset by
horizontal scroll (STR #106)
- QuitAppleEvent now correctly returns from Fl::run()
instead of just exiting (STR #87)
- Hiding the first created OpenGL context was not
possible. FLTK now manages a list of contexts (STR #77)
- FLUID didn't keep the double/single buffer type for
windows.
- FLTK didn't work with Xft2.
- OSX window resizing didn't work (STR #64)
- Fixed MacOS X shared library generation (STR #51)
- Several widgets defined their own size() method but
didn't provide an inline method that mapped to the
Fl_Widget::size() method (STR #62)
- Fl_Scroll didn't provide its own clear() method, so
calling clear() on a Fl_Scroll widget would also
destroy the scrollbars (STR #75)
- Fl::event_text() was sometimes initialized to NULL
instead of an empty string (STR #70)
- fl_draw() didn't properly handle a trailing escaped
"@" character (STR #84)
- Added documentation for all forms of
Fl_Widget::damage() (STR #61)
- Fl_Double_Window now has a type() value of
FL_DOUBLE_WINDOW, to allow double-buffered windows to
process redraws properly on WIN32 (STR #46)
- Added FL_DAMAGE_USER1 and FL_DAMAGE_USER2 damage bits
for use by widget developers (STR #57)
- Fl_Help_View didn't support numeric character entities
(STR #66)
- Menu shortcuts didn't use the Mac key names under
MacOS X (STR #71)
- CodeWarrior Mac OS X updated to work with current
CW8.3 (STR #34)
- Apple-C/X/V/Z didn't work in the Fl_Input widget due
to a bad mapping to control keys (STR #79)
- Added the OSX-specific fl_open_callback() function to
handle Open Documents messages from the Finder (STR
#80)
- The configure script contained erroneous whitespace in
various tests which caused errors on some platforms
(STR #60)
- The fltk-config script still supported the deprecated
--prefix and --exec-prefix options; dropped them since
they serve no useful purpose and would never have
worked for the intended purpose anyways... (STR #56)
- fl_filename_list returned 0 on Win32 if no directory
existed (STR #54)
- Pressing 'home' after the last letter in a Text_Editor
would move the cursor to pos 0 (STR #39)
- Fl::get_key(x) would mix up Ctrl and Meta on OS X (STR
#55)
- The configure script used the wrong dynamic library
linking command for OSX (STR #51)
- The Fl_Text_Editor widget did not set changed() nor
did it call the widget's callback function for
FL_WHEN_CHANGED when processing characters that
Fl::compose() handles (STR #52)
- The file chooser did not reset the click count when
changing directories; if you clicked on a file in the
same position after changing directories with a
double- click, the chooser treated it as a triple
click (STR #27)
- Symbols with outlines did not get drawn inactive.
- The Fl_Help_View widget now provides a find() method
to search for text within the page.
- The Fl_Help_Dialog widget now provides a search box
for entering text to search for.
- The default font encoding on OSX did not match the
default on WIN32 or X11.
- Menu items were not drawn using the font specified in
the Fl_Menu_Item structure (STR #30)
- Long menus that were aligned such that the top of an
item was exactly at the top of the screen would not
scroll (STR #33)
- The OS issues appendix incorrectly stated that MacOS
8.6 and 9 were supported; they are not (STR #28)
- Fixed handling of nested double-buffered windows (STR
#1)
- Showing a subwindow inside a hidden window would crash
the application (STR #23)
- OSX users couldn't enter some special chars when using
some foreign key layouts (STR #32)
- Hiding subwindows on OSX would hide the parent window
(STR #22)
- Added thin plastic box types.
- Fl_Pack ignored the box() setting and cleared any
unused areas to the widget color; it now only does so
if the box() is set to something other than FL_NO_BOX.
- Updated the Fl_Tabs widget to offset the first tab by
the box dx value to avoid visual errors.
- Updated the plastic up box to draw only a single
border frame instead of the old double one for
improved appearance.
- Updated the default background color on OSX to provide
better contrast.
- Fl_Text_Display and friends now look for the next
non-punctuation/space character for word boundaries
(STR #26)
- gl_font() didn't work properly for X11 when Xft was
used (STR #12)
- Fl_File_Browser incorrectly included "." on WIN32 (STR
#9)
- Include shellapi.h instead of ShellAPI.h in the WIN32
drag-n-drop code in order to work with the MingW cross
compiler (STR #6)
- The cursor was not properly restored when doing
drag-n-drop on X11 (STR #4)
- Fl::remove_fd() didn't recalculate the highest file
descriptor properly (STR #20)
- Fl_Preferences::deleteGroup() didn't work properly
(STR #13)
- Fixed the fl_show_file_selector() function - it was
copying using the wrong string size (STR #14)
- fl_font() and fl_size() were not implemented on MacOS
X.
- Sorted the icon menu bar in fluid.
- Fixed minor memory access complaints from Valgrind
- Compiling src/flstring.h on OS X with BSD header would
fail.
- Fl_Text_Editor didn't scroll the buffer when the user
pressed Ctrl+End or Ctrl+Home.
- Fl_Text_Editor didn't show its cursor when the mouse
was moved inside the window.
- FLUID now uses an Fl_Text_Display widget for command
output, which allows you to copy and paste text from
command output into other windows.
- Fl_Gl_Window could cause a bus error on MacOS X if the
parent window was not yet shown.
- FLUID could crash after displaying a syntax error
dialog for the callback code.
- FLUID would reset the callback code if you opened the
widget panel for multiple widgets.
- Added a NULL check to Fl_Text_Display (SF Bug #706921).
- The fltk-config script placed the LDFLAGS at the wrong
place in the linker options.
- Fl_Text_Display didn't draw the outer box in the right
dimensions, so it was invisible.
- Fl_Help_Dialog used the same color for links as for
the background, causing links to be invisible on pages
without a background color set.
----HTML----
<P>The second release candidate for FLTK 1.1.4 is now available
for download and testing. You now have until August 12th, 2003 to
report any problems with this release candidate using the
software trouble report form at the following URL:</P>
<PRE>
<A HREF="http://www.fltk.org/str.php">http://www.fltk.org/str.php</A>
</PRE>
<P>If no priority 4 or 5 STRs are received and confirmed before
this date, 1.1.4 will be released.
<P>Note: Since problems reported on the FLTK newsgroups or
mailing lists are <I>not</I> automatically entered as STRs, it
is important that you report any problems using the STR form.
<P ALIGN="CENTER">---- Draft FLTK 1.1.4 Release Announcement ----</P>
<P>The FLTK Team is proud to announce the release of FLTK 1.1.4,
a cross-platform C++ GUI toolkit for UNIX&reg;/Linux&reg; (X11),
Microsoft&reg; Windows&reg;, and MacOS&reg; X. FLTK provides
modern GUI functionality without the bloat and supports 3D
graphics via OpenGL&reg; and its built-in GLUT emulation.
<P>The FLTK 1.1.4 release is primarily a bug-fix release
including fixes to FLUID and the Fl_File_Chooser, Fl_Help_View,
Fl_Text_Display, and Fl_Text_Editor widgets. The new release
also adds a find method to Fl_Help_View.
<P>FLTK is provided under the GNU Library Public License with
exceptions that allow for static linking.
<P>Changes since FLTK 1.1.3 include:
<UL>
<LI>The fl_read_image() function was not implemented on
OSX (<A HREF="http://www.fltk.org/str.php?L161">STR #161</A>)
<LI>VC++ 7.1 didn't like how the copy operators were
disabled for the Fl_Widget class; now include inline
code which will never be used but makes VC++ happy
(<A HREF="http://www.fltk.org/str.php?L156">STR #156</A>)
<LI>Fixed an IRIX compile problem caused by a missing
#include (<A HREF="http://www.fltk.org/str.php?L157">STR #157</A>)
<LI>FLUID didn't write color/selection_color() calls using
the symbolic names when possible, nor did it cast
integer colors to Fl_Color (<A HREF="http://www.fltk.org/str.php?L146">STR #146</A>)
<LI>Fl_File_Chooser was very close for multiple file
selection in large directories (<A HREF="http://www.fltk.org/str.php?L140">STR #140</A>)
<LI>Fl_Text_Display/Editor did not disable the current
selection when focus was shifted to another widget
(<A HREF="http://www.fltk.org/str.php?L131">STR #131</A>)
<LI>Fl_Choice didn't use the normal focus box when the
plastic scheme was in use (<A HREF="http://www.fltk.org/str.php?L129">STR #129</A>)
<LI>Fl_Text_Editor didn't use selection_color()
consistently (<A HREF="http://www.fltk.org/str.php?L130">STR #130</A>)
<LI>The fltk_forms, fltk_gl, and fltk_images DSO's and
HP-UX shared libraries are now linked against the fltk
shared library to provide complete dependency
resolution (<A HREF="http://www.fltk.org/str.php?L118">STR #118</A>)
<LI>The configure.in file did not work with autoconf 2.57.
<LI>FLUID didn't redraw widgets when changing the X, Y, W,
or H values in the widget panel (<A HREF="http://www.fltk.org/str.php?L120">STR #120</A>)
<LI>Fl_Window::show(argc, argv) wasn't calling
Fl::get_system_colors() as documented (<A HREF="http://www.fltk.org/str.php?L119">STR #119</A>)
<LI>DSO (shared library) building wasn't quite right for
some platforms (<A HREF="http://www.fltk.org/str.php?L118">STR #118</A>)
<LI>OSX: some changes to make ProjectBuilder compiles
possible.
<LI>OSX: FLTK would not know where a window was positioned
by the OS. As a result, popup menus could open at
wrong positions.
<LI>Fl_Window::show(argc,argv) incorrectly opened the
display prior to parsing the arguments; this prevented
the "-display foo" option from working (<A HREF="http://www.fltk.org/str.php?L111">STR #111</A>)
<LI>Images were not clipped properly on MacOS X (<A HREF="http://www.fltk.org/str.php?L114">STR #114</A>)
<LI>Fl::reload_scheme() and Fl::scheme("foo") incorrectly
called Fl::get_system_colors(). This prevented an
application from setting its own color preferences
(<A HREF="http://www.fltk.org/str.php?L115">STR #115</A>)
<LI>The 'Enter' key event on OS X would not set Fl::e_text
(STR #???)
<LI>Changed behaviour of fluid to always paste into
a selected group (<A HREF="http://www.fltk.org/str.php?L88">STR #88</A>)
<LI>Menuitem now changes font, even if fontsize
is not set (<A HREF="http://www.fltk.org/str.php?L110">STR #110</A>)
<LI>Swapped shortcut labels in OS X (<A HREF="http://www.fltk.org/str.php?L86">STR #86</A>)
<LI>Non-square Fl_Dial would calculate angle from user
input wrong (<A HREF="http://www.fltk.org/str.php?L101">STR #101</A>)
<LI>Updated documentatiopn of fl_draw (<A HREF="http://www.fltk.org/str.php?L94">STR #94</A>)
and Fl_Menu_::add() (<A HREF="http://www.fltk.org/str.php?L99">STR #99</A>)
<LI>Fluid collapse triangle events were not offset by
horizontal scroll (<A HREF="http://www.fltk.org/str.php?L106">STR #106</A>)
<LI>QuitAppleEvent now correctly returns from Fl::run()
instead of just exiting (<A HREF="http://www.fltk.org/str.php?L87">STR #87</A>)
<LI>Hiding the first created OpenGL context was not
possible. FLTK now manages a list of contexts (<A HREF="http://www.fltk.org/str.php?L77">STR #77</A>)
<LI>FLUID didn't keep the double/single buffer type for
windows.
<LI>FLTK didn't work with Xft2.
<LI>OSX window resizing didn't work (<A HREF="http://www.fltk.org/str.php?L64">STR #64</A>)
<LI>Fixed MacOS X shared library generation (<A HREF="http://www.fltk.org/str.php?L51">STR #51</A>)
<LI>Several widgets defined their own size() method but
didn't provide an inline method that mapped to the
Fl_Widget::size() method (<A HREF="http://www.fltk.org/str.php?L62">STR #62</A>)
<LI>Fl_Scroll didn't provide its own clear() method, so
calling clear() on a Fl_Scroll widget would also
destroy the scrollbars (<A HREF="http://www.fltk.org/str.php?L75">STR #75</A>)
<LI>Fl::event_text() was sometimes initialized to NULL
instead of an empty string (<A HREF="http://www.fltk.org/str.php?L70">STR #70</A>)
<LI>fl_draw() didn't properly handle a trailing escaped
"@" character (<A HREF="http://www.fltk.org/str.php?L84">STR #84</A>)
<LI>Added documentation for all forms of
Fl_Widget::damage() (<A HREF="http://www.fltk.org/str.php?L61">STR #61</A>)
<LI>Fl_Double_Window now has a type() value of
FL_DOUBLE_WINDOW, to allow double-buffered windows to
process redraws properly on WIN32 (<A HREF="http://www.fltk.org/str.php?L46">STR #46</A>)
<LI>Added FL_DAMAGE_USER1 and FL_DAMAGE_USER2 damage bits
for use by widget developers (<A HREF="http://www.fltk.org/str.php?L57">STR #57</A>)
<LI>Fl_Help_View didn't support numeric character entities
(<A HREF="http://www.fltk.org/str.php?L66">STR #66</A>)
<LI>Menu shortcuts didn't use the Mac key names under
MacOS X (<A HREF="http://www.fltk.org/str.php?L71">STR #71</A>)
<LI>CodeWarrior Mac OS X updated to work with current
CW8.3 (<A HREF="http://www.fltk.org/str.php?L34">STR #34</A>)
<LI>Apple-C/X/V/Z didn't work in the Fl_Input widget due
to a bad mapping to control keys (<A HREF="http://www.fltk.org/str.php?L79">STR #79</A>)
<LI>Added the OSX-specific fl_open_callback() function to
handle Open Documents messages from the Finder (STR
#80)
<LI>The configure script contained erroneous whitespace in
various tests which caused errors on some platforms
(<A HREF="http://www.fltk.org/str.php?L60">STR #60</A>)
<LI>The fltk-config script still supported the deprecated
--prefix and --exec-prefix options; dropped them since
they serve no useful purpose and would never have
worked for the intended purpose anyways... (<A HREF="http://www.fltk.org/str.php?L56">STR #56</A>)
<LI>fl_filename_list returned 0 on Win32 if no directory
existed (<A HREF="http://www.fltk.org/str.php?L54">STR #54</A>)
<LI>Pressing 'home' after the last letter in a Text_Editor
would move the cursor to pos 0 (<A HREF="http://www.fltk.org/str.php?L39">STR #39</A>)
<LI>Fl::get_key(x) would mix up Ctrl and Meta on OS X (STR
#55)
<LI>The configure script used the wrong dynamic library
linking command for OSX (<A HREF="http://www.fltk.org/str.php?L51">STR #51</A>)
<LI>The Fl_Text_Editor widget did not set changed() nor
did it call the widget's callback function for
FL_WHEN_CHANGED when processing characters that
Fl::compose() handles (<A HREF="http://www.fltk.org/str.php?L52">STR #52</A>)
<LI>The file chooser did not reset the click count when
changing directories; if you clicked on a file in the
same position after changing directories with a
double<LI>click, the chooser treated it as a triple
click (<A HREF="http://www.fltk.org/str.php?L27">STR #27</A>)
<LI>Symbols with outlines did not get drawn inactive.
<LI>The Fl_Help_View widget now provides a find() method
to search for text within the page.
<LI>The Fl_Help_Dialog widget now provides a search box
for entering text to search for.
<LI>The default font encoding on OSX did not match the
default on WIN32 or X11.
<LI>Menu items were not drawn using the font specified in
the Fl_Menu_Item structure (<A HREF="http://www.fltk.org/str.php?L30">STR #30</A>)
<LI>Long menus that were aligned such that the top of an
item was exactly at the top of the screen would not
scroll (<A HREF="http://www.fltk.org/str.php?L33">STR #33</A>)
<LI>The OS issues appendix incorrectly stated that MacOS
8.6 and 9 were supported; they are not (<A HREF="http://www.fltk.org/str.php?L28">STR #28</A>)
<LI>Fixed handling of nested double-buffered windows (STR
#1)
<LI>Showing a subwindow inside a hidden window would crash
the application (<A HREF="http://www.fltk.org/str.php?L23">STR #23</A>)
<LI>OSX users couldn't enter some special chars when using
some foreign key layouts (<A HREF="http://www.fltk.org/str.php?L32">STR #32</A>)
<LI>Hiding subwindows on OSX would hide the parent window
(<A HREF="http://www.fltk.org/str.php?L22">STR #22</A>)
<LI>Added thin plastic box types.
<LI>Fl_Pack ignored the box() setting and cleared any
unused areas to the widget color; it now only does so
if the box() is set to something other than FL_NO_BOX.
<LI>Updated the Fl_Tabs widget to offset the first tab by
the box dx value to avoid visual errors.
<LI>Updated the plastic up box to draw only a single
border frame instead of the old double one for
improved appearance.
<LI>Updated the default background color on OSX to provide
better contrast.
<LI>Fl_Text_Display and friends now look for the next
non-punctuation/space character for word boundaries
(<A HREF="http://www.fltk.org/str.php?L26">STR #26</A>)
<LI>gl_font() didn't work properly for X11 when Xft was
used (<A HREF="http://www.fltk.org/str.php?L12">STR #12</A>)
<LI>Fl_File_Browser incorrectly included "." on WIN32 (STR
#9)
<LI>Include shellapi.h instead of ShellAPI.h in the WIN32
drag-n-drop code in order to work with the MingW cross
compiler (<A HREF="http://www.fltk.org/str.php?L6">STR #6</A>)
<LI>The cursor was not properly restored when doing
drag-n-drop on X11 (<A HREF="http://www.fltk.org/str.php?L4">STR #4</A>)
<LI>Fl::remove_fd() didn't recalculate the highest file
descriptor properly (<A HREF="http://www.fltk.org/str.php?L20">STR #20</A>)
<LI>Fl_Preferences::deleteGroup() didn't work properly
(<A HREF="http://www.fltk.org/str.php?L13">STR #13</A>)
<LI>Fixed the fl_show_file_selector() function <LI>it was
copying using the wrong string size (<A HREF="http://www.fltk.org/str.php?L14">STR #14</A>)
<LI>fl_font() and fl_size() were not implemented on MacOS
X.
<LI>Sorted the icon menu bar in fluid.
<LI>Fixed minor memory access complaints from Valgrind
<LI>Compiling src/flstring.h on OS X with BSD header would
fail.
<LI>Fl_Text_Editor didn't scroll the buffer when the user
pressed Ctrl+End or Ctrl+Home.
<LI>Fl_Text_Editor didn't show its cursor when the mouse
was moved inside the window.
<LI>FLUID now uses an Fl_Text_Display widget for command
output, which allows you to copy and paste text from
command output into other windows.
<LI>Fl_Gl_Window could cause a bus error on MacOS X if the
parent window was not yet shown.
<LI>FLUID could crash after displaying a syntax error
dialog for the callback code.
<LI>FLUID would reset the callback code if you opened the
widget panel for multiple widgets.
<LI>Added a NULL check to Fl_Text_Display (SF Bug #706921).
<LI>The fltk-config script placed the LDFLAGS at the wrong
place in the linker options.
<LI>Fl_Text_Display didn't draw the outer box in the right
dimensions, so it was invisible.
<LI>Fl_Help_Dialog used the same color for links as for
the background, causing links to be invisible on pages
without a background color set.
</UL>

2328
win32/libdocs/fltk/CHANGES Normal file
View file

File diff suppressed because it is too large Load diff

528
win32/libdocs/fltk/COPYING Normal file
View file

@ -0,0 +1,528 @@
FLTK License
December 11, 2001
The FLTK library and included programs are provided under the terms
of the GNU Library General Public License (LGPL) with the following
exceptions:
1. Modifications to the FLTK configure script, config
header file, and makefiles by themselves to support
a specific platform do not constitute a modified or
derivative work.
The authors do request that such modifications be
contributed to the FLTK project - send all
contributions to "fltk-bugs@fltk.org".
2. Widgets that are subclassed from FLTK widgets do not
constitute a derivative work.
3. Static linking of applications and widgets to the
FLTK library does not constitute a derivative work
and does not require the author to provide source
code for the application or widget, use the shared
FLTK libraries, or link their applications or
widgets against a user-supplied version of FLTK.
If you link the application or widget to a modified
version of FLTK, then the changes to FLTK must be
provided under the terms of the LGPL in sections
1, 2, and 4.
4. You do not have to provide a copy of the FLTK license
with programs that are linked to the FLTK library, nor
do you have to identify the FLTK license in your
program or documentation as required by section 6
of the LGPL.
However, programs must still identify their use of FLTK.
The following example statement can be included in user
documentation to satisfy this requirement:
[program/widget] is based in part on the work of
the FLTK project (http://www.fltk.org).
-----------------------------------------------------------------------
GNU LIBRARY GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is
numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it. You can use it for
your libraries, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.
Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library. If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software. To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs. This
license, the GNU Library General Public License, applies to certain
designated libraries. This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.
The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it. Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program. However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.
Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries. We
concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves. This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them. (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.) The hope is that this
will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, while the latter only
works together with the library.
Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License"). Each licensee is
addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
d) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public
License along with this library; if not, write to the Free
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

53
win32/libdocs/fltk/CREDITS Normal file
View file

@ -0,0 +1,53 @@
CREDITS - Fast Light Tool Kit (FLTK) Version 1.1.4
--------------------------------------------------
This file lists the people responsible for the toolkit you
are now using. If you've looking for your name in lights
but we've forgotten you here, please send an email to
"fltk-bugs@fltk.org" and we'll update this file accordingly.
CORE DEVELOPERS
The following people do the day-to-day development of FLTK:
Craig P. Earls
Curtis Edwards (trilec@users.sourceforge.net)
Gustavo Hime (hime@users.sourceforge.net)
Talbot Hughes
Robert Kesterson (robertk@users.sourceforge.net)
Matthias Melcher (matthias@users.sourceforge.net)
James Dean Palmer (jamespalmer@users.sourceforge.net)
Vincent Penne (vincentp@users.sourceforge.net)
Bill Spitzak (spitzak@users.sourceforge.net)
Michael Sweet (easysw@users.sourceforge.net)
Carl Thompson (clip@users.sourceforge.net)
Nafees Bin Zafar (nafees@users.sourceforge.net)
OTHER CONTRIBUTORS
The following people have contributed fixes or enhancements
for FLTK:
Teun Burgers
Paul Chambers
Fabien Costantini
Stephen Davies
Greg Ercolano
Yuri Fedorchenko
George Garvey
Mikael Hultgren
Stuart Levy
Howard Lightstone
Mike Lindner
Alexander Mai
Alexander Rabi
James Roth
Albrecht Schlosser
Andrea Suatoni
Paul Sydney
Aaron Ucko
Emanuele Vicentini
Jim Wilson
Ken Yarnall

213
win32/libdocs/fltk/README Normal file
View file

@ -0,0 +1,213 @@
README - Fast Light Tool Kit (FLTK) Version 1.1.4
-------------------------------------------------
WHAT IS FLTK?
The Fast Light Tool Kit ("FLTK", pronounced "fulltick") is a
a cross-platform C++ GUI toolkit for UNIX(r)/Linux(r) (X11),
Microsoft(r) Windows(r), and MacOS(r) X. FLTK provides
modern GUI functionality without the bloat and supports 3D
graphics via OpenGL(r) and its built-in GLUT emulation. It
was originally developed by Mr. Bill Spitzak and is
currently maintained by a small group of developers across
the world with a central repository in the US.
LICENSING
FLTK comes with complete free source code. FLTK is available
under the terms of the GNU Library General Public License.
Contrary to popular belief, it can be used in commercial
software! (Even Bill Gates could use it.)
ON-LINE DOCUMENTATION
All of the documentation is in HTML in the subdirectory
"documentation". The "index.html" file should be your
starting point. PostScript(tm) and PDF versions of this
documentation is also available from the FLTK web site at:
http://www.fltk.org/documentation.php
BUILDING AND INSTALLING FLTK UNDER UNIX AND MacOS X
In most cases you can just type "make". This will run
configure with the default (no) options and then compile
everything.
FLTK uses GNU autoconf to configure itself for your UNIX
platform. The main things that the configure script will
look for are the X11, OpenGL (or Mesa), and JPEG header and
library files. Make sure that they are in the standard
include/library locations. If they aren't you need to
define the CFLAGS, CXXFLAGS, and LDFLAGS environment
variables.
If you aren't using "gcc", "g++", "c++", or "CC" for your
C++ compiler, you'll also need to set the CXX environment
variable. Similarly, if you aren't using "gcc" or "cc" for
your C compiler you'll need to set the CC environment
variable.
You can run configure yourself to get the exact setup you
need. Type "./configure <options>". Options include:
--enable-cygwin - Enable the Cygwin libraries (WIN32)
--enable-debug - Enable debugging code & symbols
--disable-gl - Disable OpenGL support
--enable-shared - Enable generation of shared libraries
--enable-threads - Enable multithreading support
--enable-xdbe - Enable the X double-buffer extension
--enable-xft - Enable the Xft library (anti-aliased fonts)
--bindir=/path - Set the location for executables
[default = /usr/local/bin]
--libdir=/path - Set the location for libraries
[default = /usr/local/lib]
--includedir=/path - Set the location for include files.
[default = /usr/local/include]
--prefix=/dir - Set the directory prefix for files
[default = /usr/local]
When the configure script is done you can just run the
"make" command. This will build the library, FLUID tool, and
all of the test programs.
To install the library, become root and type "make
install". This will copy the "fluid" executable to
"bindir", the header files to "includedir", and the library
files to "libdir".
BUILDING FLTK UNDER MICROSOFT WINDOWS
There are two ways to build FLTK under Microsoft Windows.
The first is to use the VC++ 6.0 project files under the
"visualc" directory. Just open (or double-click on) the
"fltk.dsw" file to get the whole shebang.
The second method is to use a GNU-based development tool
with the files in the "makefiles" directory. To build
with the CygWin tools, use the supplied configure script
as specified in the UNIX section above:
sh configure ...options...
To build using other tools simply copy the appropriate
makeinclude and config files to the main directory and do a
make:
copy makefiles\Makefile.<env> Makefile
make
BUILDING FLTK UNDER OS/2
The current OS/2 build requires XFree86 for OS/2 to work. A
native Presentation Manager version has not been implemented
yet (volunteers are welcome!).
To build the XFree86 version of FLTK for OS/2, copy the
appropriate makeinclude and config files to the main
directory and do a make:
copy makefiles\Makefile.os2x Makefile
make
INTERNET RESOURCES
FLTK is available on the 'net in a bunch of locations:
- WWW: http://www.fltk.org
http://fltk.sourceforge.net
- FTP: ftp://ftp.easysw.com/pub/fltk
ftp://ftp2.easysw.com/pub/fltk
ftp://ftp.northamerica.net/pub/ESP/fltk
ftp://ftp.funet.fi/mirrors/ftp.easysw.com/pub/fltk
- EMail: fltk@fltk.org [see instructions below]
fltk-bugs@fltk.org [for reporting bugs]
To send a message to the FLTK mailing list ("fltk@fltk.org")
you must first join the list. Non-member submissions are
blocked to avoid problems with SPAM.
To join the FLTK mailing list, send a message to
"majordomo@fltk.org" with "subscribe fltk" in the message
body. A digest of this list is available by subscribing to
the "fltk-digest" mailing list.
REPORTING BUGS
To report a bug in FLTK, send an email to
"fltk-bugs@fltk.org". Please include the FLTK version,
operating system & version, and compiler that you are using
when describing the bug or problem. You can also submit a
bug on the SourceForge pages.
For general support and questions, please use the FLTK
mailing list at "fltk@fltk.org".
MESA
Currently the best way to get OpenGL on your Linux system is
to use Mesa. FLTK has been tested with Mesa on several
machines (and also with "real" OpenGL on SGI machines). Mesa
is available at:
http://www.mesa3d.org
The configure script will not see Mesa unless it is
installed as either libGL or libMesaGL. If you don't want
to do this you will have to edit config.h (set HAVE_GL to 1)
and makeinclude (add the libraries).
TRADEMARKS
Microsoft and Windows are registered trademarks of Microsoft
Corporation. UNIX is a registered trademark of the X/Open
Group, Inc. OpenGL is a registered trademark of Silicon
Graphics, Inc. MacOS is a registered trademark of Apple
Computers, Inc.
COPYRIGHT
FLTK is copyright 1998-2003 by Bill Spitzak
(spitzak@users.sourceforge.net) and others, including:
Craig P. Earls
Curtis Edwards (trilex@users.sourceforge.net)
Gustavo Hime (hime@users.sourceforge.net)
Talbot Hughes
Robert Kesterson (robertk@users.sourceforge.net)
Matthias Melcher (matthiaswm@users.sourceforge.net)
James Dean Palmer (jamespalmer@users.sourceforge.net)
Vincent Penne (vincentp@users.sourceforge.net)
Michael Sweet (easysw@users.sourceforge.net)
Carl Thompson (clip@users.sourceforge.net)
Nafees Bin Zafar (nafees@users.sourceforge.net)
This library is free software; you can redistribute it
and/or modify it under the terms of the GNU Library General
Public License as published by the Free Software Foundation;
either version 2 of the License, or (at your option) any
later version.
This library is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the GNU Library General Public License for
more details.
You should have received a copy of the GNU Library General
Public License along with this library; if not, write to the
Free Software Foundation, Inc., 59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA.