RE: Additional Commands

["Daniel Gwozdz" <smage@together.net>]

FYI - better to leave your links pointing to next5.pl and prev5.pl as I
mentioned before.  That way , when they're implimented, you won't have to have
everyone change their ring code.
Daniel Gwozdz
The Water-Cooled Volkswagen Ring - http://www.wcvw.org
> James,
>
> If I understand you right, what you suggest would not need any
> adjustments in the program at all. All you would need to do is to link
> from the image's "next 5" and "prev 5" to list.pl.
>
> But it sure wouldn't be very useful. In my opinion, the list page in
> Ringlink makes both "next 5" and "prev 5" redundant. In my own (still)
> WR ring I have an imagemap with "next 5", but I intend to change the
> image and remove the "next 5" option before I migrate.
>
> However, creating "next 5" and "prev 5" options is on the Ringlink
> project list, since it was requested by a few ringmasters. I haven't
> figured out yet how to combine them with the "list" option in a way that
> makes sense. Maybe I shouldn't bother, maybe some ringmasters simply
> prefer to use "next 5" and "prev 5" _instead of_ "list".
>
> / Gunnar
>
> "James S. Huggins (dot com)" wrote:
> >
> > An idea.
> >
> > Some of the pages that might come with me to the new Ringlink system are
> > using Image Maps that have functions not yet implemented (e.g.,
> Next 5, Prev
> > 5).
> >
> > It might be a while before we get these.
> >
> > The issue will be changing the IMAGE. The IMAGE has those functions.
> >
> > So, in the interim, how about making the functions that don't yet work do
> > the same thing as those that do.
> >
> > For example, Next5 could be the same as List. So could Prev5. Not perfect,
> > but it saves the image in the short term.
> >
> > James S. Huggins