[Seaside] Can I get a handle onto the canvas from a Seaside filter?

Mariano Martinez Peck marianopeck at gmail.com
Sat May 20 18:16:30 UTC 2017


On Sat, May 20, 2017 at 5:37 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> On Fri, May 19, 2017 at 7:07 PM, Mariano Martinez Peck
> <marianopeck at gmail.com> wrote:
> > Hi guys,
> >
> > I do already have some filters (subclasses of WARequestFilter) in which I
> > implement #handleFiltered:. In these cases, I normally do some
> > "backend-only" stuff. But now, I have a usecase in which I would like to
> do
> > some backend stuff, but also, may want to answer some JS to be executed
> > besides the specific answer for that case. For example, I want to do
> > something like this:
> >
> > script << ((html jQuery id: '#whatever') replaceWith:[:r |
> > self somethingRenderedOn: r.
> > ])
>
> Just to be sure I understand you correctly: behind the filter is some
> request handler or component that does the actual rendering which you
> want to influence?
>

Exactly. Imagine a JS script that I would like to render after each Seaside
callback.



>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside/attachments/20170520/c5f84260/attachment.html>


More information about the seaside mailing list