Hi Voger

As the second tab will be opened by a link, you won’t have a window to 
postMessage to/from and AIUI there is no way to get one.  This means that the 
only way to communicate with the main application in the first tab is via the 
server - and the only way to do that is to poll the server for changes.  

How quickly that updates the main app obviously depends on how often you poll, 
but there is a technique called “long poll” where you asynchronously poll the 
server and the server waits for a “long” time until there is something to 
return.  This minimises the number of round trips you have and can simulate 
server push, although it does mean that your server will always have a 
connection open for every client.

Regards
John



On 09/12/2015, 20:20, "voger" <vogernewslett...@yahoo.gr> wrote:

>The Web is all about links and a qooxdoo application is still a web 
>application. So how it can be done so a link from another source perform 
>a specific action in the qooxdoo application. A concrete example I have 
>is with password reset links. Let's say a user receives a link that he 
>can click, go to the web page types twice the password, the form is 
>submitted and the new password is valid.
>
>In qooxdoo desktop the workflow would be somehow different. The user 
>clicks the link, **goes to the main app, the main app opens a window 
>with two password fields**, the user submits the form and the new 
>password is valid.
>
>But how can I make the main app see the link and open the appropriate 
>window?
>
>I saw the code of Apiviewer and the only relevant part I found is this 
>https://github.com/qooxdoo/qooxdoo/blob/master/component/apiviewer/source/class/apiviewer/Viewer.js#L78
>
>I couldn't find the part where it loads the class from a bookmarked link
>
>Also I don't know how to implement such functionality. An idea I have is 
>this:
>The user clicks the link http://mypage.com/bookmarkable/stuff
>The server returns a stuff.html page with javascript that writes 
>instructions in the cookie for the main app and then redirects to the 
>main page
>In the main page the main app looks at the cookie and if it finds 
>instructions acts upon them and then deletes them.
>
>Is this a good idea? Any criticism or pointers to better ideas?
>
>------------------------------------------------------------------------------
>_______________________________________________
>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

Reply via email to