It's very early (it doesn't actually do anything yet!) but you can
define groups and get an idea of how the interface is shaping up.
I also wanted to show that I have actually done something on this! :-)
From here my plan is to add group support to the modules, one by one
(forums first), then go back and clean up some of the central interfaces,
graphics etc.
Finally, test, test, test and get 1.2 out well before the end of February.
This includes some significant cleanups to the new course categories
system. The basic idea is that the categories/course browser is now
unified under one system, and admin features related to that have
all been moved into the browser (as little icons).
I'm much happier with this as a foundation that can scale and be
built upon.
Still to go:
- searching
- paging
- polishing
Also in here are a lot of little cleanups around the place, such as
the initial setup process.
OK, some big changes here to the front end, particularly in
course categories and course display.
Course categories can now be nested (to any level).
Courses and course categories can now be manually sorted
any way required.
There is a groovy front end for managing these, and a better
range of options for formatting the front page.
It all still needs some polishing, which I'll be doing over
the next couple of days, including better auto-sorting.
I would not use this on production systems just yet.
Basically all the Database functions are in lib/datalib.php
and the web functions are all in lib/weblib.php, so
moodlelib.php is much thinner than it was.
Data functions have been extended ... most old calls will
still work, but now many more SQL commands can be performed
using the datalib functions rather than using SQL. I'm
currently moving through the whole tree replacing SQL
calls or at least concentrating them in one section of
mod/xxx/lib.php
Still working on forums, quizzes, surveys, resources.
The tree is currently not full working ... some things are
half-completed ... will resume tomorrow.
gmdate to format times, thus allowing it to take advantage of locale, if set,
to print dates in the appropriate language. Several userdate invocations
had to be changed, though, to use the different formatting specs.
