[greenstone-devel] Greenstone formatting changes

From Stefan Boddie
DateThu, 17 Jul 2003 13:22:31 -0600
Subject [greenstone-devel] Greenstone formatting changes
Hi Dynal (and list),

I've made some changes to allow more configuration of the way greenstone
formats various things (with some help from Aly Dharshi here at
Lethbridge University). Note that these changes are currently only
available in the CVS version of greenstone but will appear in the next
release. They are not in gsdl-2.40.

Changes are:

* You can set the number of columns used to display collections on the
home page. In the gsdl/etc/main.cfg file add something like:
SiteFormat HomePageCols 2
The default for HomePageCols is 3 so it'll look as it always has unless
you change it.

* You can display the collection list on the home page as a pulldown
menu, rather than using the default table of collection images. To do
that add the following to your gsdl/etc/main.cfg:
SiteFormat HomePageType pulldown
All this does is alter the html that appears in the dynamically
generated _homeextra_ macro. You can then move this macro around in home.dm.

* Likewise you can change the way the main navigation bar is displayed
within a collection (this is the bar with the "search", "titles a-z",
etc. buttons). If you add the following line to your collection's
collect.cfg file the dynamically generated SearchSubjectsFromDates macro will
produce a pulldown menu instead of the bar with buttons on it.
format NavigationBar pulldown

* The document content page can now be generated entirely by format
strings (including placement of the table of contents, the document
image, and all the document buttons (detach, expand contents, etc).
For example, you can add something like the following to your
collection's collect.cfg file:
format AllowExtendedOptions true
format DocumentHeading "<center>
<table border=0 width=537>
<tr valign=top>
<td><img src='[DocImage]'></td>
<tr valign=top>
<td colspan=2>

The AllowExtendedOptions option must be set for this stuff to work. This
is mostly for efficiency since we need to generate the table of contents
several times now that we embed it in format statements. For collections
that don't set AllowExtendedOptions this won't be done and so the new
format statement thingies ([DocTOC], [DocImage], etc.) won't work.
Setting it also effectively disables the older DocumentContents,
DocumentButtons, and DocumentImages options and prevents any of the
hard-coded html tables and stuff from being output around DocumentHeading.

There were a few other similar changes that Dynal wanted but which we
haven't go to yet. Aly Dharshi will hopefully be getting to these things
over the next little while.