<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Peter & Melodye Bowers wrote:
<blockquote cite="mid:79CBFFB9EA224F8594B6A31957324AFA@plb" type="cite">
<blockquote type="cite">
<pre wrap="">For example -- suppose I'm webmaster for a soccer club and want to be
able to offer team websites to the teams of the club. I create a
GenericTeam group with a couple basic pages to get them started.
Then when the 'SpeedyDemons' want a team site, all I do is go to
the WikiMaster utility, and create SpeedyDemons team site from
GenericTeam, done deal, the Speedy Demons have their team web site...
Ideally, one could perhaps even automate a variant of WikiMaster so
SpeedyDemons could sign up for their own team site, with the proper
</pre>
</blockquote>
<pre wrap=""><!---->password.
There are tools out there that can already do this ( i.e., I'm pretty sure
I've read that fox has significant template file capabilities)... Here's
how you would do it with WikiSh:
Create your templates in some (presumably protected) group. Let's say
GenericTeam.Page1 and GenericTeam.Page2. Then on GenericTeam.Admin you
would put this markup:
===(snip GenericTeam.Admin)===
{(wikish_form QUICKFORM PROCESS)}
New Group:
(:input text name=GroupName:)\\
(:input submit name=submit value=Create:)
{(wikish source {$FullName}#validate)}
(:if false:)
[[#validate]]
if test -n "${submit}"
then
if ! test -n "${GroupName}"
then
echo "ERROR: Must specify the new group name."
else
if test -f ${GroupName}.Page1 || test -f ${GroupName}.Page2
then
echo "ERROR: ${GroupName} already exists."
else
echo "Creating New Team Page...\\\n\\\n"
cp GenericTeam.Page1 GenericTeam.Page2 ${GroupName}
echo "\\\n\\\n...DONE!"
fi
fi
fi
[[#validateend]]
(:if:)
(:messages:)
===(snip)===
If you are going to let other people create the groups then you might want
to do some other validations on the group name (no disallowed characters,
etc), but this will get you the basic operation and you can fine-tune it
from there.
-Peter
</pre>
</blockquote>
Thanks for the example. However, IMHO, it's one thing to have a
cookbook recipe all set up so one just
needs to read the instructions and put in a few simple directives to
get the specific job done and another to have a generic cookbook tool
(like Fox),
perhaps with all of the necessary power, but with limited (or no)
explanations or examples of how to perform the specific task. Many
wiki-masters are too busy to dive too far into writing (simple) code
for these sorts of tasks. What is needed is a product (cookbook
recipe) packaged specifically for the task -- perhaps using Fox,
perhaps not. <br>
<br>
If my daughter's car needs a tuneup, I can point her to a box of
tools in the trunk and hand her a set of spark plugs -- the job ain't
ever going to get done. However, she can pop the hood and pour window
washing solution into the right container, fill the radiator and check
the oil -- I think, maybe, uh yeah, maybe. :) <br>
<br>
Always, Fred C<br>
</body>
</html>