Here are some of the features and notes about SeWiki's design decisions. Many of these derive directly from the SeWiki Philosophy? and lots of discussion on the mailing lists.
- SeWiki:Flat File Advantages - why SeWiki uses flat files to store pages instead of an SQL database
- SeWiki:Hierarchical Groups - why SeWiki doesn't support nested groups
- SeWiki:Page Locking - how SeWiki works without locking pages (see also simultaneous edits)
- SeWiki:Page File Format - the format of SeWiki's page files
- SeWiki:Search Improvements - why SeWiki has a native search engine
- SeWiki:File Permissions - some information about SeWiki's file permission settings
- SeWiki:Wiki Group Motivation - why WikiGroups
- SeWiki:WYSIWYG - why not WYSIWYG.
Why doesn't SeWiki use hierarchical / nested groups?
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 SeWiki:Hierarchical Groups.
Why don't SeWiki's scripts have a closing ?> tag?
All of SeWiki'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.
Does SeWiki support WYSIWYG editing (or something like the FCKEditor)?
Short answer: SeWiki provides GUI buttons in a toolbar for common markups, but otherwise does not have WYSIWYG editing. For the reasons why, see SeWiki:WYSIWYG. See also Cookbook:Worse and Cookbook:PmSyntax.
Categories: SeWiki Developer
This page may have a more recent version on wiki.solutionerp.co: SeWiki:DesignNotes, and a talk page: SeWiki:DesignNotes-Talk.