Hi,
Sorry, I forgot other people uses prefixes in their databases. Good point!
Well, for our Moodle sites (www.mystudyguide.nl and www.e-study.nl, test.e-study.nl for now) we use 1 block per course. We don't need more.
Programming a block is not that difficult. I won't be very hard to make it working for groups. However you have to change the whole administration area (make an apart table for the subscriptions).
Greets.
Paul
I agree that there should be more things configurable per course. I don't think it would be a good idea to add all these settings to the Settings page of the block. This page contains sitewide settings (and should be set by the admin). The number of hours newsfeeds should remain cached is probably a good example of such a setting.
The other settings (footer, name of newsfeed, url of newsfeed, number of items to fetch, etc...) should be handled by a different settings page (for the teacher of the course).
There is however not yet a standard way of printing this type of config page for blocks.
I thought of adding code that changes the footer of the block to something like 'Configure this block' whenever you log in as a teacher. Clicking on this link would open a form to type in footer, url, number of items, etc....
These could be stored in the same databasetable that is used for caching the rssfeeds. There is however one disadvantage: in the end every type of block will have its own way of configuring and this will confuse users. (Compare it with the modules: clicking on the little editing icon always shows the options for whatever module you are using. There should be something like that for every block too.)
My question to the moodle masters
Is this the way per course settings for blocks should be handled? Or should we wait until a more generic interface gets addded to the blockcode?
