Re: org.apache.tapestry5.services.javascript.Initialization.with(Object... arguments)

2016-09-22 Thread Adam X
I was thinking about that but never tried as it doesn't seem intuitive at all :) But thanks for the hint, I will refactor. Adam On Thu, Sep 22, 2016 at 6:06 PM, Cezary Biernacki wrote: > You can do: > > jsSupport.require("foo").invoke("myFunc").with("bar"); > > Best regards, > Cezary > > > On Th

Re: org.apache.tapestry5.services.javascript.Initialization.with(Object... arguments)

2016-09-22 Thread Cezary Biernacki
You can do: jsSupport.require("foo").invoke("myFunc").with("bar"); Best regards, Cezary On Thu, Sep 22, 2016 at 5:54 PM, Adam X wrote: > Is there a reason this is not a fluid setter? Right now I have to do: > > Initialization foo = jsSupport.require("foo"); > foo.with("bar"); > foo.invoke("my

Re: org.apache.tapestry5.services.javascript.Initialization.with(Object... arguments)

2016-09-22 Thread rapidtransit440
moveClass('loading'); } }); -Original Message- From: Adam X To: Tapestry users Sent: Thu, Sep 22, 2016 11:54 am Subject: org.apache.tapestry5.services.javascript.Initialization.with(Object... arguments) Is there a reason this is not a fluid setter? Right now I have

org.apache.tapestry5.services.javascript.Initialization.with(Object... arguments)

2016-09-22 Thread Adam X
Is there a reason this is not a fluid setter? Right now I have to do: Initialization foo = jsSupport.require("foo"); foo.with("bar"); foo.invoke("myFunc"); I'd rather just do: jsSupport.require("foo").with("bar").invoke("myFunc") but with(Object...) returns void :( Adam -