Search the Community
Showing results for tags 'history'.
Routing is the link between specific url's and specific functionality in an app, so f.i. https://<server>/index.html starts up your app in the browser as per normal https://<server>/login executes a specific view (f.i a login form) Smart per default produces single page app's, without routing functionality There are a couple of strategies which can be followed to implement routing (and which will work to some extent) : use # formatted urls. Browsers have a 'hashchange' event built in, which fires every time a url changes,
- the browsers back-button in Smart Mobile Studio Most users find it frustrating they cannot use their browsers back/next buttons to navigate between forms. And especially so since they will typically leave the application altogether if they use them. One solution to this problem is manipulating the browsers history stack. Basically if we insert entries in the browsers history whenever there is a form change, and have a notification happening when the user uses the back/next buttons, then we can hook any history changes to form changes. Html5 introduced the history object. See http