I did try to implement multipage resource, but failed. The internal structure of present resource is not compatible with multipage resource idea.
Problematic areas:
- database structure - one more page for subpage definitions would be needed, some changes would be needed in lib.php
- editing - resources are now edited on one page, it would take too long to load page with 10 editors for example, the subpage editing could be done on separate pages, or from user view (as in Book module). IMO it would not fit - all resources should be edited on one page only.
- view.php parameters - there would have to be one more parameter for subpage ID
- backup/restore - new routines for relinking of subpages
IMO it would be more interesting to export book content as SCORM package, I have already studied ATutor's source code - it looks promising
skodak