1. 12 Jun, 2020 1 commit
  2. 30 Sep, 2019 1 commit
  3. 24 Sep, 2019 1 commit
    • Roque's avatar
      erp5_officejs: refactoring in new officejs approach · 14354bad
      Roque authored
      - reorginize and extend app setting and customization
      - each portal type has its own setting dictionary
      - handling blob types in document render and submit
      - remove hardcoded app configuration manifest
      - allow custom view in controller
      - common configurations refactored
      - handle_action handles notify submit and redirect base on custom action
      return
      - controller default page forces storage sync if app version changes
      - fix 401 login redirect in storage selection
      - general code refactoring and cleanup
      14354bad
  4. 09 Aug, 2019 1 commit
    • Roque's avatar
      erp5_officejs: new approach for officejs apps · fba02e96
      Roque authored
      - improve OfficeJS applications by reducing the quantity of code to be written and reuse the ERP5 configuration (portal_type, actions, forms, etc.) instead to generate the app
      fba02e96
  5. 11 Feb, 2019 1 commit
  6. 27 Sep, 2017 1 commit
  7. 07 Mar, 2016 1 commit
  8. 02 Mar, 2016 1 commit
  9. 13 Jan, 2016 1 commit
  10. 06 Jan, 2016 1 commit
  11. 30 Nov, 2015 1 commit
  12. 25 Nov, 2015 2 commits
  13. 12 Nov, 2015 1 commit
  14. 28 Oct, 2015 9 commits
  15. 27 Oct, 2015 1 commit
  16. 20 Oct, 2015 1 commit
    • Romain Courteaud's avatar
      [erp5_web_renderjs_ui] Rewrite the URL navigation handling · 89ef7b43
      Romain Courteaud authored
      Stop using the patched renderJS version which forces to use a fix URL pattern (#a=b&c=d).
      Instead, the URL logic was moved to the router gadget which becomes responsible to build and parse URL.
      
      This will allow applications to support their own URL pattern (HTML5 pushState for example).
      
      In case of the ERP5 JS UI, it provides now a stateful URL building (next URL depends on the current one).
      
      This is used to support browser side "selection" (ie, stored query parameters), needed to support pagination from one document to another.
      Example:
        * go to a module
        * filter with a search
        * click on the first document line and review it
        * click on the "next" icon, to directly see the second document without going back to the list
      
      Stateful URL are also used to provides a "global" navigation history on the browser side.
        Example:
         * go to a module
         * click on the first document (A) and review it
         * use a jump button to go to a linked document (B) and review it
         * click on the "back" button to go back to A
         * click on the "back" button to go back to the module
      Please note that this history works even if you open a new tab, as it is persistent in IndexedDB.
      TODO: it will be required to clean IndexedDB from time to time to not fill it
      
      The current URL patterns are:
        #/jio_key?a=b&c=d (used to display an ERP5 document)
        #!command?a=b&c=d (used to apply some operations on the URL)
      89ef7b43
  17. 18 Sep, 2015 1 commit
  18. 04 Feb, 2015 1 commit
  19. 13 Oct, 2014 1 commit
  20. 03 Oct, 2014 1 commit
  21. 02 Oct, 2014 1 commit
    • Romain Courteaud's avatar
      Implement interaction between the header and the page content. · f7320a4b
      Romain Courteaud authored
      Move loading notification in the header (drop JQM global notification).
      Inform user when some changes were made in the form.
      Add form submit notification.
      Allow to trigger the form submit from the header button.
      Do not submit any form if one gadget field validation constraint fails. Display the error next to the label.
      f7320a4b
  22. 29 Sep, 2014 1 commit
  23. 18 Sep, 2014 1 commit
  24. 08 Aug, 2014 7 commits
  25. 30 May, 2011 1 commit