[KULRICE-7554] Implement Dialog Group invocation mode Created: 27/Jun/12  Updated: 03/Apr/13  Resolved: 16/Jul/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.2.0-m2, 2.2
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Jerry Neal (Inactive) Assignee: Claus Niesen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-7208 Template Closed
discovered KULRICE-7668 Ajax Rendering of Lightbox doesn't bl... Open
Similar issues:
KULRICE-14082Reduce invocations for edit mode and action flag checks
KULRICE-10360Investigate a reset option for dialog groups
KULRICE-12138KRAD Library - Containers - Dialog Group - Regular Group Dialog actions Yes No are non-functional
KULRICE-12137KRAD Library Containers - Dialog Group - Client AJAX Dialog Empty textbox in lightbox.
KULRICE-13558Fill AFT Gap: KRAD Labs: Dialog with Explanation in ReadOnly mode
KULRICE-7446Implement return from dialog
KULRICE-7330Dialog Framework - UifDialogGroup create new group component
KULRICE-13628Fill AFT Gap: Library Containers Dialog Group
KULRICE-8828Dialog group bean definition should force session presistence
KULRICE-12812Labels in dialog group get clearfix class added four times
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


Currently the dialog groups are configured in a list on the view and rendered after the view is rendered. We want to have options or the rendering of these so each one is not rendered every time (some could be invoked by the server in certain situations).

This is roughly the plan:

Dialog Render:

1) From Server

2) Client Dom

3) Client Ajax

Add an option to DialogGroup named invocationMode that defaults to server. Can be changed to dom or ajax.

We will need to add something to the end of the view template that iterates through the dialogGroups and writes those that are marked as client dom or client ajax. For the dom option the group would then be hidden. For ajax just the wrapper is needed. Take a look at template.tag and how it handles progressiveDisclosure. We might be able to let the template.tag handle it for us and by setting the progress properties.

We could write the invocation mode as a data attribute, and other information needed for retrieving the group as data attributes. Then in showLightboxComponent we need to check whether the group is marked for ajax, and if so retrieve the contents before displaying in the lightbox.

Comment by Daniel Seibert (Inactive) [ 27/Jun/12 ]

See Jerry's notes at the bottom of the dialog design notes page: https://wiki.kuali.org/display/KULRICE/Dialog+Framework%2C+Rich+Lightbox+design+notes

Comment by Jerry Neal (Inactive) [ 16/Jul/12 ]


Can we resolve this one?


Generated at Wed Apr 08 22:31:33 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.