On Thu, 2011-09-15 at 14:42 +0100, John Hodrien wrote:
I think the risk of the KISS approach is that you tend to reimplement everything, because everything everyone else has done is overcomplicated.
I share coding within systems (because it means just a single alternation each time) and have general routines available to all applications. My definition of programming efficiency excludes senseless re-implementations of coding.
It's not that you *can't* do all this yourself, but that you're possibly dealing with life at a layer or two lower than you might. Simply by using an existing library (say jpgraph, but it's chosen at random) you get a load of functionality (that gets improved over time) without having to implement any of it yourself. You're not simply producing a graph, you're producing code that draws a graph and then drawing a graph. Why write the code?
In this instance I would use a GMagick Draw function from with a routine. The PHP coding would be minimal and straight-forward.
Paul.