-
this release fixes the name of the auth-cookie, an escaping problem with js_translation_strings and cross-browser support in the gallery module. it introduces translations for thickbox, new filters for json and yaml, bound-method for db-models, new if-statements in templates including shortcuts for them ( ==, !=, <, > etc ). see changelog for more.
by the way i've added a note on the...
2007-12-22 18:52:11 UTC in aurora framework
-
ordering elements by column+direction is missing.
2007-09-11 16:00:20 UTC in aurora framework
-
uploaded into svn repos.
2007-09-10 21:24:22 UTC in aurora framework
-
it should be possible to restrict certain urls for use only with certain header-entries. for example only when the user-client is a real gecko browser or when the client should be a xmlhttprequest with special headers send by.
2007-09-10 21:22:24 UTC in aurora framework
-
also implement hook-support.
2007-09-10 14:43:41 UTC in aurora framework
-
it should be possible to load lng-vars from an array or array-object. this could be handy if one wants to load texts from a database.
2007-09-10 14:33:41 UTC in aurora framework
-
as for now we only have foreign keys and many2many connections. but for complex situations we should be able to describe a complete path to specific field.
it's still unclear how we could implement this properly..
what about this?
class test_model
{
$field = array ( path, array (
table_b => left, table_b => right,
table_c => left, table_c => right,
table_d => left...
2007-08-26 20:13:10 UTC in aurora framework
-
after the simple caching-mechanism is implemented we should apply some kind of validation for template-variables. these should be saved as meta-data by the file-cache and could be checked when a template-block is needed. it should also be possible to exclude blocks for caching. ( for ex. a block which displays the current time would be useless to cache.. algo possible?! )
2007-08-26 18:43:49 UTC in aurora framework
-
simple template-caching should cache a compiled template-block for an estimated time. nothing more. this should be fine if one have static pages which don't have to be checked for changes anytime soon..
but how could i implement this in the template-language?.
2007-08-26 18:39:08 UTC in aurora framework
-
as for now we only have mem-caching. but we still need persistant file-caching. a file-cache should have a lifespan and some meta-data on which we could apply some kind of validation.
i'm having template-caching in my mind where we only have to recompile a template-block if it's variables have changed.
2007-08-26 18:29:22 UTC in aurora framework
