Initial revision

Author: jcid

AUTHORS

@@ -0,0 +1,68 @@
+
+     _________________________________________________________________
+   
+                              Dillo project's team
+     _________________________________________________________________
+   
+   Project maintainer:
+          * Jorge Arellano Cid 
+          
+   Core Developers:
+          * Jorge Arellano Cid 
+          * Sebastian Geerken 
+          
+   Steady developers:
+          * Livio Baldini
+          * Eric Gaudet 
+          * J�rgen Viksell 
+          
+   Contributors:
+          * Lars Clausen
+          * Geoff Lane 
+          * Sammy Mannaert 
+          * James McCollough 
+          
+   Patches:
+          * Philip Blundell
+          * Francis Daly
+          * Sam Dennis 
+          * Melvin Hadasht
+          * Madis Janson
+          * Andrew McPherson 
+          * Sean 'Shaleh' Perry
+          * Marcos Ram�rez
+          * Adam Sampson
+          * Andreas Schweitzer
+          * Dominic Wong 
+     _________________________________________________________________
+   
+   Web site logo:
+          * Eric Gaudet
+          * Jarrod Henry 
+          
+   Gzilla author:
+          * Raph Levien 
+     _________________________________________________________________
+
+
+
+
+-------------------
+Up to gzilla-0.1.7:
+-------------------
+
+Raph Levien <raph@acm.org> is the author of gzilla.
+
+Christoph Thompson <obituary@freshmeat.net> and Tomas O"gren <stric@ing.umu.se>
+ added pixmaps for the buttons and the code encessary to make them work.
+ They also reorganized the source tree and gave general advice and tips.
+ (Tomas will be pleased to find that my personal bookmarks file is no longer
+ hard-coded into Gzilla. :))
+
+Ian Main <slow@intergate.bc.ca> did the bookmarks.
+
+Thanks to Otto Hammersmith, David Mosberger-Tang, and Peter Mattis for
+patches.
+
+Contributions are always welcome!
+

COPYING

@@ -0,0 +1,176 @@
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+
+   The file `configure.in' is used to create `configure' by a program
+called `autoconf'.  You only need `configure.in' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes a while.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  You can give `configure'
+initial values for variables by setting them in the environment.  Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory.  After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+     CPU-COMPANY-SYSTEM
+
+See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Operation Controls
+==================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+     Use and save the results of the tests in FILE instead of
+     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
+     debugging `configure'.
+
+`--help'
+     Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--version'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`configure' also accepts some other, not widely useful, options.
+

ChangeLog

@@ -0,0 +1,5 @@
+SUBDIRS = doc dlib dpip src dpid dpi
+
+EXTRA_DIST = ChangeLog.old dillorc2 install-dpi-local README-port
+
+sysconf_DATA = dillorc2

INSTALL

@@ -0,0 +1,33 @@
+----
+NEWS
+----
+
+Nov 2000:
+
+  Introduced a new design layer between the IO and the Dw.
+
+March 2001:
+
+  Finally the new dillo widget is ready! (dillo >= 0.4.0).
+  0.4.0 is able to cope with low resolution depths.
+
+Apr 2002:
+
+  We moved to:  http://dillo.cipsga.org.br/
+
+Dec 2002
+
+  We moved to:  http://dillo.auriga.wearlab.de/
+
+Jun 2003
+
+  http://www.dillo.org/     (hosted at the wearlab!)
+
+Sep 2007
+
+  The new FLTK2-based dillo code is released! (under GPL3)
+
+  Jorge.-
+  jcid@dillo.org
+  Project maintainer, core developer, patcher, you name it! :-)
+

Makefile.am

@@ -0,0 +1,76 @@
+=======
+ Dillo
+=======
+
+  This  is  an  alpha release of the next generation of the Dillo
+web  browser.  The  code  underwent  a major rewrite: significant
+parts  of  the  codebase  were  ported  to C++, and the rendering
+engine now uses the FLTK2 library instead of GTK1.
+
+  With  regard to Dillo 0.8.6, dillo-f15f has some advantages (as
+antialiasing and utf-8), and some disadvantages. The problems are
+simple  to  solve and only need some man months to complete. When
+we're  there,  dillo-f15f  will be easily regarded as better than
+the former series.
+
+  This is release should be regarded as alpha.
+
+
+  Here's a list of some well known problems:
+
+    * no iteration inside simple lists
+    * image links haven't been hooked yet
+    * you may experience crashes from "assert" statements from
+      unfinished code.
+    * the scrolling position is not yet updated (when following a
+      link, the former scroll position is kept).
+    * viewport scrolling is not yet optimized (takes lots of CPU)
+    * context menus are not yet completely hooked or activated
+
+    * no FRAMES rendering
+    * no https            -- read the FAQ to enable a protoype.
+
+
+------------
+Dpi programs
+------------
+
+  These  are  installed by "make install". If you don't have root
+access,  copy  "dillo"  and "dpid" to some directory in your path
+and  install  the  dpis by running "./install-dpi-local" from the
+top directory (they will be installed under ~/.dillo).
+
+
+----
+*BSD
+----
+
+  Dillo  may  compile on *BSD systems; please report on this.
+Please note that you'll need GNU make.
+
+  From  OpenBSD  >=  3.3,  gethost* calls are not thread safe. If
+your dillo crashes or locks at times, just use:
+
+    ./configure --disable-threaded-dns
+
+  so dillo uses a single thread for name resolving.
+
+
+-------
+Solaris
+-------
+
+  Dillo may compile and run OK on Solaris but (please report):
+
+    * use gmake (a symbolic link make -> gmake works OK)
+
+  Solaris is very inconsistent so you may need to add/remove:
+
+  -lrt -lposix4
+
+  at link time.
+
+    
+Jorge.-
+(jcid@dillo.org)
+Sep 30, 2007