Urs Hunkler

I just created the Moodle Tracker entry MDL-28198.

I tried to get the Moodle popup dialogs looking consistent. After spending a lot of work into the filepicker, quiz and help dialogs I arrived at the enrolment dialogs - and went nuts.

I get the impression that each Moodle popup is build different - different XHTML structure, different CSS, different images

Usability of the dialogs is similar inconsistent. For example some dialogs have "Cancle" buttons, some must be closed clicking on the "x"-close-button.

There are 5 enrolment dialogs - each is different. From the dialogs I had worked on I got the impression that they more or less use YUI Overlay structure and CSS. From the enrolment dialogs the "quickcohortenrolment" dialog is the only one basing on Overlay. The others are build different.

Please refactor ALL dialogs to offer a consistent interface (look and feel, buttons etc.) and use consistent XHTML, CSS and images.

Please, everybody interested in Moodle Usability and Look vote on the tracker issue - I hope somebody will investigate then.

I cross-post this topic here and in the "General developer forum" because I think this is an issue for developers and designers and not many read both forums.

I just created the Moodle tracker entry MDL-28198.

I tried to get the Moodle popup dialogs looking consistent. After spending a lot of work into the filepicker, quiz and help dialogs I arrived at the enrolment dialogs - and went nuts.

I get the impression that each Moodle popup is build different - different XHTML structure, different CSS, different images

Usability of the dialogs is similar inconsistent. For example some dialogs have "Cancle" buttons, some must be closed clicking on the "x"-close-button.

There are 5 enrolment dialogs - each is different. From the dialogs I had worked on I got the impression that they more or less use YUI Overlay structure and CSS. From the enrolment dialogs the "quickcohortenrolment" dialog is the only one basing on Overlay. The others are build different.

Please refactor ALL dialogs to offer a consistent interface (look and feel, buttons etc.) and use consistent XHTML, CSS and images.

Please, everybody interested in Moodle Usability and Look vote on the tracker issue - I hope somebody will investigate then.

Eloy, the tutorial you give here shows that my approach to implement the module related information on the course level in the DB and the backup/restore process was not right. But I didn't know that I can implement this information in a course format on module level. And I didn't find examples.

Following your tutorial the implementation looks so simple and logical.

Thanks so much.

Thanks for your detailed answer Eloy.

After I had checked the "after_execute_question" method before asking here I tried the "after_execute_" hooks but without success.

After reading your explanation I guess I need to implement "after_execute_xxx" routines for all modules and correct the database fields with the new IDs the modules have gotten and can tell about in the "after_execute_" method.

Does anybody know a way to use one method to catch all "after_execute_xxx" calls for all modules?

Thank you very much for the background information Tim. There is no documentation about plugin backup as far as I found out. There is the OU Theme DB backup docu. But that doesn't cover adopting ids of course modules after backup.

So Eloy is the only one who knows the details - I'll ping him and hope he may find the time to answer.