lemonldap-ng/lemonldap-ng-manager
2015-12-16 11:37:43 +00:00
..
eg Add CGI file for the manager 2015-12-16 11:37:39 +00:00
lib/Lemonldap/NG Manage "force saving" 2015-12-15 20:49:02 +00:00
scripts Do not require perltidy 2015-12-16 11:37:33 +00:00
site Clean code 2015-12-15 21:08:30 +00:00
t Update manager tests 2015-12-16 11:37:43 +00:00
.bowerrc Set bower path 2015-07-09 17:01:30 +00:00
bower.json Update js dependency versions 2015-07-09 17:02:27 +00:00
Changes Update Changes and report trunk copyright changes into 1.2 2013-01-31 06:23:14 +00:00
KINEMATIC.md Import and adapt https://github.com/guimard/angular-lemonldap-ng-manager.git 2015-05-14 06:44:38 +00:00
Makefile.PL Replace version 2.00 by 2.0.0 2015-04-15 14:18:38 +00:00
MANIFEST Update manifest 2015-12-16 11:37:35 +00:00
META.yml Replace version 2.00 by 2.0.0 2015-04-15 14:18:38 +00:00
README Update copyrights 2015-06-18 11:00:24 +00:00
README.md Import and adapt https://github.com/guimard/angular-lemonldap-ng-manager.git 2015-05-14 06:44:38 +00:00
REST-API.md Import and adapt https://github.com/guimard/angular-lemonldap-ng-manager.git 2015-05-14 06:44:38 +00:00
TODO.md Update todo list 2015-12-15 21:08:27 +00:00

angular-lemonldap-ng-manager

This is just a POC to build an angular based manager for Lemonldap::NG.

See LemonLDAP::NG website.

Install

git clone https://github.com/guimard/angular-lemonldap-ng-manager.git
cd angular-lemonldap-ng-manager
npm install

Start servers

npm run perlserver
npm start

MVC

  • The view is managed by :
    • index.html for HTML building
    • some other html files for forms ?
    • struct.json who gives the tree position for each configuration element and requests to do
    • translate.json (which will be delivered by a CGI to choose current language)
  • The controller is splitted in 2 pieces :
    • client side in js/manager.js, based on ANgularJS, it provides the link between the DOM and the CGI. It manages:
      • downloads of JSON datas
      • translations
      • form display depending on data types
    • server side, based on PSGI, it provides the link between network and configuration. It will be able to respond to 3 types of rest queries:
      • key values
      • hash keys for this type of nodes
      • hash content
  • The model (datas) is:
    • the current configuration
    • the modified datas (client side only or both to be able to notify changes to other administrators ?)