Re: cpdflib instead of pdflib, question?

If cpdflib (or clibpdf from the web pages) is a superset of pdflib, then it probably makes sense to implement it on top of the pdflib support. Otherwise I'd say just implement it as an independent extension. The cpdflib license is highly restrictive (pay for commercial use), so I don't think we should eliminate the normal pdflib support (which I assume has a more friendly license). In fact, because of cpdflib's license, I would be reluctant to include the support in PHP proper. With PHP4, it will be much easier for people to distribute third-party extensions, so I don't think there's any great loss there. (In fact, there's probably a few things that are currently in the PHP3 distribution that should be kicked out into their own distributions once we can do that.) And hey, we've still got two WDDX implementations, we're certainly not unfriendly to contributed code! Jim On May 20, Uwe Steinmann wrote: > I've been considering to add support for the cpdf library > (http://www.fastio.com/) as an alternative to pdflib. > One crucial question is how to do it: > > - start a new cpdflib wrapper from scratch and leave the current wrapper > of pdflib as it is. This would allow optimal support for each lib but > more work to maintain them. > - take over the the current pdflib wrapper and cover both pdflib and > cpdflib, but avoid too many changes to the current wrapper. I feel > like this could be a dead end, since cpdflib has much more features then > pdflib which may not be available throught the pdflib wrapper. > - start completely from scratch and develop a complete new wrapper for > pdflib, cpdflib and possible other pdf creation libs. Is it worth the work? > > I just need some general comments. Maybe experiences others have made > with similar problems. -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net