Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-12563

Build JSR-168 Portlet as Complete Replacement for Web.Content Tool

    Details

    • Type: Task
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.0
    • Fix Version/s: 2.9.2
    • Component/s: Web Content
    • Labels:
      None

      Description

      Build a complete seamless replacement for the web content tool except using a JSR-168 portlet. The portlet should look and operate exacly the same as the tool, except that the Options button moves to the title bar as a little "Edit" icon. This way, when a page is displayed there is only one iframe in the background document. In the current situation there is an iframe within an iframe for the sole purpose of displaying the Options button.

      Make a portlet that responds to the sakai.iframe and other tool ids:

      sakai.iframe.myworkspace
      sakai.iframe.service
      sakai.iframe.site
      sakai.iframe

      The original tool will be retained with its IDs disabled so that switching back will be a simple patch if problems are identified.

      No conversion will be necessary - the portlet will use the same property settings as the tool and use all the same translations - the actual Velocity files will be reused in the portlet so look and feel will be identical to the web content tool.

      This will also make the popups look different - when the popups come up - they will only have the content - not the content within a Sakai frame and an options button.

      This will also allow the iFrame tool to be used with the new frame set portal where the left navigation goes away and the entire screen bottom belongs to the content (see SAK-12402).

      This also paves the way to teach the iFrame portlet about content proxying - thus eliminating iframes completely in some cases. Because the tool starts out as a portlet, there is no enclosing frame - if the tool learns to proxy - then there are no remaining frames in a web content placement - Viola!

      This JIRA is only about the direct replacement of the iFrame tool with an iFrame portlet. Other Jiras will be written covering any new features put into the iFrame portlet.

      This depends on the changes included following other JIRAS in /portal and /reference - they are simple - but important:

      SAK-23195
      SAK-23224

      Make sure to install those along with this code if you want to deploy this tool.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  csev Charles Severance
                  Reporter:
                  csev Charles Severance
                  Votes:
                  1 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration