This is a communication as resulting of a dev effort in the french community to provide technical continuity to the initial Flexpage course format model (initially MoodleRooms provided).
Actually, we have a lot of 1.9 instances programs that will have to be upgraded, and the new architecture of the Flexpage format for 2.4 published by MoodleRooms could not be sustainable for us.
So we launched a new upgrade path to get the original Flexpage upgraded to Moodle 2, keeping the exact construction of the original, and pursuing making usefull enhancements on it.
This format is now called simply Paged format.
Here come some characteristics of it :
- No proprietary framework (no use of mr framework at all)
- Integration to "base" theme as far as possible to avoid having to redraw all themes for page integration
- Still using the "page" and "page item" concept
- "Page item" can be block or activity
- Activity still can have a portlet additional view to fit in-page presentation as a block
Some enhancements above the 1.9 version
- Full public pages (no login) : some pages of the course can be shown to outside people
- User attached pages : some pages can be assigned to some users (user base)
- Group attached pages : some pages can be assigned to exlusive group use
- Teacher pages : some pages can be only visible to teachers (though published)
- Drag'n'Drop page order and hierarchy rearrangement (using DHTMLX tree view)
- Activity override : one page can be completely overriden by an activity content.
- Page lock : one page access can be locked upon an activity score condition. This is tracked consistantly in accessory plugins.
Content of the plugin set :
- course "Page" format
- local end point overrides (needed to switch the block manager class, in some moodle screens)
- block "Page Module" : as for moodle 1.9 Flexipage, will embed and activity "as a block"
- block "Page Tracker" : a visual course map that provides monitoring upon visited sections
- module "Page Menu" : as for moodle 1.9 Flexipage, provides structured internal navigation of a paged course.
Solved issues :
- Overriding the whole standard block management strategy to fit multipage requirements : changes the block_manager to a specialized subclass.
- Theme integration ; new Flexpage version had a severe drowback for theme integration as forcing a "Page" theme to be used on paged courses. This was adding a lot of integration work on moodle that use multiple themes for making additional Paged enabled themes...
- Backup/restore : format specific information are circularily linked to course modules and block instances. This needs a complex post-mapping that could be resolved using the flexibility of new backup/restore architecture.
- Moodle 1.9 upgrade and content retrieval : This has been a serious and mandatory point, as we plan to use it as continuity of huge moodle 1.9 programs of several To of contents. I'm actually close to the end on that point, making last upgrading tests on real content...
Releasability of the plugins :
At this moment there was no schedule not plan to release and publish publically this work in moodle contribs (private publication status). The question is :
Is it worth publishing it aside the actual Flexipage format ?
You will find information entry point in my moodle supporting web site :