Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m2, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      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.

        Attachments

          Issue Links

            Activity

            jkneal Jerry Neal (Inactive) created issue -
            jkneal Jerry Neal (Inactive) made changes -
            Field Original Value New Value
            Link This issue cloned from KULRICE-7208 [ KULRICE-7208 ]
            jkneal Jerry Neal (Inactive) made changes -
            Fix Version/s 2.2.0-m2 [ 16463 ]
            Fix Version/s 2.2-backlog [ 16475 ]
            Description 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 what the plan:

            More ...

            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.
            jkneal Jerry Neal (Inactive) made changes -
            Start Date
            Fix Date 2012-06-25 [ set to sprint end date ]
            jkneal Jerry Neal (Inactive) made changes -
            Description 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 what the plan:

            More ...

            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.
            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 showDia
            jkneal Jerry Neal (Inactive) made changes -
            Description 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 showDia
            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.
            Assignee Brian Smith [ bsmith ]
            Hide
            dsiebert Daniel Seibert (Inactive) added a comment -

            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

            Show
            dsiebert Daniel Seibert (Inactive) added a comment - 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
            jkneal Jerry Neal (Inactive) made changes -
            Assignee Brian Smith [ bsmith ] Claus Niesen [ cniesen ]
            cniesen Claus Niesen made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            Claus,

            Can we resolve this one?

            Jerry

            Show
            jkneal Jerry Neal (Inactive) added a comment - Claus, Can we resolve this one? Jerry
            cniesen Claus Niesen made changes -
            Link This issue discovered KULRICE-7668 [ KULRICE-7668 ]
            cniesen Claus Niesen made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 146406 ] Copy of custom for rice [ 214495 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow Copy of custom for rice [ 214495 ] custom [ 224243 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 224243 ] Rice Workflow [ 233991 ]

              People

              • Assignee:
                cniesen Claus Niesen
                Reporter:
                jkneal Jerry Neal (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: