Re: some old criticisms of T5

2016-09-22 Thread Cezary Biernacki
In my experience Tapestry generates better HTML than many (most?) of other frameworks. Lets take for example the whitespace issue. In most cases whitespace in templates are artefacts of indentation used to improve readability of templates during development. As the result when blindly preserved,

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

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"); >

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

2016-09-22 Thread rapidtransit440
Wouldn't jsSupport.require("foo").invoke("myFunc").with("bar"); Work? IMHO if the library is your own (a bit from a mixin that adds a spinner on ajax buttons and then removes it on a response), ajaxResponseRenderer.addCallback((JavaScriptCallback) javascriptSupport -> {

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

Re: beaneditform with option lists of objects

2016-09-22 Thread Barry Books
You will need to build a select model for your list http://tapestry.apache.org/using-select-with-a-list.html I would create an Interface and have the child implement it so you can create a generic one Then create an edit block out of that code. This will allow the BeanEditor to edit this kind