On Tue, 03 Mar 2015 09:36:11 -0300, Robert Schmelzer
wrote:
Hi,
Hi!
we built a prototype based on your suggestions. The main idea would work
- but there is one main issue we are not able to address:
Event propagation - if the component fires a request it will be
propagated to its "
Hi,
we built a prototype based on your suggestions. The main idea would work
- but there is one main issue we are not able to address:
Event propagation - if the component fires a request it will be
propagated to its "dummy" page where the component is hosted and we
cannot attach listeneres
On Mon, 02 Mar 2015 11:42:57 -0300, Robert Schmelzer
wrote:
Thanks for the immediate response.
;)
We are building a product which acts as a complete backoffice solution
for a specific business type - so yes the 220 pages are doing really
different things.
Wow indeed. :)
The reusable
Thanks for the immediate response.
We are building a product which acts as a complete backoffice solution
for a specific business type - so yes the 220 pages are doing really
different things. The reusable parts are all modeled as components. And
yes your assumption is right, all of the pages
On Mon, 02 Mar 2015 10:43:09 -0300, Robert Schmelzer
wrote:
Hi,
Hi!
we have a quite big business app counting about 220 pages.
Wow! 220! Does it really need that many unique pages? Does each one have
its own logic, different from the others?
By the way, which Tapestry version does t
Hi,
we have a quite big business app counting about 220 pages. We are using
a UX style where you can pop up dialogs containing wizards, which can
again pop up dialogs and so on. The dialogs are opened in AJAX request
on top of the page and realized in tapestry as embedded components.
After fu
