Documentation Wiki

dot9

Idea/Lists

One important requirement is someone to take the lead in the language
system project - any volunteers?

Refactor core so that object library *is* core (lead: Mark)

• move pn* functions so that project rename can happen smoothly
• create a PN compat. library
• enhance code for php 5 only (GoPHP5∞)
• remove any php 4 hacks
• create PN compatibility library (all public pn* functions aliased to new core)
• apply proper patterns (singletons etc.) to improve performance across core
• apply E_STRICT coding standards

Language system enhancement (lead: Bernd Plagge)

• Implementation of GetText? across core and VAs
• UTF-8
• development new core language architecture

Permission system enhancement (lead: Frank)

• make permission system more intuitive, e.g. with drag and drop, maybe ACLs
• make it possible to define permissions from a within a module
• category based permissions would be nice ("allow group X to edit all entries which are in category A while group Y can edit photoshare items in category A only")

Enhance system modules (lead: ?)

• review existing modules and propose new or enhanced functionality
• enhance modules based on review and existing FR tracker
• extend modules to utlise new core

Enhance ValueAddons (lead: ?)

• review existing modules and propose new or enhanced functionality
• enhance modules based on review and existing FR tracker
• extend modules to utlise new core

Usability review (lead: Robert (???))

• Usage of SQL transactions to avoid problems with aborted functions leaving inconsistent stuff in the database and making PN more bulletproof in case of many users working in the same "area" (or with the same tables) at the same time
• Some of the responsibility for this must lie with module developers - DBUtil should just provide start and end transation calls.

Unordered list

• Use Exceptions!

Mark & Robert

• Implement a standard caching engine for internal caching so that we can use either internal memory or external cachng systems (e.g. memcached).
• Note: this should be hooked into DBUtil

Drak

• Introduce another module type to allow use of methods, will be module type 4
• Make framework able to exist outside of webroot allowing users to only have their modules/themes and config directories present.
• Create a set of css classes to markup up standard user side items

Frank

• We need to define a structure for documentation, eg. like eisfair.org does. This project compiles all sub-project documentation into one big doc file using a defined structure. This xml-based structure can be used for pdf, online docs, etc.pp. This should be a minimum requirement for projects being hosted in EasyDist?.

Axel

• idea: provide module permission schemas within extrainfo arrays, so that hooks can perform permission checks based on a particular context
• the further development of the hook mechanism is a very interesting topic. At the moment it works as a simple observer implementation, but this will not be sufficient for complex integrations. Therefore more pattern like proxies and delegates become necessary to integrate a messaging system. This way modules become services. This also relates a SOAP layer in the next term...

Simon

• Review structure - could a module like content replace the standard 1-module-per-page-with-blocks approach we have now?
• Exceptions and Logging
• Enhance modules module for interaction with Extensions database
• Unit Testing Framework (phpUnit?)
• Add first time configuration wizard to PostNuke installer.
• Ability to clear per-module caches manually in pnRender

Others

• Use ajax to trigger a session keep-alive for editing longer text areas