module.ini has always bothered me too. As you said, the only "real" (current) use for them is enabling/disabling a module. This could certainly be achieved more efficiently than reading and parsing an ini file for each module we hit!
That said, just thinking about moving towards a "Registry" object instead of AG_ constants, maybe module-specific config files is an idea we should keep around for the moment, and re-examine when that work happens. --Bob On 6/18/05, Graeme <[EMAIL PROTECTED]> wrote: > Hi, > > My email has been playing up lately so I wanted to check if you got the > diff file I sent on Thursday? > > Okay here is a quick question on the module.ini file. Do we need it? All > that it is used for (as far as I can see) it to determine if the module > is enabled or not. This could be done with a central ini file making > management of individual modules slightly more streamlined. > > > graeme. > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
