Design Patterns in JFreeChart
Design Patterns in JFreeChart
I am trying to find design patterns in JFreeChart -- can anyone suggest some likely candidates?
-
david.gilbert
- JFreeChart Project Leader
- Posts: 11734
- Joined: Fri Mar 14, 2003 10:29 am
- antibot: No, of course not.
- Contact:
Re: Design Patterns in JFreeChart
If you find some, let me know.jfarmer wrote:I am trying to find design patterns in JFreeChart -- can anyone suggest some likely candidates?
I did read the "gang of four" book once, and it was great. But it was like one of those books that says eat healthy food and exercise more - you know it is right, but you ignore the advice all the same.
Actually, someone did mock me once, hinting that I didn't understand the Factory pattern because JFreeChart's ChartFactory class so obviously doesn't use the Factory pattern. In fact, back when I chose the name ChartFactory (2000/2001?) I hadn't heard of design patterns at all, and thought that ChartFactory sounded like a good name for a class that *assembles* chart instances. I should have called it ClassThatAssemblesChartInstancesToSaveYouFiguringOutHowToDoIt. Oh well.
David Gilbert
JFreeChart Project Leader
Read my blog
Support JFree via the Github sponsorship program
JFreeChart Project Leader
Read my blog Support JFree via the Github sponsorship programThe ChartFactory is a factory, there is no doubt about it.
The "holy book" mentions two factories: the "Abstract Factory" pattern, which I actually never used in the real world, and the pattern called "Factory Method". The ChartFactory class is a great example for having many factory methods.
The observer pattern is used in all EventListeners, so you'll find many of them.
The strategy pattern can be found in the various "Block" classes, they use a layout strategy that is expressed via the "Arrangement" class.
The BlockContainer is also a good example for a Composite pattern.
Whenever you add a border to a chart, you are deep inside a decorator pattern.
So dont trust David when he says he does not use or know about patterns.
The book itself only described what sane programmers (at this time) did for years. The reason the book became a success was not for its new and deep insights but for providing the programming community a well-defined set of names for the things each of them did in their daily life. Once they had the common names, it was a lot easier to talk about code.
The "holy book" mentions two factories: the "Abstract Factory" pattern, which I actually never used in the real world, and the pattern called "Factory Method". The ChartFactory class is a great example for having many factory methods.
The observer pattern is used in all EventListeners, so you'll find many of them.
The strategy pattern can be found in the various "Block" classes, they use a layout strategy that is expressed via the "Arrangement" class.
The BlockContainer is also a good example for a Composite pattern.
Whenever you add a border to a chart, you are deep inside a decorator pattern.
So dont trust David when he says he does not use or know about patterns.
The book itself only described what sane programmers (at this time) did for years. The reason the book became a success was not for its new and deep insights but for providing the programming community a well-defined set of names for the things each of them did in their daily life. Once they had the common names, it was a lot easier to talk about code.