Also, there should be a possibility to define rules triggered
during permission checking.
what do you really mean by that "rules triggered during permission
checking" ? please give an example
Rules can be attached to users or rights to perform certain actions. Rules act as an 'alias' to delegate compliance checking to a PHP function. Rules are triggered before or after compliance checking. If triggered before, the rule can cancel access. If triggered after, the rule will only perform certain actions. This concept is close to a rule system in a database (such as PostgreSQL).
For example: if downloading privilege is linked to rule_downloading, you can delegate to rule_downloading certain actions like: verify that the downloaded file does not exceed > 2 Mb, verify that the user does not exceed 10 downloads a day, increase the downloading counter, etc... This helps define custom rules easily.
It is very important to be able to display a minimal GUI for
incorporation in target applications.
you mean stuff like login page?
i dont think so, my classes have _no_ html inside and dont return no
html, i think this is up to the user to design the page etc.
everything that goes out and can be seen should be made up by the
webdesigner not given by an API, i think
so again _my classes dont produce no html output_ neither for the
login screen, nor for any other screen
Have a look at http://homepage.mac.com/ghorwood/php_lib_login/.
The class has poor group support, no privilege notion and no rule.
But it provides the very minimal features needed among which login and administration pages.
Best regards,
Jean-Michel POURE