On Fri, 08 Nov 2013 20:12:20 -0200, Michael Wyraz
wrote:
IMO tapestry forms have too many restrictions (especially when form
elements are dynamic added/removed). We developped many workarounds
(e.g. manipulating t:formdata for adding/removing form elements) - but
this is so annoying that
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
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
Hi,
I could solve it - just needed to bootstrap angularjs manually:
- remove ng-app from my html
- add initializer code:
angular.bootstrap(document.getElementById('myapproot'),[MyApp']);
Hello Thiago,
thank you for fast reply. I'll check this as soon as my app runs.
At the moment I try to
Hello Thiago,
thank you for fast reply. I'll check this as soon as my app runs.
At the moment I try to get angularjs to work as module. A while ago you
wrote that you already did this and solved the problems.
What I've done:
- downloaded angular.zip, extracted to META-INF/assets/angular
- add
