-- Philip G <guice...@gmail.com> wrote (on Tuesday, 27 October 2009, 10:44 AM -0500): > You're right, it's a simple format for simple configuration. My issue > is Zend's and PHP Group's hacks into the INI format trying to force it > to do things it was never designed to do. No different than using a > flat-head screwdriver when the screw was designed for a phillips-head. > Doable, but a pita. (not to mention you're looking at a future of > readability and maintenance nightmares) > > My point is Zend needs to switch off INI now. ZFW and it's > confirmation structures have gotten far too complex to be handled > within any INI file. We need to stop adding in more hacks into the INI > format. We need to start saying "you can't do that in INI, use XML" > instead of the other way around (eg: constants - took them years to > get constants into XML).
Listen, this is your opinion. The fact is that ZF has been built from the ground up to accomodate the opinions of *many* people, and to provide flexibility to allow developers to develop as they want. If you don't like the INI configuration adapter -- don't use it. But don't tell others not to use it if they prefer it. > Tutorials, examples, everything (unless specifically talking about > INI) need to be converted to XML. Need help? I can do that - I just > need to know how to make and submit documentation pieces. The fact is that INI is perhaps the simplest format for many developers to grok, and this is why we use it in the examples. It's a very succinct format, unlike the nested hierarchies of XML which are more machine-readable than XML. At best, we'll consider providing examples in each format -- but don't expect to see the INI examples disappear any time soon. > INI is a simple format. It works for simple "name = string" confirmation. But > when you need a real configuration format, able to handle arrays, custom > namespaces, nesting, XML will be right here waiting for you. :) > > (On a side note, I think PHP's XML parser needs to be updated, too, to > properly > parse XML files based on DTDs or WSDLs. When a WSDL *says* return is always to > be an array - PHP needs to parse the string as an array. :( ). > > --- > Philip > g...@gpcentre.net > http://www.gpcentre.net/ > > > On Tue, Oct 27, 2009 at 4:27 AM, Karol Grecki <kgre...@gmail.com> wrote: > > > INI is simple and simple is good. It's a config format for PHP itself, > people > are used to it. > If simple doesn't cut it, choose something else, it's entirely up to you. > And if you want to shove XML down someone's throat, switch to Java ;) > > Karol > > > Philip Gabbert wrote: > > > > In my opinion, I think XML should be the recommended route. Using some > > obscured version of a Windows origin configuration file and then > > bastardizing it belong belief to add functionality is the entirely wrong > > way > > to go. > > > > XML and the newly added ZendFW XML namespace (in 1.9) is the right way. > > That's what XML was built for. Not INI. > > > > We should be discouraging bad practices. Bending a format into a > direction > > it was never meant to go is not a good practice. > > > > --- > > Philip > > g...@gpcentre.net > > http://www.gpcentre.net/ > > > > > > -- > View this message in context: http://www.nabble.com/ > application.ini-adaptation-for-php-5.3-tp25993786p26074544.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > > -- Matthew Weier O'Phinney Project Lead | matt...@zend.com Zend Framework | http://framework.zend.com/
