linkbat-devel

[Linkbat-devel] next step

[Wayne <xie...@ho...>]

Hello Everyone !

Thanks for your comments, and they will make the codes better.

To summerize, I have got several things to do to produce the next =
version of the static_page_generating tool:
1) -F option, which is supposed to parse all the files in certain =
directory;
2) Generate static DYKs (Do You Know);
3) Handling the glossary popups and links;
4) More error handling.

Jim, I am considering your idea of splitting the codes into two pieces. =
Since I use existing functions to generate static pages by redirecting =
their outputs, the main code is not likely to be too long, while many =
minor changes may occur in the existing codes. My suggestion is to add =
more switch variables in all_variable file, such as =
USE_STATIC_DYK,USE_STATIC_TYK and the like. They can be grouped into a =
configuration part together with USE_STATIC_PAGES and STATIC_PAGES_PATH =
I already added. This way, I can branch the existing functions into =
either the new way (generating static pages) or the old way (generating =
dynamic pages) according to the switch variables, deciding which part of =
the mainframe is static or dynamic.

Comments are welcome.

Best regards,

Wayne=20

Re: [Linkbat-devel] next step

[James M. <lin...@ji...>]

On Tuesday 18 February 2003 14:59, Wayne wrote:
> Hello Everyone !
>
> Thanks for your comments, and they will make the codes better.
>
> To summerize, I have got several things to do to produce the next version
> of the static_page_generating tool: 1) -F option, which is supposed to
> parse all the files in certain directory; 2) Generate static DYKs (Do You
> Know);

Not yet. The code is already there to create the DYKs. So don't worry too much 
about this for now. 

> 3) Handling the glossary popups and links;
> 4) More error handling.

Both of these are very important. Getting this done means we can create a 
static content page, even if everything else is created dynamically. That is 
what is taking up the majority of the processing time.

>
> Jim, I am considering your idea of splitting the codes into two pieces.
> Since I use existing functions to generate static pages by redirecting
> their outputs, the main code is not likely to be too long, while many minor
> changes may occur in the existing codes. My suggestion is to add more
> switch variables in all_variable file, such as
> USE_STATIC_DYK,USE_STATIC_TYK and the like. They can be grouped into a
> configuration part together with USE_STATIC_PAGES and STATIC_PAGES_PATH I
> already added. This way, I can branch the existing functions into either
> the new way (generating static pages) or the old way (generating dynamic
> pages) according to the switch variables, deciding which part of the
> mainframe is static or dynamic.

Not a bad idea. What about using command line switches as well? These would 
override all_variables file. Just an idea. 

By the way, I think the "Test Your Knowledge" questions will probably always 
be dynamic. Theoretically we could create number questions pages statically 
that are then loaded at random, but is that necessary? Comments?

Regards,

jim
-- 
---------------------------------------
"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