Hello!
I'm struggeling with very dynamic forms on a regular base. Especially an "out
of date" t:form-data which does no longer represent the current state/content
of the form.
So I found HLS's idea of a form submit paradigmn change --> replacing normal
HTTP Posts and their query params with AJA
On Tue, Mar 27, 2018 at 4:49 AM, wrote:
> Hi,
>
Hello!
> tapestry 5.4 made with the requireJS integration a great step towards
> supporting any
> of the JS frameworks out there. Supporting only a single one of them would
> be a step
> back.
>
Indeed. This doesn't prevent having separate proje
On Mon, Mar 26, 2018 at 6:45 PM, Juan Manuel Garrido de Paz <
juanm.garrido@gmail.com> wrote:
> Hi Thiago, does it make sense to use tapestry just as a middleware between
> a javascript client-side framework and the server? Just for implementing a
> REST API that gathers the requests from the
On Mon, Mar 26, 2018 at 6:45 PM, Cezary Biernacki
wrote:
> @SetupRender
> public void configureWaitSeconds() {
> // See http://requirejs.org/docs/api.html#config-waitSeconds
> javaScriptSupport.addModuleConfigurationCallback((config) ->
> config.put("waitSeconds", 120));
>
Hi,
tapestry 5.4 made with the requireJS integration a great step towards
supporting any
of the JS frameworks out there. Supporting only a single one of them would be a
step
back.
Using tapestry on the server side of dynamic client applications is effective
as it
possible to initialize the pag
