This is an overview of the main functionality currently in development for bitweaver. The meaning of the columns in the table below is as follows:
Functionality: a (very) short description of the functionality in development.
ETA: the current estimate by the developer(s) of the expected completion date of the previously specified functionality.
Priority: this indicates how important the previously specified functionality is to make it into ReleaseTwo (R2) according to the developers on a scale of 1 to 5.
Who: the developer(s) currently working on the previously specified functionality.
DB abstraction layer is now interchangable to use different layers. PEAR::DB has been added, wtih the option of adding PDO in the future. See /articles/6 for details
Each individual piece of content can have indvidual preferences of any name/value pair. This is just like the old users_preferences table, that in fact was generalized, and users (which are content) now store their values in the general content_preferences table.
Parsed content caching
All parsed content can be cached by defining a maximum cache time in the liberty admin screen