Re: Feature suggestion: picfolder variable

["Gunnar Hjalmarsson" <gunnar at ringlink.org>]

Thanks for the suggestion, Richard! Below follow my first comments.
The suggestion presupposes
1) that the ring navigation panel includes graphics,
2) that a ring member is required to download one or more
   pictures at their own site, and
3) that the member stores the ring graphics in some other
   folder than the folder where the HTML file with the ring
   code is stored.
The principal point with Richard's suggestion is that there would never be
a need for the ring members to edit the customized code, but they would be
able to just copy and paste.
Personally I'm not sure this is a big issue. I have a feeling that "poor
html users" tend not to make use of separate folders for graphics, but
simply store the graphics files in the same folders as the related HTML
files. Those who store graphics separately are probably well aware of the
need to edit the references accordingly. Also, some rings don't make use of
graphics, and some ringmasters allow their members to reference graphics
stored at the ring site.
So, I guess I'm trying to say that it's an interesting idea, but low
priority IMO.
Richard Bozman wrote:
> This can also be expanded into the check sites to prove
> existance of graphic files in the correct place.
Agree. But please note that there will still always be a need for manually
checking member sites to ensure that all the membership requirements are
met.
> This can be expanded into the ring appearance also, a place to
> post the graphics names into variables $leftpic $rightpic etc.
Don't see the need for this. Why not simply require that the original names
are used?
/ Gunnar