Re: Package Proposal: Image_JPEG

<sdelmont@zonageek.com> wrote : > >> Is it possible to think a little bit outside the scope of your package? >> i.e. as a way to get an unique IPTC package in PEAR? >> > > This is not an IPTC package. > > This is a full featured JPEG File Format package > > That does involve IPTC information, as one of several blocks of information. > > As such, this package already provides every single feature provided by > Image_IPTC. > > But for several reasons, one of them being the fact that this package is > not just IPTC but the whole JPEG format, there is no simple way of > implementing the IPTC portion of this package using the techniques from > Image_IPTC. > > The only way of putting the two packages together would be to kill > Image_IPTC. And that would mean the loss of a fast targetted implementation. > > I don't think it makes sense to add more complexity to an already very > complex code (have you seen the code?) That's the whole problem. Just like with HTML_Template_Sigma and its "cache" feature, Pierre Alain Joye doesn't look at the code before opening his mouth. Actually, he doesn't even read mails entirely so in the end he thinks he understands, but he doesn't. I suggest you don't loose your time arguing with him, and try to gather enough votes to get your class accepted. > just to be able to "avoid > duplication" where there is no duplication, just an intersection of > orthogonal problems. After reading your explanations, Image_JPEG seems to fit well. Bertrand Mansion Mamasam