File: README

package info (click to toggle)
galrey 1.0.2-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 140 kB
  • ctags: 60
  • sloc: perl: 359; python: 171; sh: 149; makefile: 49
file content (55 lines) | stat: -rw-r--r-- 2,668 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Using galrey.

First, take a look a the config file (galrey.rc). Default values would be ok.

The install.sh script will place it in /etc but here comes a quick/important 
note on the config file location: Galrey NEEDS the config file to work, and it 
will try its best to find it. First, it looks if the related command line parameter 
is used (see below), then it looks in the current directory, then in the user home 
directory and finally in the /etc dir. Probably, you need a galrey.rc for each 
gallery you create, and for this reason you'd probably have a galrey.rc in each 
gallery directory. So galrey will complain (but continues...) when it find the
config file in /etc !

After galrey.rc, have a look into galrey.tpl (aka the 'template' file).
The .tpl file is mostly a normal HTML file, which you provide as a template
to galrey for creating the final work. Inside the .tpl file you can see some
"strange" fields. These fields are substitued with actual data, when the
program runs:

$TITLE$       : it is substitute with the "title" you have defined in galrey.rc
$FIRST$       : is the first html file generated
$PREVIOUS$    : is the "previous" html file 
$INDEX$       : is the index file as you defined it in galrey.rc
$NEXT$        : is the "next" html file
$LAST$        : is the "last" html file
$ID$          : is the number of the current file
$TOTAL$       : is the total number of files in the collection
$CURRENT$     : is the current image file
$WIDTH        : is the width of the image
$HEIGHT       : is the height of the image
$DESCRIPTION$ : is the description associated with the image read from
                the "memofile".

You can use some command line options to override some galrey defaults:

 -i <images path> to redefine where the image files reside
 -o <output path> to redefine where the generated file will be placed
 -t <template file> to specify a particular template file (default is ./galrey.tpl) 
 -c <config file> to specify a particular config file (default is ./galrey.rc)
 -m <memo file> to specify where the $DESCRIPTION$s must be read

Remember that all these options (except the location of config file, of course)
are also in the galrey.rc config file. Passing command line options will
OVERRIDE the information in config file.

Once finished, get the code into "index.html", or whatever you named it, and
get the HTML code galrey had create for you. Then paste it into the page you 
want to be the _real_ index.html. The index.html created by galrey is only
provided to preview the work. It does not contain any graphics or addictional
color. It is not configurable in any way, though.

That's all.

FleXer.