Andreas,
I'm also saying that if you're after big/complex angular apps (within
Tapestry or standalone), then componentize at the angular level.
But why have Tapestry templates generate those static angular templates
instead of just serving them directly from the context ?
because this gives me
In my proof-of-concept app I decided to use REST (tynamo-resteasy) for
binding the gui to the backend. So I do not use tapestry forms at all.
IMO tapestry forms have too many restrictions (especially when form
elements are dynamic added/removed). We developped many workarounds
(e.g. manipulati
Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
Any issues for the Board?
There are no Board-level issues at this time.
When did the project last make any releases?
The latest stable vers
I'm also saying that if you're after big/complex angular apps (within
Tapestry or standalone), then componentize at the angular level.
But why have Tapestry templates generate those static angular templates
instead of just serving them directly from the context ?
On Fri, Nov 8, 2013 at 9:29 AM,
On Fri, 08 Nov 2013 07:40:58 -0200, Dmitry Gusev
wrote:
I thought about Angular/Tapestry integration and I see one issue so far:
Is's integrating with Tapestry5 forms
Angular can update DOM on the client-side but you won't be able to submit
that form, to be more correct because tapestry won
I thought about Angular/Tapestry integration and I see one issue so far:
Is's integrating with Tapestry5 forms
Angular can update DOM on the client-side but you won't be able to submit
that form, to be more correct because tapestry won't be able to handle
submitted data (translate values, validat
