Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:screenshot [2009/12/03 16:29]
Benjamin Renard
en:screenshot [2009/12/16 11:38] (current)
Julien Danjou
Line 1: Line 1:
-**LdapSaisie** uses [[http://​www.smarty.net/​|Smarty]] template ​core, which makes application design easy to manipulate. The following ​screenshots ​show the default theme.+**LdapSaisie** uses [[http://​www.smarty.net/​|Smarty]] template ​system, which makes application design easy to manipulate. The following ​screen-shots ​show the default theme.
  
 ====== Connection ====== ====== Connection ======
 {{:​login.jpg?​400 }} {{:​login.jpg?​400 }}
-**LdapSaisie** is able to connect to several directories,​ allowing to deal with several ways to connect to them. It's possible to choose ​dynamicaly, if necessary, the server and the connection level.+**LdapSaisie** is able to connect to several directories,​ allowing to deal with several ways to connect to them. It's possible to choose ​dynamically, if necessary, the server and the connection level.
  
- It is possible to authentify to LdapSaisie ​entering ​email, ​username, or any other user attribute which has been previously configured with a search filter. This way, it is also able to specificaly ​deactivate user connexion according to some attributes. For example, a boolean attribute or a revocation account date could be consulted to check user authentication rights.+A user can log-in into LdapSaisie ​by using any authentication information: ​email, ​user name, or any other user attribute which has been previously configured with a search filter. This way, it is also able to specifically ​deactivate user connexion according to some attributes. For example, a boolean attribute or a revocation account date could be consulted to check user authentication rights.
  
 ====== Listing and searching objects ====== ====== Listing and searching objects ======
 {{:​viewlist.jpg?​400 }} {{:​viewlist.jpg?​400 }}
-Based upon objects configuration,​ searches can be done concurrently on several attributes, and can be approximative (using ~= Ldap operator).+Based upon objects configuration,​ searches can be done concurrently on several attributes, and can be approximative (using ~= LDAP operator).
  
 Findings are paginated and can be sorted. Objects headings can be easily manually set and can be composed of several attributes. Findings are paginated and can be sorted. Objects headings can be easily manually set and can be composed of several attributes.
Line 15: Line 15:
 ====== Displaying an object ====== ====== Displaying an object ======
 {{:​view.jpg?​400 }} {{:​view.jpg?​400 }}
-Based on the configuration of the objects and the attributes, the object view is  +Based on the configuration of the objects and the attributes, the object view is easily organizable. Each attribute is displayed according with its type and it's possible to group them by tab. 
-Basée sur la configuration des objets et de leurs attributs, la vue d'un objet est easily organizable. Each attribute is displayed according with its type and it's possible to group them by tab. +
  
-The relations between objects (for instance which groups a user is a member) are displayed and editable from the view of the object. It'​s ​ +The relations between objects (for instance which groups a user is a member) are displayed and editable from the view of the object. It's thus possible for example to view and modify user groups ​with simple ​**LSselect** ​window. [[screenshoot#​lsselect|More details]]
-Les relations entre les objets (par exemple les groupes dont un utilisateur est membre) sont affichées et modifiables à partir de la vue d'un objet. It is thus possible for example ​ to view and modify user groups ​so simple through ​window ​**LSselect**. [[screenshoot#​lsselect|More details]]+
  
 ====== Modifying an object ====== ====== Modifying an object ======
Line 27: Line 25:
 Each field is an abstracted object **LSformElement** managing features of the field itself. This object has already been declined numerous times to handle the peculiarities of form fields. Each field is an abstracted object **LSformElement** managing features of the field itself. This object has already been declined numerous times to handle the peculiarities of form fields.
  
-Thus, a //​password//​ field doea have a generating feature when a //email// field does have the feature of sending mail from the interface.+Thus, a //​password//​ field does have a generating feature when a //email// field does have the feature of sending mail from the interface.
  
 One **LSformElement** could be extended, modified and created easily to enable management of all types of fields by abstracting the syntax and the complexity of LDAP attribute values. One **LSformElement** could be extended, modified and created easily to enable management of all types of fields by abstracting the syntax and the complexity of LDAP attribute values.