Zikula Community

Language system enhancement (lead: Bernd Plagge)

• Implementation of GetText? across core and VAs
• make permission system more intuitive, e.g. with drag and drop, maybe ACLs
• Some of the responsibility for this must lie with module developers - DBUtil should just provide start and end transation calls.

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 Zikula installer.
• Ability to clear per-module caches manually in pnRender
  
  Deletions:
  

  Language system enhancement (lead: ?)

• review and evaluate language technologies and systems used by other popular apps
• apply to all existing modules (system and value addons)
• make permission system even more intuitive, e.g. with drag and drop, maybe ACLs
• Note (Robert): The basic code for this is already in index.php. It just needs some testing and possibly refinement.
  
  

  ---

  edited 2007-10-06 20:12:09 by markwest added user side css review
  
  
  
  Additions:
  * Create a set of CSS classes to markup up standard user side items
  
  

  ---

  edited 2007-10-06 19:38:36 by rgasch
  
  
  
  Additions:
  

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

• Note (Robert): The basic code for this is already in index.php. It just needs some testing and possibly refinement.

Mark & Robert

• Note: this should be hooked into DBUtil
  
  Deletions:
  

  Usability review (lead: ?)

Mark

• 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...

Others

• Use Ajax to trigger a session keep-alive for editing longer text areas
  
  Deletions:
  * 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...
  
  

  ---

  edited 2007-07-31 16:42:44 by Guite added idea for hook enhancement
  
  
  
  Additions:
  

  Axel

• 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...
  
  Deletions:
  
  
  

  ---

  edited 2007-07-31 12:15:33 by Landseer permissions
  
  
  
  Additions:
  

  Permission system enhancement (lead: Frank)

• make permission system even more intuitive, e.g. with drag and drop, maybe ACLs
• make it possible to define permissions from a within a module
  
  Deletions:
  * more intuitive permission system (create permission using drag&drop and dropdowns for options), there are some useful implementations we can look at, eg. ACLs.
  
  

  ---

  edited 2007-07-24 12:19:34 by Landseer
  
  
  
  Additions:
  * Make framework able to exist outside of webroot allowing users to only have their modules/themes and config directories present.

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?.

Language system enhancement (lead: ?)

• review and evaluate language technologies and systems used by other popular apps
• UTF-8
• 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")
• 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
  
  Deletions:
  * create PN compatability library (all public PN* functions aliased to new core)

Language system enahancement (lead: ?)

• review and evaluate language technologies and systems used by
• other popular apps
• category based permissions would be nice ("allow group X to edit allentries which are in category A while group Y can edit photoshare items in category A only")
• Usage of SQL transactions to avoid problems with aborted functions leaving inconsistent stuff in the database and making PN morebulletproof in case of many users working in the same "area" (or withthe same tables) at the same time
  
  

  ---

  edited 2007-07-11 18:29:35 by drak
  
  
  
  Additions:
  * Use Exceptions!
• 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.
  
  Deletions:
  * Use Exceptions!

Unordered list

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?.org)
• remove any PHP 4 hacks
• create PN compatability 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 enahancement (lead: ?)

• review and evaluate language technologies and systems used by
• other popular apps
• development new core language architecture
• apply to all existing modules (system and value addons)

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: ?)

• more intuitive permission system (create permission using drag&drop and dropdowns for options), there are some useful implementations we can look at, eg. ACLs.
• category based permissions would be nice ("allow group X to edit allentries which are in category A while group Y can edit photoshare items in category A only")
• Usage of SQL transactions to avoid problems with aborted functions leaving inconsistent stuff in the database and making PN morebulletproof in case of many users working in the same "area" (or withthe same tables) at the same time
  
  Deletions:
  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?.org)
• remove any PHP 4 hacks
• create PN compatability library (all public PN* functions aliased to new core)
• apply proper patterns (singletons etc.) to improve performance across core
• apply E_STRICT coding standards
• Notes: create a branch for this work

1. review and evaluate language technologies and systems used by
2. other popular apps
3. development new core language architecture
4. apply to all existing modules (system and value addons)

1. review existing modules and propose new or enhanced functionality
2. enhance modules based on review and existing FR tracker
3. extend modules to utlise new core

1. review existing modules and propose new or enhanced functionality
2. enhance modules based on review and existing FR tracker
3. extend modules to utlise new core

1. move PN* functions so that project rename can happen smoothly
2. create a PN compat. library
3. enhance code for PHP 5 only (gophp5?.org)
4. remove any PHP 4 hacks
5. create PN compatability library (all public PN* functions aliased to new core)
6. apply proper patterns (singletons etc.) to improve performance across core
7. apply E_STRICT coding standards
8. Notes: create a branch for this work

1. review and evaluate language technologies and systems used by
2. other popular apps
3. development new core language architecture
4. apply to all existing modules (system and value addons)

1. review existing modules and propose new or enhanced functionality
2. enhance modules based on review and existing FR tracker
3. extend modules to utlise new core

1. review existing modules and propose new or enhanced functionality
2. enhance modules based on review and existing FR tracker
3. extend modules to utlise new core

Drak

SantaClaus?