Re: [Fwd: Re: [WWdevel] feedback e-mail subject line]

[Michael G. <ga...@ma...>]

Hi John,

I think this is a good idea and in fact Sam and Dennis and I once  
talked about ideas for this, although it never became urgent enough  
to implement it.  Putting web interfaces on both course.conf and  
global.conf might be too much of an undertaking and might make it  
difficult to add  new features.  However, what if just course.conf  
had a web interface and the features that course.conf could override  
using this webinterface were fairly limited?

I don't think this would be too hard to implement.  The kind of perl  
constructs that are actually used in course.conf are pretty limited
(just overriding single values or occasionally an array) and one  
could put an HTML form front end for filling out these values.

Then we would hide course.conf in the file manager and create a  
separate module which would allow course.conf to be edited by
the instructor.  In fact the file course.conf might not be needed at  
all -- the override values could be held in
a mysql database table.  This latter approach would involve some  
changes to existing code, but it might not be too bad.

Having global.conf edited through the web via the admin course would  
be quite a bit more complicated and I'd suggest not implementing
that at first.  Once we have a web interface we like for course.conf,  
then we can consider extending it to global.conf

take care,

Mike
On Sep 16, 2005, at 4:13 PM, John Jones wrote:

> So, what do people think about having a web-based interface to  
> setting webwork course/system options?  If done, the values of  
> global.conf could be adjusted through the admin course, and other  
> courses would deal with course.conf.  For making webwork friendly  
> to a wider audience, this would be a big plus.  But, is this too  
> big of an undertaking?
>
> John