On Thursday 22 May 2003 04:19, Feng Xie wrote:
> Hello, Jim
> I am now working on the glossary pages. What I am going to do is adding
> codes to the parse_page.pl, which is to go on to generate static glossary
> pages after the normal processing of generating static content pages.
> display_glossary.pl will do the job you described: generate the frame and
> read the concerning glossary page in. The following are some details.
> Waiting for comments.
I am not sure we are thinking about the same thing and I want to be sure.
There is one function that creates the static glossary page without any of the
menus, etc, just the actual glossary entry. When display_glossary.pl is
called from a web page it is passed the ID of the glossary entry (for
example) and then displays the all menus plus the static glossary page. Is
that what you talking about?
> With "parse_page.pl -i" , which generate/regenerate all the content pages,
> all the glossary pages are generated/regenerated also. While in order to
> enable the tool to generate single glossary pages, a new option "-g" is
Okay sounds reasonable. The -g just creates all of the glossary entries right?
What about the index of glossary terms that contais all of the entries? Are
you going to work on that?
> Naming of the glossary pages:
> Use the glossary ID in glossary.data. For example, the page name for the
> "UNIX" glossary is 474.html.
I had originally been thinking about something like "UNIX.html", but it sounds
okay to me if you use the ID numbers. I cannot think of anytime where someone
would want to access the pages directly, and if they did they can figure out
what page is which.
> Where to store the glossary pages:
> The generated glossary pages will be put into a new directory named
How about just "glossary"? It really doesn't matter. I am just lazy. However,
once it is coded, no one will need to access it directly.
> The problem is about the display_glossary.pl. What kinds of parameters does
> it need ? glossary ID comes first for sure, but how about the
> previous/original page code, the current TYK code and the current
> mysiteconfig code, which are used by display.pl ? As I noticed,
> previous/original page code is always 0, which means it's never used. I am
> not sure if it needs the TYK code and the current mysiteconfig code. Could
> you explain a little bit about them ?
Originally the previous page code kept track of the very last page you were on
and the original page code was where you entered things like the the
Questions (TYK), the TYK Code is used within the TYK section to keep track of
options, etc and the mysiteconfig defines the appearance. Eventually I want
to save the TYK code and mysiteconfig as cookies and maybe the other things
as well. The current page code is always used to keep track of which page is
displayed. This is the most important one.
I am wondering why the previous/original page code is always 0. It shouldn't
be. How do you get to the glossary pages?
"Be more concerned with your character than with your reputation. Your
character is what you really are while your reputation is merely what others
think you are." -- John Wooden
Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info