What would be the proper way to open a new browser window/tab with a
selected component as root component but using the same session? E.g. I have a main app component and want to open "viewers" (a new component on a particular model) as root component on the new tab. I expect the user to interact with this new component, and then likely to close the tab, the component tree in the main tab should remain unchanged. I could see WAInitialRenderLoopContinuation seems to have what I need, but the whole WARenderLoopContinuation hierarchy is something that I could never understand and never could find documentation about it either (e.g. WAPluggableActionContinuation doesn't have any references in my image). I'll appreciate any pointer here. Regards, Esteban A. Maringolo _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi! I just use self session presenter show: aComponent in a popupAnchor callback On Wed, Feb 6, 2019 at 9:57 PM Esteban Maringolo <[hidden email]> wrote: What would be the proper way to open a new browser window/tab with a _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Esteban A. Maringolo
Hi Esteban,
I would think the following is sufficient: html anchor target: ‘_blank’; callback: [ …. ]; with: ’Open another tab’ This opens the component on another tab/window using the same session. Both pages are different application states (aka continuations) within the same session. Johan > On 6 Feb 2019, at 21:56, Esteban Maringolo <[hidden email]> wrote: > > What would be the proper way to open a new browser window/tab with a > selected component as root component but using the same session? > > E.g. I have a main app component and want to open "viewers" (a new > component on a particular model) as root component on the new tab. I > expect the user to interact with this new component, and then likely > to close the tab, the component tree in the main tab should remain > unchanged. > > I could see WAInitialRenderLoopContinuation seems to have what I need, > but the whole WARenderLoopContinuation hierarchy is something that I > could never understand and never could find documentation about it > either (e.g. WAPluggableActionContinuation doesn't have any references > in my image). > > I'll appreciate any pointer here. > > Regards, > > Esteban A. Maringolo > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi Johan, Gerhard,
I was opening on other tabs, using the `target: '_blank'` approach, but for callbacks returning content with inline disposition (e.g. HTML/PDF reports), however the trick I was missing was the one that Gerhard suggested, using the `self session presenter show: (MyComponent new)`. I wasn't aware of the `presenter` in the session, and I don't know exactly what it does, but it works! I though I understood Continuations when Seaside was originally released, and when I ported Seaside 2.7 to Dolphin, but now with this I have to assume I can't explain WHY it works. :-| I'm willing to learn the WHY if somebody wants to explain, I could donate to a bounty if necessary. :) Thanks for the help. Best regards, Esteban A. Maringolo El jue., 7 feb. 2019 a las 3:39, Johan Brichau (<[hidden email]>) escribió: > > Hi Esteban, > > I would think the following is sufficient: > > html anchor > target: ‘_blank’; > callback: [ …. ]; > with: ’Open another tab’ > > This opens the component on another tab/window using the same session. > Both pages are different application states (aka continuations) within the same session. > > Johan > > > On 6 Feb 2019, at 21:56, Esteban Maringolo <[hidden email]> wrote: > > > > What would be the proper way to open a new browser window/tab with a > > selected component as root component but using the same session? > > > > E.g. I have a main app component and want to open "viewers" (a new > > component on a particular model) as root component on the new tab. I > > expect the user to interact with this new component, and then likely > > to close the tab, the component tree in the main tab should remain > > unchanged. > > > > I could see WAInitialRenderLoopContinuation seems to have what I need, > > but the whole WARenderLoopContinuation hierarchy is something that I > > could never understand and never could find documentation about it > > either (e.g. WAPluggableActionContinuation doesn't have any references > > in my image). > > > > I'll appreciate any pointer here. > > > > Regards, > > > > Esteban A. Maringolo > > _______________________________________________ > > seaside mailing list > > [hidden email] > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |