Page Comparison

...

<stage w="100" x="0" h="100" y="0" id="3a52e8ee-349c-49de-b5da-a6a47b268218">
        <config>
            <![CDATA[{"opacity":100,"strokeWidth":1,"stroke":"rgba(255, 255, 255, 0)","autoplay":false,"visible":true,"color":"#FFFFFF","genieControls":false,"instructions":""}]]>
        </config>
        <param name="previous" value="59e8bd17-86ad-4043-b340-18c9d9862a5c"></param>
        <org.ekstep.summary rotate="0" z-index="0" w="77.45" x="4.61" h="125.53" y="-29.38" id="45ecdc54-ce1d-48cd-a5a4-808c03ee12e2">
            <config>
                <![CDATA[{"opacity":100,"strokeWidth":1,"stroke":"rgba(255, 255, 255, 0)","autoplay":false,"visible":true}]]>
            </config>
        </org.ekstep.summary>
        <manifest>
            <media assetId="summaryImage"></media>
        </manifest>
  </stage>

Pros:

• This will take less development time and no other changes in the existing flow.

Cons:

• For new content types, we are adding forcefully adding new stage programmatically, what if some other content types introduce in the futureEasy to implement. Simple change on the content creation side(editor).

• Any summary plugin fixes will reflect on the new/edit contents immediately.(without user concern)

Cons:

• We are adding this plugin for every self-assess content. It will increase the size of the ecar file.

• Any fixes of the summary plugin will work only for new contents. Older contents need to edit & republish to get fixes of summary plugin.

• This is the core plugin changes(Stage plugin), any issues will have an huge impact on other contents as well.

• If user explicity adding this plugin to the last stage, then he will see 2 stages with summary plugin. Which he don’t have any info why it is showing twice.

Note:

Existing contents has to fix(remove the last slide). Else edit/copy of the any exisinting will be having duplicate slides of summary plugin.

Solution 2:

Handling on consumption side as an end-page plugin(merging summary plugin & end page)

...