<!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">
PMwiki is a hacker's paradise, with customization easy for hacks to
do. However, this doesn't necessarily translate into being easy for
the average point and click user. <br>
<br>
For an example of "easy" for average non-hackers, one might look to
Windows (the world's largest computer virus). There's a point and
click module in the Windows control panel to add and remove parts of
Windows that you may or may not need. An equivalent in pmwiki might be
to have a module that browses thru the cookbooks at pmwiki.org. Click
on one, and it is ftped directly to your cookbook site and the proper
code installed in your config file. Removal would remove the file and
code from config. <br>
<br>
The same would be true of skins. Windows (the worlds largest computer
virus), again provides an example of how this might work. If you right
click on the desktop and select properties, there's several point and
click options on how to configure your desktop as well as basic window
displays (color schemes for various parts of the window, font sizes,
etc), and you can save and load schemes... A pmwiki equivalent might
be to scan thru the skins at pmwiki, click on one and it would be ftped
to your skins folder and code installed in config. Removal same as
above. <br>
<br>
Even at dialup speeds, most pmwiki cookbooks and skin modules are small
enough to download or upload on the internet in a few tens of
seconds. However, it would seem to make a lot more sense to just
directly ftp code from pmwiki to a wiki site, which would take seconds
at best... <br>
<br>
This could all be done without changing much of anything of the beauty
of the pmwiki world that hacks find so 'simple' to work in. <br>
<br>
As a final comment -- with a slow but growing trend towards moving OSs
and apps online, the addition of such a system to PMwiki would seem to
go a long ways to ward defining pmwiki as a wikiOS for many users.
Particularly if installing pmwiki could be made as easy as a point and
click after being given a site name and password. <br>
<br>
<br>
<br>
Sandy wrote:
<blockquote cite="midekfcrd$74i$1@sea.gmane.org" type="cite">
<pre wrap="">writeon1 wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After spending considerable time evaluating pmwiki, I came to two
conclusions. (1) It's a great product, with add-ons that offer all the
features and flexibility I could want, and (2) the time investment in
learning to set up, use and maintain the system is more than I can
afford. (Would that I were smarter.) The idea of creating a basic
product and allowing users to add features as needed would work a lot
better if adding features was a push-button affair. I hope that
eventually the question of how to make configuring the product easier
will be made the main thrust of development for a while. I'll look in
again in a few months - I still think that of the wiki /cms systems I
have looked at PMwiki would be the best for my purposes, if it were less
demanding of the prospective administrator. Thanks,
Brendan
</pre>
</blockquote>
<pre wrap=""><!---->
We hope you do look again. I agree that the first step of customizing it
can look daunting, but most customizations are actually pretty easy to do.
Which customizations are you looking for?
Sandy
_______________________________________________
pmwiki-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a>
<a class="moz-txt-link-freetext" href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Always, Dr Fred C
<a class="moz-txt-link-abbreviated" href="mailto:drfredc@drfredc.com">drfredc@drfredc.com</a></pre>
</body>
</html>