<HTML><HEAD>
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV>> [Original Message]<BR>> From: David Spitzley <dspitzle@wash.k12.mi.us><BR>> To: <pmwiki-users@pmichaud.com><BR>> Date: 3/9/2005 4:29:37 PM<BR>> Subject: Re: [pmwiki-users] Re: Perfection and Menus (WAS: onover-bundling) . . .<BR>><BR>> Well, just in case PM is wavering on his decision to include GUIedit in<BR>> the core installation, I would argue that the GUIedit module is, if not<BR>> >needed<, then extremely useful for what has historically been the<BR>> primary feature of a Wiki: the enabling of non-techies to participate<BR>> in the creation of the wiki with a minimum of training. I think it is<BR>> entirely appropriate that it is disabled by default, <BR><BR>GUIedit should be enabled by default as pmwiki's foundation should be ease of use. <BR><BR>Of my pet peaves as a webmaster would be to simplify the ease of updates. <BR><BR>I'd like to see the config file broken up into two files. </DIV>
<UL>
<LI>Wiki_ID -- for a wiki's identity (URLs, passwords, and other similar rarely changed stuff in the updating process). </LI>
<LI>Wiki_Config -- for the various frequently configured features of the wiki. These would be set to the most commonly used settings to reduce webmaster updating overhead. </LI></UL>
<DIV>This way, one could easily update a wiki by uploading Wiki_config to the Local folder while leaving the Wiki_ID identity file untouched. There are obviously other menu driven ways one might handle this to ease overhead, but hey, one thing at a time. <BR></DIV>
<DIV>Always, Fred C</DIV></BODY></HTML>