[Envolution-devel] Utility Modules

[Andrei K. <ak...@ho...>]

Since we finally got into code development discussions here, this would
be a good time to actually start working on all the exciting things we
would like to see in envo.

I have compiled a list of things I would like to see as utility modules
or API extensions (we should make a decision on naming, btw). We can
share our ideas in this thread, and I will recompile the list to
incorporate ideas at least once a week. When we think we got the basics
down, I will post it on the forums to get even more feedback.

So, here is the first iteration of Utility Modules Wish List :)

***Content Utility Module:

Global content registration. Whenever a piece of content is created by
any module, it is registered with Content Utility Module. Unique ID
assigned by Content Utility Module is a universal identifier for
everything created by modules. Permissions, category assignment,
comments and ratings assignments as well as notifications can be tied to
this unique global ID.

Required Components:

-unique content id from the module content belongs to.

-name to be displayed for associated content id

-module name (or module ID) (to associate content to the right module)

-language 


***Category Utility Module

Global categories tree for content that was meant for browsing based
access.

Required Components:

-category id to uniquely identify content within categories tree.

-parent id for categories tree structure

-unique content id from Content Utility Module to point to actual
content.

-type to identify if a given category id content pointer or another
category.

-language

I am currently working on these two modules. Actually, they are combined
into one, but I am planning to separate them into two separate entities.

The following Utility Modules are just concepts :). I don't have any
code for them yet.

***Comments Utility Module

Comments facility that can be assigned to any content id.

Required Components:

Ability to do display threaded, nested and flat styles (probably through
parent id and group id)


***Ratings Utility Module

Ability to rate any piece of content.

Required Components:

-ability to compute composite rating.

-ability to have either scale or good/bad rating for any content type

-ability to display number of good and number of bad votes

(The more I think about it, it looks to me that having two different
ratings utility modules might be better)

***Private Messaging Utility Module

Should at least provide the same functionality current PM module
provides.

***Notification Utility Module

Can let you associate user ids with content ids and raise alerts if a
given action has been performed (like content being assigned to a given
category, or content modification or deletion).

***Email Utility Module

Should handle email messaging for envo. Can be invoked whenever
specified alert is triggered by, for example, Notification Utility
Module.

***XML-RPC Utility Module

Should provide interface (abstraction layer) for functions (methods)
designed for remote access (or allowed to be accessed remotely)

***SOAP Utility Module

Same as XML-RPC but for SOAP protocol

***Backup Utility Module

A tool to backup not only entire database, but separate tables (per
module for example) and use Email Utility Module to mail a copy to site
admin.

***RSS Utility Module

Should provide an easy tool to convert any content into an XML file
suitable for RSS feed.


That is all I can think of for now :). Feel free to through in
additional Utility Module ideas. The more the better :). When you reply
with suggestions, please use <name> Utility Module at the beginning of
your comment. Will make my life a lot easier.

Best Regards,

ak