[
https://issues.apache.org/jira/browse/TAP5-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835888#action_12835888
]
Ville Virtanen commented on TAP5-558:
-------------------------------------
I think the form fragment part is overkill, 99% of cases does not need that
functionality. The same logic that could be implemented using
"form-fragment-dialog" can be implemented using separate per dialog forms I
believe. The important part is to get the dialog to load via ajax. I know that
I requested the form fragment part, and I think it would be super cool if you
could do such thing but the priority is rather low I think.
Would the changes to PrgressiveDisplay and ZoneManager be beneficial to other
use cases also? At least it would enable developers to do things like "place
progressive display to page and make it do it's magic when it gets visibility",
which in my opinion would be great.
In the end, it all depends how hard that is. If it is really hard just
implement the progressivedisplay functionality directly to modaldialog, but
please at least make it configurable from client _and_ server side whether to
use the lazy loading of the dialog contents.
My 2c :)
And thanks for doing great job Ulrich!
> Create modal dialog component
> -----------------------------
>
> Key: TAP5-558
> URL: https://issues.apache.org/jira/browse/TAP5-558
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Ville Virtanen
> Assignee: Ulrich Stärk
> Attachments: Dialog-Mixin-src.tar.gz
>
>
> Tapestry's AJAX support is missing one important component, modal (or
> non-modal) dialog. Dialog could be created with
> http://www.wildbit.com/labs/modalbox/ or http://roland.devarea.nl/dialog/ or
> http://github.com/robhurring/prototype-dialog/ or
> http://livepipe.net/control/window
> After quick look first one looks like most professional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
