Re: XML_RSS seems dated and unmaintained

On Tue, Apr 7, 2009 at 11:10 PM, Martin Jansen <martin@divbyzero.net> wrote: > How does this compare to e > Á߈lMï”—Û{Œhttp://pear.php.net/package/XML_Feed_Parser? > This package is unmaintained as well, but perhaps you are willing to > invest some time into revamping it, probably merging some of your stuff > into it? > > Martin > I'm not sure how I managed to overlook this extension. XML_Feed_Parser is right along the lines of where I was headed. Perhaps we should deprecate XML_RSS with a pointer to XML_Feed_Parser? Anyway, before I offer to take over maintenance, I'd like to extend it to provide the functionality that I need. If I feel comfortable enough with the code, I could probably take it over. So, to that end, there's two things I foresee implementing. First is an automatic namespace extension handler so it will autoload namespace elements based on the xmlns definitions in the XML. So basically if it sees an itunes namespace in the XML definition, try to load support for that namespace. Are there any current pear extensions that have similar types of requirements that I could model from? It seems a bit much to create a new package for each namespace extension (i.e. XML_Feed_Namespace_itunes, XML_Feed_Namespace_wfw). Maybe a single package that solely handles extensions? I'm sure there's a better way. Second, I need to add methods to modify the feed and turn the object back into XML. It seems odd to have a class called Parser to turn it back into XML though. XML_Feed_Parser::asXML() and XML_Feed_Parser::addItem() don't really sound right. Perhaps I could add an XML/Feed.php file as well and still maintain the existing interface for those already using it. However, that does create a problem with the current package name since the resulting package would need to be called XML_Feed. Let me know your thoughts on these items and If all goes well, I could submit my code and we can go from there. Sound like a plan? Thanks, Eric