Thanks for the feedback Chardelle, I'll do my best to sort out any problems you encounter. Here's some quick responses.
I tried a quick fix for the footer thing in preview release #3 (I've been ignoring it as it only shows up in debug mode, and then only on Internet Explorer) but I've not yet tested it in IE
The help pages are probably the same problem as the frames. Basically anything that isn't a full size web page is going to look silly with a giant header. Shouldn't be too hard to fix just some special case rules in the CSS. I'll probably just hide the header for the frames, and perhaps create a mini-header for the help. (Though to be honest I'll probably also file bugs asking for many of the uses of frames to be done away with as soon as possible too. Frames rub me the wrong way for all sorts of reasons.)
I take it you've spotted the 'logged in as' link in the footer? There is a bit of a dearth of options when it comes to what you can include in the headers and footers without hacking around in the PHP guts of Moodle. My standard, but slightly unsatisfying, CSS hack is to
display: nonethings I don't want to see and this seems to work if you place theecho $menuwithin appropriately targettable container (e.g. div class="hidden"). You could even specify it so that the language menu and the login info appear but not the jump menu or any other combination. It would be nice to be able to specify the exact location of language and login info separately though. (A devious part of my brain is thinking that you couldecho $menutwice with appropriate classes and hide the parts separately but that's definitely getting further into ugly hack territory, especially asdisplay: nonedoesn't always apply to certain accessibility tools).note that the
display: nonehack, which I also used for the menu icons, doesn't actually stop the images etc. being downloaded, it just stops them being displayed. So for performance and clarity your commenting out solution is actually better though it is more work, and it's what I'm working towards generally rather than constantly downloading and then hiding things with CSS.I can't really explain why the Chat isn't working, I've perhaps broken something important in the header? The right frame comes up blank for me in Safari but I'll look into it.
I don't really use SCORM much. Do I need a SCORM (learning object?) in order to test it? Where would I get one?
I've not tested on dialup yet. There's also various web page optimising tools that will measure download size in a more objective manner and give and idea for comparison, though I've not used those either. I'm guessing the theme is fairly lightweight by Moodle theme standards. There aren't that many images and the original Kubrick theme images are actually very well compressed by the original author. Some are smaller than the enrolment key icon for example. Also the fact that they are mostly background images should mean they can load in the background (appropriately enough) without delaying layout of the page. The other images aren't as small (though by no means large) but I'll see what I can do to compress them further once they are finalised. The theme should work without images too for anyone who likes there themes to be really minimalist.