Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-45949

SCORM TOC tree should expand the node currently in use

    Details

    • Affected Branches:
      MOODLE_26_STABLE, MOODLE_27_STABLE

      Description

      When a Scorm package is used with a complex structure (Categories and subcategories, etc..), The tree collapses whenever sco is changed, so that the student does not have a clear vison is located within the content.

      So it would be advisable to set the status of the tree between collapsed and expanded, in the config page.

      In previous versions, the tree expanded by default came out, so there was no problem.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              danmarsden Dan Marsden added a comment -

              Thanks for the report. I'm not too keen adding another setting to control this... IMO the parts of the tree not in use should be collapsed but the area the student is currently looking at should be expanded to show the location - if that's not currently happening it's definitely a bug - if you manage to track a fix down to allow this I'd consider adding it but I'm not convinced that a setting to always leave the TOC tree expanded is a good idea. (feel free to try and convince me though!)

              just stating "it did it that way in previous versions" isn't likely to convince me

              Show
              danmarsden Dan Marsden added a comment - Thanks for the report. I'm not too keen adding another setting to control this... IMO the parts of the tree not in use should be collapsed but the area the student is currently looking at should be expanded to show the location - if that's not currently happening it's definitely a bug - if you manage to track a fix down to allow this I'd consider adding it but I'm not convinced that a setting to always leave the TOC tree expanded is a good idea. (feel free to try and convince me though!) just stating "it did it that way in previous versions" isn't likely to convince me
              Hide
              seryon Sergio López added a comment -

              In my case I am using version 2.5 just for this operation, I understand that everyone may not be useful to expand the entire tree, but as you say, at least should show deployed across the category to which belongs the point Viewed .

              Show
              seryon Sergio López added a comment - In my case I am using version 2.5 just for this operation, I understand that everyone may not be useful to expand the entire tree, but as you say, at least should show deployed across the category to which belongs the point Viewed .
              Hide
              bostjan53 Bostjan added a comment -

              We are dealing with same problem.

              Current node is not expanded.

              But if user clicks twice in a row on same node, current location is expanded.

              Show
              bostjan53 Bostjan added a comment - We are dealing with same problem. Current node is not expanded. But if user clicks twice in a row on same node, current location is expanded.
              Hide
              vicentgrau Vicent Grau Martínez added a comment -

              Moreover, it happens that the navigation of SCORM does not work since some versions, which forces the user to expand increasingly folders and subfolders contained tree. I agree with Sergio Lopez in that at least the folder of the current SCO should open. It is not necessary that the entire tree to fully expand. I consider it very important to find a solution to this problem.

              PD: Sorry for my English translation.

              Show
              vicentgrau Vicent Grau Martínez added a comment - Moreover, it happens that the navigation of SCORM does not work since some versions, which forces the user to expand increasingly folders and subfolders contained tree. I agree with Sergio Lopez in that at least the folder of the current SCO should open. It is not necessary that the entire tree to fully expand. I consider it very important to find a solution to this problem. PD: Sorry for my English translation.
              Hide
              stephanep Stéphane Poinsart added a comment - - edited

              Hello,

              As a workaround, let me provide a 1 line tentative patch (moodle28-scorm-toc-expand-workaround.patch) that should revert moodle 2.8 to the old behavior of "the scorm TOC is fully expanded". It is provided just as a workaround, designed only to allow the survival of the users who find the current behavior too frustrating, until someone else provide a proper fix.

              It does not conform to the "expand only the items in the path up to the current node" behavior requested in this ticket so you probably don't want to mainline it.

              Make sure you clear your cache if you want to test the patch, otherwise the old JS file still get loaded.

              In moodle 2.6, it probably will not work as lazy loading is done explicitly in mod/scorm/yui/build/moodle-mod_scorm-treeview/moodle-mod_scorm-treeview.js but you can probably change it in there. I don't know about 2.7.

              Regards,

              Stephane

              Show
              stephanep Stéphane Poinsart added a comment - - edited Hello, As a workaround, let me provide a 1 line tentative patch (moodle28-scorm-toc-expand-workaround.patch) that should revert moodle 2.8 to the old behavior of "the scorm TOC is fully expanded". It is provided just as a workaround, designed only to allow the survival of the users who find the current behavior too frustrating, until someone else provide a proper fix. It does not conform to the "expand only the items in the path up to the current node" behavior requested in this ticket so you probably don't want to mainline it. Make sure you clear your cache if you want to test the patch, otherwise the old JS file still get loaded. In moodle 2.6, it probably will not work as lazy loading is done explicitly in mod/scorm/yui/build/moodle-mod_scorm-treeview/moodle-mod_scorm-treeview.js but you can probably change it in there. I don't know about 2.7. Regards, Stephane
              Hide
              vicentgrau Vicent Grau Martínez added a comment -

              I checked in version 2.7.4 and it works. It also allows floating navigation bar works well.
              Indeed not only expands the elements of the path to the current node that would be desirable.
              Thanks Stéphane.

              Vicent Grau

              Show
              vicentgrau Vicent Grau Martínez added a comment - I checked in version 2.7.4 and it works. It also allows floating navigation bar works well. Indeed not only expands the elements of the path to the current node that would be desirable. Thanks Stéphane. Vicent Grau

                People

                • Votes:
                  12 Vote for this issue
                  Watchers:
                  13 Start watching this issue

                  Dates

                  • Created:
                    Updated: