We have finished our version of Moodle for the iPhone. It is not an iPhone app but we have made it look like one.
The script uses a PHP script to determine the User Agent. If the User Agent equals “iPhone” then we tell Moodle to load the iPhone stylesheet.
Most jobs require tools. Plumbers need wrenches, joiners need saws, accountants need calculators, hairdressers need scissors. But what does a Moodle Developer carry in their toolbox?
This will differ depending on your Operating System but in terms of functionality, how many applications does a Moodle developer really need?
Following on from my iPhone detection script I have added the Windows CE User Agent. When Moodle detects the WinCE browser tag it loads a new stylesheet called wince.css.
Every Moodle administrator/developer has daily tasks that they perform.
Although many jobs can be automated during the cron there are often small jobs to do that can accumitively take up a lot of time.
I needed a to-do list system that would collate all my daily Moodle tasks and display them on one page.
To upgrade or not to upgrade? That is the question.
Well my answer is…upgrade!
I am currently in the process of writing a short paper on a possible upgrade to Moodle 2.0 for Leeds City College. I am proposing an upgrade during the summer.
Unfortunately, due to the size of the organisation, our custom tweaks, third party plug-ins and staff training needs, an upgrade isn’t going to be easy.
This blog post will be part of several posts during the run up to D-Day! Or M2-Day as I’ll call it.
Today I created a Moodle Task List (MTL) which further enhances the custom MyMoodle page.
The Moodle Task List works by checking a series of database queries to see whether or not a student (or staff member) has completed a certain activity or visited a certain page.
The queries are modular and extra queries can easily be “bolted” on to the list.
This task list will work great for our inductions at the start of the new term. The list will prompt the student to do the following: