[pmwiki-users] Suggestion for wiki calendar

[John Rankin]

On Friday, 20 May 2005 11:47 PM, Joachim Durchholz <jo at durchholz.org> wrote:
>malexism (f) wrote:
>> A cookbook witch need another cookbook is not a good idea,
>imho.
>
>There's nothing wrong with such dependencies in general. If two recipes 
>share code, it's a good idea to move that shared code to a common base 
>recipe.
>
>Of course, calling up a recipe simply just because you need a single 
>feature of it, the rest being unnecessary ballast - that's not a good 
>idea. (I already cursed those recipes that need MarkupExtensions, for 
>example - I don't want MarkupExtensions, too many features and too 
>handwavy documentation for my taste.)

The 'too many features' issue is hard to deal with, because different
recipes take advantage of different feature subsets. My experience
from PmWiki 1 was that recipe interdepencencies were a nightmare
for me to keep straight. But I'll think about what can be done.
I already find that some code is duplicated across multiple recipes
to reduce interdependencies, and this causes problems, as you can 
imagine.

The documentation issue: perhaps I should scrap the entire page
that has evolved and start again. And perhaps re-think the whole 
architecture.


-- 
JR
--
John Rankin