(:Summary:Contains the 'action' links (like Browse, Edit, History, etc.), placed at the top of the page, see site page actions:) (:comment This page can be somewhat complex to figure out the first time you see it. Its contents are documented at PmWiki.SitePageActions if you need help. :) * View * Edit * History * Print

 (:comment delete if and ifend to enable backlinks:)

* Backlinks

(:Summary: PmWiki group header. Includes styles and trail.:) (:comment please leave the multiple style definitions concatenated as a single line. Linebreaks do appear in the output when the wiki is configured with linebreaks enabled -- thanks!:) (:comment included in PmWiki localisation headers and footers :)


< PmWiki philosophy | Documentation Index | Release notes >

(:nl:)(:Summary:Some of the features and notes about PmWiki's design decisions:)

Here are some of the features and notes about PmWiki's design decisions. Many of these derive directly from the PmWiki Philosophy and lots of discussion on the mailing lists.

* PmWiki:Flat File Advantages - why PmWiki uses flat files to store pages instead of an SQL database * PmWiki:Hierarchical Groups - why PmWiki doesn't support nested groups * PmWiki:Page Locking - how PmWiki works without locking pages (see also simultaneous edits) * PmWiki:Page File Format - the format of PmWiki's page files * PmWiki:Search Improvements - why PmWiki has a native search engine * PmWiki:File Permissions - some information about PmWiki's file permission settings * PmWiki:Wiki Group Motivation - why WikiGroups * PmWiki:WYSIWYG - why not WYSIWYG.


Q: Why doesn't PmWiki use hierarchical / nested groups? A: It essentially comes down to figuring out how to handle page links between nested groups; if someone can figure out an obvious, intuitive way for authors to do that, then nested groups become plausible. See Design Notes and PmWiki:Hierarchical Groups.

Q: Why don't PmWiki's scripts have a closing ?> tag? A: All of PmWiki's scripts now omit the closing ?> tag. The tag is not required, and it avoids problems with unnoticed spaces or blank lines at the end of the file. Also, some file transfer protocols may change the newline character(s) in the file, which can also cause problems. See also the Instruction separation page in the PHP manual.

Q: Does PmWiki support WYSIWYG editing (or something like the FCKEditor)? A: Short answer: PmWiki provides GUI buttons in a toolbar for common markups, but otherwise does not have WYSIWYG editing. For the reasons why, see PmWiki:WYSIWYG.

Categories: PmWiki Developer

(:nl:)(:Summary:Trail and talk page links:) (:comment included in PmWiki localisation headers and footers :)


<<? >>bgcolor=#ffe border-top="1px solid black" font-size=.8em<< This page may have a more recent version on pmwiki.org: PmWiki:DesignNotes, and a talk page: PmWiki:DesignNotes-Talk. >><<

Design by N.Design Studio, adapted by solidGone.org and IDUX
Powered by pmwiki-2.2.86