Wikka Code Structure

A few days ago I had a little discussion with JsnX in TheLounge (the #wikka channel on irc.reenode.net) about "external" type programs (not part of Wikka but providing important functionality), actions, plugins... and how to organize it all better into a directory structure. I'd been thinking about the same things myself, but somehow didn't quite pick up on what JsnX was proposing (I was probably "multitasking" and doing other things while talking to JsnX on #wikka, sorry).

So, I'll now try to take it from there and give a worked example of what I had in mind (and possibly JsnX as well).


My rationale for this proposal is as follows:

So here is how I'd structure the directory (some comments included in PHP-style):




[wikka]/3rdparty/core/safehtml/			#HTML can be turned off globally

[wikka]/3rdparty/plugins/freemind/		#cannot be turned off yet but is not needed functionality
[wikka]/3rdparty/plugins/onyx-rss/		#replaces [wikka]/xml/ 
[wikka]/3rdparty/plugins/wikiedit2/		#can be turned off globally


# "overall management" actions (referring to other pages than the current one)
# page content (or referring to/changing the current page only)
[wikka]/actions/core/colour.php			#only does an include of color.php so don't have duplicated code!
[wikka]/actions/core/image.php			#and disallow dynamic image inclusion via url: not valid html

# system management
[wikka]/actions/plugins/emailpassword.php	#access control may not be desired/implemented
[wikka]/actions/plugins/usersettings.php	#access control may not be desired/implemented
# page content
[wikka]/actions/plugins/iframe.php		#now in intranet dir for security reasons: it's really an action!
# ... more actions added in version

# library files with code to be included and called

# page structure rather than content (not for actions and handlers)
[wikka]/templates/footer.php			#not an "action"!
[wikka]/templates/header.php			#not an "action"!
# page content blocks and templates


"Core" actions could be in the same registry, but with a marker that makes it impossible to deactivate or unregister them: that way the registry function could also display which "core" functions are available. A registration mechanism like this would also solve the problem of the (insecure) iframe action which is now hidden away in an intranet directory: it could be delivered with the file placed in the actions directory but unregistered in the registry.
Structure adapted now by placing header and footer into a new directory templates that better describes their purpose. In case we do move to some templating system for Wikka, we'll need a place to store the templates anyway.
Adapted for the new (proposed) structure of the library directory. The subdivision in common/actions/handlers is intended to facilitate some (future) automatic processes to find to-be-included code and to describe (in CVS) which files belong together.
The name "library" is (still) only preliminary, I'm open to better suggestions; the idea is to have a name that expresses its purpose as described here.
If we move to a 'real' template system, this may need to be revised of course (depending on that system's requirements for locating templates) but if we don't this will still be a "half-way" template solution that would make interface design for Wikka much easier.. --JW


Comments and better ideas welcome, of course.

Function names

There are no comments on this page.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki