Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0

Request #12792 Throw out JPGraph for a new lib
Submitted: 2007-12-28 23:32 UTC
From: dufuz Assigned: dufuz
Status: Closed Package: pearweb (version CVS)
PHP Version: Irrelevant OS: NA
Roadmaps: 1.18.0    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 12 - 2 = ?

 
 [2007-12-28 23:32 UTC] dufuz (Helgi Þormar Þorbjörnsson)
Description: ------------ JPGraph is old and we need something fresh that's PHP 5+ and actually updated. ezcGraph is a good candidate IMHO, Image_Graph simply isn't being maintained, I talked to Jesper briefly in November this year and he promised to start fixing bugs but he's very much so strapped with time. If anyone wants to use Image_Graph over ezcGraph then please let me know so that it can be discussed else I assume we'll go with ezc

Comments

 [2007-12-29 10:26 UTC] wiesemann (Mark Wiesemann)
Just FYI: There is PHP 5 version of JPGraph that is maintained and that is 99% API-compatible to the PHP 4 version.
 [2007-12-30 19:33 UTC] dufuz (Helgi Þormar Þorbjörnsson)
True enough but it's dual licensed, I know we are open source and non commercial and thus we can use it as per http://www.aditus.nu/jpgraph/jpdownload.php but I somehow feel like we should move away to a solution that doesn't keep "advanced" features for people that pay. Perhaps we can start by moving to the PHP 5 version so we at least have a up2date lib and move this ticket a bit back and see if we want ezcgraph or not.
 [2008-01-21 17:31 UTC] dufuz (Helgi Þormar Þorbjörnsson)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.