Urs Hunkler

Hi Barry,

after I read the posting from Roberto #Bobo# Pinna I tried ounce again to build a SCORM package form your files.

I made up an ADL SCORM 1.2 package with the corresponding Metadata. I additionally set the SCORM Type of the Resources to "sco" as needed. Now your example is running fine in the SCORM Player. In moodle i had no API errors at all but some "not implemented" warnings when i quited the exercise. The tracking and the quiz result was correctly displayed in moodle afterwards.

There is no need to modify the imsmanifest.xml when working with the Reload Editor, when you build an ADL SCORM 1.2 package and set the SCORM Type of the Resources to "sco".

great

urs

hello all,

in the developer wiki I started two new pages for the dicussion on "Module and block collection for naming" (just two lists) and "Structure of the CSS File(s)" for the very important aspects of the way how the CSS files are build and the CSS is coded.

In this forum you have already written many thoughts, aspects, proposals. For further discussion and decisions we could collect them in the wiki with the advantage to build up a working base for the implementation of the template and CSS files. And a base for the documentation for later easyer handling of the moodle layout.

It's wiki style to just work into the existing pages - to add, to supplement, to change - if necessary everything. Perhaps you know, every page version is stored in a database, so every step is documented, every mistake can easily be undone.

Can you envision the wiki way to be the way for the development of the CSS for moodle 1.5?

I'm very intrestet in your opinions
urs

hello all,

when martin started this discussion here i collected my snippets and links and made the graphics for my proposal of a possible moodle page layout. i have been working on it for my own moodle design and was looking foreward to the chance to enhance the usability of the moodle css. please have a look at the moodle wiki pages http://moodle.org/mod/wiki/view.php?id=2935&userid=0&groupid=0&wikipage=CSS_Statements_uHunkler

I started a wiki branche [Reforming the CSS] in the developer wiki, because I think we should collect the results of the discussion here in the wiki. in the wiki they can be structured and can still be edited. I have good experriences working with wikis.

what do you think abot my proposal?

urs

hello harald, hello barry,

@harald: I've got the very same errors from moodle and couldn't find a solution for them in any discussion here.

@barry: at the first place thank you very much for your very detailed and helpfull description about packing a scorm archive with Reload Editor. I was able to work through it quite easily.

I tried several ways to solve the problem without success. My last step was to try serving the package through the Reload SCORM Player. While trying to open the package with the SCORM Player it produces a Manifest Error "Manifest file does not appear to be Scorm 1.2 compilant". Hmmm. I build the package with the files you sent me as an ADL SCORM 1.2 package with the corresponding Metadata. The SCORM Player accepted this package - but when the pages are opened in the browser the same error messages as in moodle are produced. Do you have any ideas concerning the reasons of this behavior or better said misbehavior? Could there have gone something wrong with your files?

the software versions I'm working with:
Reload SCORM Editor 1.3
Reload SCORM Player 1.2
Moodle 1.4.x

thank you for your answers
urs

ps. barry, could you please post here the changes in your metadata file you mentioned which correct the problem.

Hello,

being new I'll shortly introduce myself. My professions as graphic / new media designer and e-learning consultant led me to moodle. I am strongly interested in modifying the look and feel of moodle to fit individual or company needs.

My experiences after some times working with the moodle templates are complex - on one hand it's easy to chance things, on the other moodle behaves very inaccessible. Like for example the hard coded font tags.

For this task my solution is to define a basic relative size for the font tag of 100% withthe following lines within the front part of style.php after the body definition:

In Firefox 1.0, IE 6 and Opera 7 this definition of "font" overwrites the font sizes in the html code. (I didn't test in other browsers) So I'm able to specify the font-size within the CSS-file as usual.

greetings
Urs