diff options
| author | Michael R Sweet <michael.r.sweet@gmail.com> | 2001-11-29 19:24:00 +0000 |
|---|---|---|
| committer | Michael R Sweet <michael.r.sweet@gmail.com> | 2001-11-29 19:24:00 +0000 |
| commit | 09daf20b81cdae78772f07c0af22a571d7cc73eb (patch) | |
| tree | 1641f788cafe20b505355b0479ba0d528297eb30 /documentation/intro.html | |
| parent | b105ab8b7fb6281635076559aae96f2b3b12fc51 (diff) | |
Documentation updates galore (up to chapter 7, still need to do chapter
8 and 9, tweek the appendices, and recapture the screenshots...)
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@1786 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/intro.html')
| -rw-r--r-- | documentation/intro.html | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/documentation/intro.html b/documentation/intro.html index c92b860af..abdf5a454 100644 --- a/documentation/intro.html +++ b/documentation/intro.html @@ -20,7 +20,7 @@ operating system. The system only has to provide arbitrary shaped but featureless windows, a powerful set of graphics drawing calls, and a simple <I>unalterable</I> method of delivering events to the owners of the windows. NeXT (if you -ignored NextStep) provided this, but they chose to hide it and +ignored NextStep) provided this, but they chose to hide it and tried to push their own baroque toolkit instead.</P> <P>Many of the ideas in FLTK were developed on a NeXT (but @@ -54,7 +54,7 @@ he integrated his table-driven menus into it. Several very large programs were created using this version of Forms.</P> <P>The need to switch to OpenGL and GLX, portability, and a -desire to use C++ subclassing required a rewrite of Forms. +desire to use C++ subclassing required a rewrite of Forms. This produced the first version of FLTK. The conversion to C++ required so many changes it made it impossible to recompile any Forms objects. Since it was incompatible anyway, Bill decided @@ -106,7 +106,7 @@ is now included with several Linux distributions.</P> WIN32 version - only about 10% of the code is different.</LI> - <LI>Interactive user interface builder program. Output is + <LI>Interactive user interface builder program. Output is human-readable and editable C++ source code.</LI> <LI>Support for overlay hardware, with emulation if none @@ -145,7 +145,7 @@ functions and structures started with "fl_". This naming was extended to all new methods and widgets in the C++ library, and this prefix was taken as the name of the library. It is almost impossible to search for "FL" on the -Internet, due to the fact that it is also the abbreviation for +Internet, due to the fact that it is also the abbreviation for Florida. After much debating and searching for a new name for the toolkit, which was already in use by several people, Bill came up with "FLTK", including a bogus excuse that it @@ -159,7 +159,7 @@ everything.</P> <P>FLTK uses GNU autoconf to configure itself for your UNIX platform. The main things that the configure script will look -for are the X11 and OpenGL (or Mesa) header and library files. +for are the X11 and OpenGL (or Mesa) header and library files. If these cannot be found in the standard include/library locations you'll need to define the <tt>CFLAGS</tt>, <tt>CXXFLAGS</tt>, and <tt>LDFLAGS</tt> environment variables. @@ -231,13 +231,13 @@ tool, and all of the test programs.</P> <P>To install the library, become root and type "make install". This will copy the "fluid" executable -to "bindir", the header files to +to "bindir", the header files to "includedir", and the library files to "libdir".</P> <H2>Building FLTK Under Microsoft Windows</H2> -<P>There are three ways to build FLTK under Microsoft Windows. +<P>There are three ways to build FLTK under Microsoft Windows. The first is to use the Visual C++ 5.0 project files under the "visualc" directory. Just open (or double-click on) the "fltk.dsw" file to get the whole shebang.</P> @@ -286,7 +286,7 @@ EMX 0.9d and libExt (from <A HREF="http://posix2.sourceforge.net">posix2.sourceforge.net</A>) is installed. -<P>To build the XFree86 version of FLTK for OS/2, copy the appropriate +<P>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: </P> <UL><PRE> @@ -320,9 +320,9 @@ interface, so XFree86 will no longer be required.</P> <DD><A HREF="ftp://gd.tuwien.ac.at/hci/fltk">Austria (gd.tuwien.ac.at)</A> <DT>EMail</DT> - <DD><A href="mailto:fltk@fltk.org">fltk@fltk.org</A> [see + <DD><A href="mailto:fltk@fltk.org">fltk@fltk.org</A> [see instructions below] - <DD><A href="mailto:fltk-bugs@fltk.org">fltk-bugs@fltk.org</A> [for + <DD><A href="mailto:fltk-bugs@fltk.org">fltk-bugs@fltk.org</A> [for reporting bugs] <DT>News</DT> @@ -335,7 +335,7 @@ interface, so XFree86 will no longer be required.</P> Non-member submissions are blocked to avoid problems with unsolicited email.</P> -<P>To join the FLTK mailing list, send a message to +<P>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.</P> @@ -351,7 +351,7 @@ any kind of help without that basic information.</P> <P>Bugs can also be reported to the "fltk.bugs" newsgroup or on the SourceForge bug tracker pages.</P> -<P>For general support and questions, please use the FLTK mailing list +<P>For general support and questions, please use the FLTK mailing list at "fltk@fltk.org" or one of the newsgroups.</P> </BODY> |