Download Latest Version webpage-1.0.132-152-noarch-8.6.10.zip (343.5 kB)
Email in envelope

Get an email when there's a new version of TclFltk

Home / Windows
Name Modified Size InfoDownloads / Week
Parent folder
README 2016-05-21 6.8 kB
TclFltk-1.0.885-3-single_buffering-i386-Windows-8.5.11-bin.zip 2016-05-20 3.4 MB
TclFltk-1.0.885-8-double_buffering-i386-Windows-8.5.11-bin.zip 2016-05-20 3.4 MB
TclFltk-1.0.853-1-single_buffering-i386-Windows-8.5.11-bin.zip 2016-01-22 3.4 MB
TclFltk-1.0.699-3-single_buffering-i386-Windows-8.5-bin.zip 2013-08-13 3.4 MB
TclFltk-1.0.423.0-19-double_buffering-8.4a2-Windows-i386-bin.zip 2011-12-22 2.6 MB
Totals: 6 Items   16.2 MB 0
Fltk for Tcl/Tk Version 1.0.885-8
Built on io on Fri May 20 21:35:16 EDT 2016 for Windows i386

1. Overview

	This is a dynamic extension to the Tcl/Tk application development
environment that implements a language binding between Tcl/Tk and the
Fast Light Tool Kit (FLTK). Using this extension you can develop GUI
applications using Tcl scripts that make use of the FLTK widget set. You
would want to do this if you like the FLTK look and feel and wish to
enjoy the performance of a native GUI implementation on your machine. The
package is similar in nature and function to the traditional Tk GUI
development extension.

2. Requirements

	You need to have Tcl/Tk installed on your machine. Tcl/Tk distributions
are available on the internet from a variety of places, including www.tcl.tk and
sourceforge.net. Most UNIX machines will have Tcl/Tk already installed.

	If you are installing the binary distributions of this package, you
do not need to have anything else. If you are building from source, then
you need to have the following:

	. An FLTK source distribution at or later than 1.1.0
	. The Image 1.2 distribution from my web site
	. The Tcl/Tk source distribution and libraries
	. The OpenGL libraries or the MESA equivalents
	. The JPEG,PNG and TIFF libraries

	For the source build, you need to be comfortable with make and its
uses, and have a gcc compiler. I do not build on Windows any more, so there
are no makefiles for VC++ or other Windows compilers. I use MINGW on a
Linux box. Its much cleaner, faster and less expensive, as well as being
a generally better compiler and without the need to experience the unending
misery of being a Windows user. 
	
3. Installation

	The release package file name is generated with the following component
values:

	TclFltk-Version.Patchlevel-Build-Technology-Target-TclVersion-bin.Suffix
	
where: 	Version is the TclFltk version number
	Pathlevel is the TclFltk patch number
	Build is the current package build number
	Technology is the target architecture (i386, armv4t...)
	TclVersion is the Tcl/Tk library version
	Suffix is the package type (deb, rpm, zip.....)

You should acquire a package that matches your installation requirements. If you
don't find one on the distribution site, e-mail me.

	This release has been built with the following components:

	. FLTK Source Version 1.1.3
	. Image Version 1.2
	. Tcl/Tk Version 8.5.11
	
	This package will work with any Tcl/Tk installation post version 8.1.
If the Tcl/Tk installation on your machine is not the same release level as the
one I used to build the package, the following procedure will work to invoke
the extension:

	tclsh
	package require Fltk
	.....
	
If you use the fltkwish custom shell, the version of your Tcl/Tk installation must
match the version used to build fltkwish. This package contains a binary
fltkwish8.5 with a link fltkwish which will invoke it, so scripts that
invoke it should not need changes.

	You may need to make a link between your actual Tcl/Tk libraries (.DLL or .so)
and the library version used by this package. Some linkers default to a specific
version form instead of a generic libtcl.so or LIBTCL.DLL form. On some Linux
systems, use a command like:

	cd /usr/lib; sudo ln -sf libtcl8.5.so.0 libtcl8.5.so
	
On Windows you can use a shortcut.

	If you are using a package manager (RPM, DPKG), the archive will 
install using the appropriate tool for that type of package. 

	For tar and zip archives, Unpack the archive in an appropriate place. 
On a Windows box the place for binary distributions is where Tcl is installed. 
On a Linux box, the binary distribution contains a file called install-binaries 
which will do it for reasonably typical Linux setups, such as Fedora or
Debian distributions. For other setups, hands on methods may be required.

	For the source build, you need to be comfortable with make and its
uses, and have a gcc compiler. I do not build on Windows any more, so there
are no makefiles for VC++ or other Windows compilers. I use MINGW on a
Linux box. Its much cleaner, faster and less expensive, as well as being
a generally better compiler and without the need to experience the unending
misery of being a Windows user.

	A proper installation using a package manager will display an output 
from the tclfltk_test_script command installed in the installation bin
directory. If a zip or tar archive is used, you should cd to the bin directory
and execute it. Under Windows, you MUST be in the bin directory for it to
work. Generally, if the test script dies, it means your install is not working.

	This package will work with any Tcl/Tk distribution that supports the
STUBS implementation. Generally, Tcl/Tk after 8.1 will have STUBS. Regardless
of the build of Tcl/Tk used for this build, a simple soft link to the libraries
of your Tcl/Tk distribution will result in a working version of this package.
Linux uses the 'ln -sf' command for soft links, Windows uses a gui method. This
package will look for Tcl/Tk libraries that match those used in the build. Just
create a link with the library version used here to the versions on your
machine. 

4. Documentation

	There is a file in PDF format that has all of the documentation for the
commands added to Tcl/Tk by the extension. The best way to read it is with
the Acrobat reader on a Windows box, but the UNIX tools xpdf, gv, evince and
Acrobat will also work well. The documentation contains lots of examples of how
to do things. The PDF file is available on the web site that has the distributions.
It is a separate download as a space saving measure.

	The scripts directory that is installed in the library target contains a lot 
of demo and test scripts. Have a look at these to see how things work.

5. Licence

	You are free to use, copy and modify the package for any purpose except
commercial distribution. Commercial distribution is prohibited without the
express written permission of the author. Any redistribution of the materials
must contain an intact, unmodified copy of this README file.

	The included LICENSE file contains additional information respecting the 
license for this application. Please read it.

6. Warranty

	None. No warranty of any kind is offered. Use this software at your own
risk and expense. The author assumes no responsibility whatsoever for any
loss or damage to your interests or property due either directly or indirectly or 
for any other reason or cause related to the use of this software. By installing 
this distribution package you acknowledge having read and accepted the terms of 
this licence.

7. Bugs

	Report bugs, errors, and suggestions for improvements to:

	ifindleton@videotron.ca

8. Copyright

	All materials that form part of this package are 
	Copyright (C) I.B.Findleton, 1996-2016
	All Rights Reserved.

Source: README, updated 2016-05-21