In this respect, there _are_ issues in the documentation. For example AuthUser <-> UserAuth, many people asked for clarification in pmwiki.org. Along the same issue is there are several interpretations and uses for "templates" in PMWiki. "XL templates" are for converting pmcommands into different languages (seems "language conversion list" might be a better term), there's autoloading premade template pages into new pages (my enduser view of what a template is), then there's skin templates (which might be better termed "skin parameter list"), etc. It also doesn't help clarity when one searches the pmwiki documentation for something like "template", you end up with a laundry list of between 100 or 200 files, in alphabetical order, starting with "AccessKeys" that has little, if anything, to do with templates. By the time one finally stumbles on the template info you might want, your brain may be so muddled from reviewing who knows how many other pages that weren't at all about what you were looking for, that you don't recognize you've finally found what your are looking for. Much of this is related to how PMWiki is generally designed from the code outward to user, rather than user documentation inwards to the code. Programmers, when given the latitude to do work from the code outwards, will frequently muddle up end user documentation to the point of creating more documentation confusion than clarity. The various uses of templates, as well as UserAuth/AuthUser, seem to be examples of this at work. There's undoubtably other examples. That said, there's benefits to the freedom of an open source colaborative effort. It's this feature that in many ways makes the PMwiki as useful as it is, once you figure out how to make it work the way you want. -- Always, Dr Fred C [EMAIL PROTECTED] |
_______________________________________________ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
