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?
Sure did, I had already patched in you VM and validator changes to my branch. It didnt look like there was anything different from the original post there. I'm planning on merging my branch into trunk as soon as I'm finished working out the remaining issues related to ticket #32. > 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. Yea, it's going to come down to a question of what the modules are and how they're aquired/used, I think. I'm all for some modular configuration. It makes it more feasible to distribute/share modules. Having the configuration stay with the module, helps keep the module 'modular' and independent. That said, I think it would be a good idea to consolidate configuration within the module but it's an issue I'm not going to be touching until after I've had time to experiment with converting the present Context object into a Registry. -Mike _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
