
gHTTrack v0.5.2 - Frontend for HTTrack
(C)2007 Paul Schuurmans


Installation
============
The configure script has been omitted from this package due to its size 
and the fact that it doesn't work on all systems.  Instead, you run an 
autogen script which creates the configure script.  If you need to pass 
any arguments to the configure script, you can do so on the autogen.sh 
command line.  Other than that, installation is pretty much the same as 
usual:

  sh autogen.sh
  make
  make install



Using Anjuta
============
This package includes an Anjuta 1.0.2 project file.  Because of the missing 
configure script, "Build|Build" won't work initially; you'll need to select 
"Build|Auto generate..." first.



General
=======
This is a frontend for Xavier Roche's 'HTTrack Website Copier'.  Being a 
frontend, it won't work unless you have the httrack backend installed on your 
system.  If you have httrack installed, there should be some documentation 
somewhere in your install path.  This intro includes a few notes for the 
gHTTrack frontend only.  For details concerning the HTTrack engine, consult the 
httrack documentation.

Although the amount of options may seem a bit overwhelming at first, the only 
two that you really need to specify are the URLs (Web addresses) to mirror and 
a destination path (the directory where fetched files should be stored).  All 
others are optional and the default settings should suffice for most purposes.



The User Interface
==================
Previous versions of this frontend included a menu, toolbar, and various 
dialogs.  This version uses a Notebook widget with four tabbed pages 
(Introduction, Options, Actions, and HTTrack), as described below.

The Options Page
----------------
This page replaces the old Options dialog.  This is where you set various 
options that will be used as arguments/parameters to the HTTrack main engine.  
Note that all options marked with an asterisk (*) are httrack defaults and do 
not need to be specified explicitly.  Once you've set all the desired options, 
press the [OK] button to move on to the next step.

The Actions Page
----------------
This page replaces the menu and toolbar used in previous versions of gHTTrack.  
This is where you select an action to perform.  Note: If the 'Project Info' and 
'HTTrack Command Line' boxes are empty, it means you haven't yet pressed the 
[OK] button on the Options page.  Or, if only the 'HTTrack Command Line' box 
is empty, it means that either there are no URLs specified or no destination 
path has been set.

The HTTrack Page
----------------
This is basically the same as in previous versions of gHTTrack.  This is where 
you read (or re-read) the HTTrack log file.  You can check the end of the log 
to find out if HTTrack has finished processing the mirror.



Programming Notes
=================
- For callbacks that use FileDlg, the chain of commands are:
  - The initial callback should call AppRunFileDialog(),
  - AppRunFileDialog() displays the FileDlg dialog,
  - The actual handler code should be placed in on_filedlg_btn_ok_clicked().
- When adding new options, modify the following:
  - AppShowSettings()
  - Global Options array in main.c
  - OPTIONCOUNT definition in main.h
- For options that use a GtkComboBoxEntry widget, set the maximum length and 
  tooltip in AppDoWidgetSetup().

