From ecd2c821be8a72b0364cf3e08d102e3f9a82defc Mon Sep 17 00:00:00 2001 From: Michael R Sweet Date: Mon, 26 Nov 2001 21:40:14 +0000 Subject: Doco updates. Remove unneeded files from the makefiles directory. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@1735 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- documentation/intro.html | 144 ++++++++++++++++++++++++++++++----------------- 1 file changed, 93 insertions(+), 51 deletions(-) (limited to 'documentation/intro.html') diff --git a/documentation/intro.html b/documentation/intro.html index fe9d5fcac..c92b860af 100644 --- a/documentation/intro.html +++ b/documentation/intro.html @@ -1,43 +1,45 @@ +

1 - Introduction to FLTK

The Fast Light Tool Kit ("FLTK", pronounced "fulltick") is a LGPL'd C++ graphical user interface toolkit for X (UNIX®), OpenGL®, and Microsoft® -Windows® NT 4.0, 95, or 98. 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.

+Windows®. Work is also underway to support FLTK under MacOS +X. 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.

History of FLTK

-

It has always been Bill's belief that the GUI API of all modern -systems is much too high level. Toolkits (even FL) are not what -should be provided and documented as part of an operating system. The -system only has to provide arbitrary shaped but featureless windows, a -powerful set of graphics drawing calls, and a simple unalterable -method of delivering events to the owners of the windows. NeXT (if -you ignored NextStep) provided this, but they chose to hide it and -tried to push their own baroque toolkit instead...

+

It has always been Bill's belief that the GUI API of all +modern systems is much too high level. Toolkits (even FLTK) are +not what should be provided and documented as part of an +operating system. The system only has to provide arbitrary +shaped but featureless windows, a powerful set of graphics +drawing calls, and a simple unalterable method of +delivering events to the owners of the windows. NeXT (if you +ignored NextStep) provided this, but they chose to hide it and +tried to push their own baroque toolkit instead.

Many of the ideas in FLTK were developed on a NeXT (but not using NextStep) in 1987 in a C toolkit Bill called "views". Here he came up with passing events downward in the tree and having the handle routine return a value -indicating the used the event, and the table-driven menus. In +indicating the used the event, and the table-driven menus. In general he was trying to prove that complex UI ideas could be entirely implemented in a user space toolkit, with no knowledge or support by the system.

After going to film school for a few years, Bill worked at -Sun Microsystems on the (doomed) NeWS project. Here he found an -even better and cleaner windowing system, and he reimplemented -"views" atop that. NeWS did have an unnecessarily +Sun Microsystems on the (doomed) NeWS project. Here he found an +even better and cleaner windowing system, and he reimplemented +"views" atop that. NeWS did have an unnecessarily complex method of delivering events which hurt it. But the designers did admit that perhaps the user could write just as -good of a button as they could, and officially exposed the -lower level interface.

+good of a button as they could, and officially exposed the lower +level interface.

With the death of NeWS Bill realized that he would have to live with X. The biggest problem with X is the "window @@ -45,7 +47,7 @@ manager", which means that the toolkit can no longer control the window borders or drag the window around.

At Digital Domain Bill discovered another toolkit, -"Forms". Forms was similar to his work, but provided +"Forms". Forms was similar to his work, but provided many more widgets, since it was used in many real applications, rather then as theoretical work. He decided to use Forms, except he integrated his table-driven menus into it. Several very large @@ -101,8 +103,8 @@ is now included with several Linux distributions.

performance.
  • Precise low-level compatability between the X11 and - WIN32 version (only about 10% of the code is - different).
    • + WIN32 version - only about 10% of the code is + different.
  • Interactive user interface builder program. Output is human-readable and editable C++ source code.
    • @@ -235,13 +237,22 @@ to "bindir", the header files to

    Building FLTK Under Microsoft Windows

    -

    There are two ways to build FLTK under Microsoft Windows. +

    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.

    -

    The second method is to use a GNU-based development tool with -the files in the "makefiles" directory. To build +

    The second method is to use the configure script +included with the FLTK software; this has only been tested with +the CygWin tools:

    + + + +

    The final method is to use a GNU-based development tool with +the files in the "makefiles" directory. To build using one of these tools simply copy the appropriate makeinclude and config files to the main directory and do a make:

    @@ -252,19 +263,23 @@ make

    Using the Visual C++ DLL Library

    -The "fltkdll.dsp" project file builds a DLL-version of the FLTK -library. Because of name mangling differences between PC compilers (even -between different versions of Visual C++!) you can only use the DLL that -is generated with the same version compiler that you built it with. -

    When compiling an application or DLL that uses the FLTK DLL, you will need -to define the FL_DLL preprocessor symbol to get the correct linkage -commands embedded within the FLTK header files. + +

    The "fltkdll.dsp" project file builds a DLL-version +of the FLTK library. Because of name mangling differences +between PC compilers (even between different versions of Visual +C++!) you can only use the DLL that is generated with the same +version compiler that you built it with.

    + +

    When compiling an application or DLL that uses the FLTK DLL, +you will need to define the FL_DLL preprocessor symbol +to get the correct linkage commands embedded within the FLTK +header files.

    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!). +

    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!).

    The current set of Makefiles/configuration failes assumes that EMX 0.9d and libExt @@ -274,18 +289,28 @@ is installed.

    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:

    - + +

    Building FLTK Under MacOS X

    + +

    The current version of FLTK requires the XFree86 X server for +Darwin. Follow the instructions for building FLTK under +UNIX.

    + +

    Future versions of FLTK will provide a Carbon-based window +interface, so XFree86 will no longer be required.

    Internet Resources

    -FLTK is available on the 'net in a bunch of locations: + +

    FLTK is available on the 'net in a bunch of locations:

    +
    +
    WWW -
    http://www.fltk.org +
    http://www.fltk.org/
    FTP
    California, USA (ftp.fltk.org) @@ -299,18 +324,35 @@ FLTK is available on the 'net in a bunch of locations: instructions below]
    fltk-bugs@fltk.org [for reporting bugs] + +
    News
    +
    news.easysw.com
    +
    -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 unsolicited email. + +

    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 +unsolicited email.

    +

    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.

    +"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. + +

    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. We will be unable to provide +any kind of help without that basic information.

    + +

    Bugs can also be reported to the "fltk.bugs" newsgroup or on the +SourceForge bug tracker pages.

    +

    For general support and questions, please use the FLTK mailing list -at "fltk@fltk.org".

    - +at "fltk@fltk.org" or one of the newsgroups.

    + + + -- cgit v1.2.3