06-11-2022, 01:12 AM
(This post was last modified: 06-11-2022, 01:26 AM by Alexandre Machado.)
Hi guys,
Recently I've been asked on how to enable the back button in an IntraWeb app and have it working as it was an HTML web site. I came up with this demo that I've just published showing how to accomplish that (it requires some bits released on IW 15.2.57):
https://github.com/Atozed/IntraWeb/tree/...ltiPageApp
Key points:
- The application works as a Multi-page application, MPA (opposed to SPA, Single Page Application). MPA have multiple URLs (e.g http://yourdomain/newcustomer http://yourdomain/checkout, etc). On the contrary, traditional SPAs have a single URL
- One key difference between MPA and SPA is how they respond to the back button. In general, hitting the back button when in a SPA application will take you to another page, outside the scope of the application. On the other hand, MPAs respond correctly to back and forward buttons and will take you to the previous or next page in the browser history, inside the application scope. Also, URLs of a MPA app can be bookmarked
- This application makes use of content handlers to handle the URL addresses of the application. Each form has its own URL.
- There is no special code required other than the creation of the content handlers and setting a single property in the ServerController
- Everything should just work as expected. Have a look at the comments in the source code as it contains some important information on how to switch between forms and how to create the content handlers
Enjoy!
Recently I've been asked on how to enable the back button in an IntraWeb app and have it working as it was an HTML web site. I came up with this demo that I've just published showing how to accomplish that (it requires some bits released on IW 15.2.57):
https://github.com/Atozed/IntraWeb/tree/...ltiPageApp
Key points:
- The application works as a Multi-page application, MPA (opposed to SPA, Single Page Application). MPA have multiple URLs (e.g http://yourdomain/newcustomer http://yourdomain/checkout, etc). On the contrary, traditional SPAs have a single URL
- One key difference between MPA and SPA is how they respond to the back button. In general, hitting the back button when in a SPA application will take you to another page, outside the scope of the application. On the other hand, MPAs respond correctly to back and forward buttons and will take you to the previous or next page in the browser history, inside the application scope. Also, URLs of a MPA app can be bookmarked
- This application makes use of content handlers to handle the URL addresses of the application. Each form has its own URL.
- There is no special code required other than the creation of the content handlers and setting a single property in the ServerController
- Everything should just work as expected. Have a look at the comments in the source code as it contains some important information on how to switch between forms and how to create the content handlers
Enjoy!