Controller code screen :   - Changed the link to source code for this format : source : /home/testp1/Dev/symfony_demo/src/AppBundle/Controller/BlogController.php, class : AppBundle\Controller\BlogController, method : indexAction, page : 41 : code source and class can then be copy/pasted in phpStorm on ubuntu where the standard url based integration lead to (too) complex congiguration in ubuntu.   - Added the links : "Edit doc" and "Save doc as xml" with an alert of success or error : this links integrate the Axel xml editor library (http://ssire.github.io/axel/).   TODO :     - mean term : template is default (Page), add managment of customer templates configuration and "symfony framework feature specific" elements (same with apache and postresgl features) : for example add dynamic template extensions or full generations, based on the project or vendor bundle controller names, doctrine entities / repositories names and so on...     - short term : check axel capability of templates with html links in text.     - short term (level 1) and mean term (level 2) : manage templates and code documents in postgresql database : two (non mutualy exclusive) level of granularity : 1 : store xml documents "as is" in a db text field (so querying the xml with other db field is not possible yet full text postgres search in the xml documents are possible, and update is only possible at document level with the editor); 2 : store and manage xml document elements in db text fields, so everything is possible yet performance becomes an issue.     - short term : refactor with asset component the coding of url/routes of axel's js asset and xml code documents.     - short term : make the needed refactoring to provide this documenting solution with axel integration, a bundle providing a "symfony project documenting service" (starting by managing axel js library version with composer).     - long term and probably never : enhance the documentation process, integrating it with symfony specific feature, phpstorm ide, ticketing systems like redmine, trello and code forge sites like github (for integrated doc / code version managment).     - long term and probably never : add value added plugins to axel to enhance editing experience     - long term and probably never : add parsing of source code for a tighter integration with the xml content documenting the parsed source code.    - long term and probably never (yet really missing today): Add missing tracability between business requirements (like business specs / stories, evolution requests...), implementation code documenting, and QA test reports. Add enhanced integration of documentation of third parties components (like php / postgres / apache docs, value added tutorials found on the web...) : for example the capability to add "external links" to these third parties web documentations. Theses "external links sets" would be "project documentation centric" (not global knowledge centric : wikipedia , openclassromms and others exist for that), and defined by the project members to share and enhance knowledge in the project(s) dev team(s) on the mean / long term.
Controller code screen :
  - Changed the link to source code for this format :
source : /home/testp1/Dev/symfony_demo/src/AppBundle/Controller/BlogController.php, class : AppBundle\Controller\BlogController, method : indexAction, page : 41 : code source and class can then be copy/pasted in phpStorm on ubuntu where the standard url based integration lead to (too) complex congiguration in ubuntu.
  - Added the links : "Edit doc" and "Save doc as xml" with an alert of success or error : this links integrate the Axel xml editor library (http://ssire.github.io/axel/).
  TODO :
    - mean term : template is default (Page), add managment of customer templates configuration and "symfony framework feature specific" elements (same with apache and postresgl features) : for example add dynamic template extensions or full generations, based on the project or vendor bundle controller names, doctrine entities / repositories names and so on...
    - short term : check axel capability of templates with html links in text.
    - short term (level 1) and mean term (level 2) : manage templates and code documents in postgresql database : two (non mutualy exclusive) level of granularity : 1 : store xml documents "as is" in a db text field (so querying the xml with other db field is not possible yet full text postgres search in the xml documents are possible, and update is only possible at document level with the editor); 2 : store and manage xml document elements in db text fields, so everything is possible yet performance becomes an issue.
    - short term : refactor with asset component the coding of url/routes of axel's js asset and xml code documents.
    - short term : make the needed refactoring to provide this documenting solution with axel integration, a bundle providing a "symfony project documenting service" (starting by managing axel js library version with composer).
    - long term and probably never : enhance the documentation process, integrating it with symfony specific feature, phpstorm ide, ticketing systems like redmine, trello and code forge sites like github (for integrated doc / code version managment).
    - long term and probably never : add value added plugins to axel to enhance editing experience
    - long term and probably never : add parsing of source code for a tighter integration with the xml content documenting the parsed source code.
   - long term and probably never (yet really missing today): Add missing tracability between business requirements (like business specs / stories, evolution requests...), implementation code documenting, and QA test reports. Add enhanced integration of documentation of third parties components (like php / postgres / apache docs, value added tutorials found on the web...) : for example the capability to add "external links" to these third parties web documentations. Theses "external links sets" would be "project documentation centric" (not global knowledge centric : wikipedia , openclassromms and others exist for that), and defined by the project members to share and enhance knowledge in the project(s) dev team(s) on the mean / long term.

delahayef/testp1,delahayef/testp1,delahayef/testp1