Thanks. Serving the app from different places was one of the options. I haven't thought about independent caches etc. I see now it was a bad idea :-D I saw that the apiviewer uses the hash for the generated link but I assumed the hash is only for describing document fragment. But yeah, it could be shared around as a link and simplifies a lot of things.
> Regarding the docs, the link you gave is for qx.Website - I assumed you were writing a Desktop app, but I guess that’s not the case? I don’t know how different qx.Website and Desktop are from each other I am writing a Desktop app but Apiviewer also uses that module and I also use some other qx.bom modules. Thank you very much for the advice On 11/12/2015 08:06 μμ, John Spackman wrote: > If you do that then doesn’t that mean that you’ll have to serve the app up > from several URLs (in which case the browser will see each URL as a separate > app and cache the results independently), or redirect the user back to a > common URL with a parameter? > > I think the differences with the API viewer is that because the app is > already running when the user clicks a link, it can intercept the event and > modify the history (and the URL in the address bar) so it appears that there > are these different URLs, but the API viewer modifies the URL to change the > bookmark (ie the part after a #) and not the change the path to the app > itself. EG the URLs are > http://demo.qooxdoo.org/current/apiviewer/#qx.ui.layout.HBox and > http://demo.qooxdoo.org/current/apiviewer/#qx.ui.layout.Grow, and *not* > http://demo.qooxdoo.org/current/apiviewer/qx.ui.layout.Grow > > This is essential because it means that the app is always being loaded from > the same place, and the app can determine when it starts up what the bookmark > is referring to. > > So your bookmark able URLs would need to be something like: > > > > http://example.com/mainapp/#accounts/password/reset/key/2-47k-0ab765eddbf39c6656aa/ > http://example.com/mainapp/#accounts/user/voger > http://example.com/mainapp/#users/voger/posts > http://example.com/mainapp/#users/voger/post/123456 > > Regarding the docs, the link you gave is for qx.Website - I assumed you were > writing a Desktop app, but I guess that’s not the case? I don’t know how > different qx.Website and Desktop are from each other > > John > > > On 11/12/2015, 17:50, "voger" <vogernewslett...@yahoo.gr> wrote: > >> What I want to do is to create bookmarkable and clickable links. >> >> for example >> >> http://example.com/accounts/password/reset/key/2-47k-0ab765eddbf39c6656aa/ >> Will open the main app with a dialog for reset password >> >> http://example.com/accounts/user/voger >> Will open the main app with a window with the users profile >> >> http://example.com/users/voger/posts >> Will open the main app with a window with voger's posts >> >> http://example.com/users/voger/post/123456 >> Will open the main app with a window displaying the specific post >> >> Kind of like the apiviewer does it. I am reading it's code and try to >> understand how it works. >> >> I try to get as much information as and I haven't clarified yet in my >> mind how to design it. Should the content be somewhere in the HTML >> minimizing trips to the server and maximizing SEO potential or should I >> rely in parsing the URL? Should I use the qx.bom.History module or some >> other library or rely in pure javascript? >> >> Also it gets more confusing with the note in the top of Back-Button and >> Bookmark Support page in the manual >> http://manual.qooxdoo.org/current/pages/website/back-button_and_bookmark_support.html?highlight=history >> >> "This document is outdated and does not reflect the proposed way of >> working with qx.Website. The history module is still under development. >> As soon as the module is ready, this document will be updated as well." >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> qooxdoo-devel mailing list >> qooxdoo-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
