| Age | Commit message (Collapse) | Author |
|
classes which extend the User_Definition and Group_Definition classes defined in the Identity API
|
|
for event notifications. This drove out some issues in the user::users and
group::groups API backend.
|
|
Identity/Gallery::list_groups
|
|
|
|
Create an Identity library that defines the interface the Gallery3 expects
Move the user and group helpers into the gallery module to provide the familiar
interface into the Identity library.
Create a Gallery Identity back-end that is supplied by the user module.
The vision here is that all user and group code that is gallery or ui specific
is contained within the core product. Anything that relates to manipulating a
user or group is contained in the back end code that can be replaced.
|
|
consistency. No 3rd party libs in "libraries", at least for now.
|
|
html for the login form is retrieve via an ajax call when the user clicks on login. Can't login with a valid id yet, but you certainly get error messages when things are wrong :-)
|
|
login link in the header wil open up a login box like the mockup
|
|
file_structure_test
|
|
mechanism as g1 and g2 to facilitate a migration.
|
|
|
|
based on the contents of the user/config/user.php file. And load that driver based on the User_Driver interface. There is a default User_Gallery_Driver class that will provide the actual interface implementation. Replacing this driver will allow a completely different user and authentication implementation to be used... hopefully will reduce issues with embedding and other user management systems. Removed from unit tests so they will still run.
|