<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Trevor<br>I think you make a good point, except that the examples you gave tend to be about personal preferences rather than "rights" or "wrongs", so:<br><br>* sandbox a bit<br>* make a decision that suits you<br>* move on, and live with your decision<br><br>In some cases, if you change your mind down the track, there will be an acceptable workaround which may be a recipe created by someone whose thinking went the same track as yours.<br><br>You are going to find that folks are continually "inventing better mousetraps" which will make your initial decisions seem sub-optimal, and this will set up a similar conundrum...you, and the world, are in continual flux...<br><br>Warm regards<br><br><div><font color="#660099" face="Lucida Handwriting, Cursive" size="4"><strong><em>Ray Storey</em></strong></font></div>
<div>mob: +66 8 9020 6237</div>
<div>Homepage: <a href="http://www.all-my-world.com">http://www.all-my-world.com</a> [a sort of porridge of pmwiki, tiddlywiki, and a couple of other things]<br></div><br><br><br><br>> Date: Fri, 28 Aug 2009 14:55:18 +0200<br>> From: twylite@crypt.co.za<br>> To: raystorey@hotmail.com<br>> CC: pmwiki-users@pmichaud.com<br>> Subject: Re: [pmwiki-users] Recommended recipes?<br>> <br>> Thanks Ray,<br>> > In my experience pmwiki lends itself well to starting simple, <br>> > sandboxing, adding functionality as you recognise the need.<br>> ><br>> > Unless your needs are very simple, or your mind is very disciplined, <br>> > you ain't going to get it right first time...and that is not a crime.<br>> This is pretty much what I am planning to do, but I realised quite early <br>> in the process that there are a number of decisions that can be quite <br>> costly (time, effort) if I don't get them right from the start:<br>> <br>> * Changing the Wiki markup to <br>> http://www.pmwiki.org/wiki/Cookbook/Creole or <br>> http://www.pmwiki.org/wiki/Cookbook/Markdown is a decision that can only <br>> be taken before any content is created.<br>> <br>> * Changing the linking scheme of the Wiki to an <br>> http://www.pmwiki.org/wiki/Cookbook/AlternateNamingScheme or even to <br>> disable CamelCaseLinks needs to be done from the start. CamelCaseLinks <br>> could be enabled later, but not disabled without a significant <br>> probability of destroying existing links.<br>> <br>> * PageStore changes such as <br>> http://www.pmwiki.org/wiki/Cookbook/PerGroupSubDirectories can be <br>> awkward to introduce once many pages exist. Changing where uploads are <br>> stored as in http://www.pmwiki.org/wiki/Cookbook/UploadPlus would be <br>> extremely difficult to automate.<br>> <br>> * Getting rid of Main (http://www.pmwiki.org/wiki/Cookbook/GetRidOfMain) <br>> or changing the group home page name <br>> (http://www.pmwiki.org/wiki/Cookbook/GroupHomePageChange) would involve <br>> renaming pages and altering links, and may not be straightforward <br>> depending on the size of the Wiki. For a public Wiki this would also <br>> destroy URLs that may have been bookmarked.<br>> <br>> * If I introduce say <br>> http://www.pmwiki.org/wiki/Cookbook/PageTableOfContents to create ToCs, <br>> but later find that it is buggy or doesn't interact well with some <br>> common/useful recipes, then I may need to change the markup on many <br>> pages in order to migrate to another ToC recipe.<br>> <br>> * The previous point is generally true for any recipe/extension that <br>> adds markup and which graduates from the sandbox -- removing such <br>> extensions is non-trivial, so you want to avoid installing one where a <br>> more suitable alternative exists, suggesting a need to investigate <br>> alternatives.<br>> <br>> I try to keep my approach disciplined, even if my mind isn't ;)<br>> <br>> Regards,<br>> Trevor<br>> <br>> <br>> <br>> <br>> <br><br /><hr />Check the daily blob for the latest on what's happening around the web <a href='http://windowslive.ninemsn.com.au/blog.aspx' target='_new'>What goes online, stays online</a></body>
</html>