<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid1494019416.20070124194343@softflow.co.uk"
type="cite">
<pre wrap="">And when is a bundle a Bundle? When does a recipe stops being a
recipe and becomes a Bundle? What degree of complexity or combination
of other recipes is required to warrant it be named a Bundle?
</pre>
</blockquote>
Perhaps these definitions need to be better defined to clarify things.
As I see it <br>
<ul>
<li>A recipe is a collection of tools and structures that may or may
not be used to create something in a wiki. <br>
</li>
<ul>
<li>Recipes generally do not self activate but require some
additional programming instructions to be put to use.</li>
</ul>
<ul>
<li>Example -- PMCalendar. It can be provided in the cookbook, but
the code just sits there unless implemented by a proper set of
programming instructions.<br>
</li>
</ul>
<li>A bundle is a general purpose construct using various tools and
structures (recipes) to achieve a particular purpose or application. <br>
</li>
<ul>
<li>When a bundle is installed, one should generally end up with a
default (but customizable) construct of some sort. <br>
</li>
<li>Examples (real and possible) -- <br>
</li>
<ul>
<li>WikiPublisher -- It's a bundle of wiki recipes that when
installed construct the wiki site in a format so pages can be printed
as pdf files. <br>
</li>
<ul>
<li>WP includes several customized (individually available)
recipes that must interact with each other to properly work. It is
problematic to the WP Bundle to have these recipes installed
independently. <br>
</li>
</ul>
<li>MyCalendar -- (Possible). This might be a bundle of the
PMCalendar recipe and some default Calendar pages that when unzipped
and uploaded would end up with a fully operation Main/Calendar page at
a PMWiki Site. There would be no additional programming required to
get it working.<br>
</li>
<li>MyForum -- (Possible). A bundle that when unzipped and
uploaded would create a fully operational Main/Forum page at a PMWiki
Site. No additional programming would be required to get it working. <br>
</li>
<li>MyOnlineStore -- (Possible) A bundle that might unzip and
upload to a wiki site to create a Main/OnlineStore with a couple sample
items, Cart, and CheckOut to start with. No additional programming
required to get it up and going. <br>
</li>
<li>Wiki Site Bundles (Possible) -- distinguished from the
Bundles above by being self contained web sites.<br>
</li>
<ul>
<li>WikiForumSite -- When unzipped, and properly uploaded, this
bundle might create a wiki website with a forum as it's centerpiece,
perhaps with a couple general purpose pages already intact (ForumPage,
ForumRules, ForumPurpose, SignUpPage, ContactUs, DisclaimerPage, LogIn,
etc). <br>
</li>
<li>WikiStoreSite -- When unzipped and uploaded, it creates a
simple online store with several default pages ready for use. <br>
</li>
<li>WikiClubSite -- When unzipped, and uploaded, it would
create a simple website for a Club to use that would have pages already
created for the typical Club website. <br>
</li>
<ul>
<li>Such a bundle might include several standard Club site
pages like Calendar, Contacts, Who are we, LogIn, etc that would be
ready for customization. <br>
</li>
</ul>
</ul>
</ul>
</ul>
</ul>
-------<br>
IMHO, while PMWiki offers a powerful set of highly customizable tools
for website creation and maintenance, one of PMWiki's general
weaknesses is there is a modestly steep (but frequently unnecessary)
learning curve to getting many common wiki sites and functions up and
going. WikiBundles, as defined above, if made available might simplify
the startup and implementation task for many users with common site
needs. <br>
<br>
In other words, in PMWiki, there's lots of reinventing the wheel going
on when offering some replication of generic working examples would
seem more effective use of many people's time. <br>
<br>
</body>
</html>