Frameworks are growing with every release. Classes are changed, removed and added. In this series I zoom in on some well known projects and analyze their class names with completely meaningless statistics. Now up: Wicket 1.3.3!
To get these statistics, I wrote a script that analyzed all classes. They get chopped up on word boundaries, so for ContextAwareFactoryBean the words Context, Aware, Factory and Bean are counted. From the output I generated a class cloud.
Wicket likes Requests for Pages or Resources
8.47% of the total number of classes in Wicket contain the word Resource. In absolute numbers, 68 classes (of a total of 802) have this word in their name. This is quite a low percentage for the top result, compared to the Spring statistics where the top result Bean is present in 12.31% of all classes.
From the top ten, it’s easy to spot that Wicket is a web framework, with Pages, Web, Ajax and Resources in many class names.
Wicket loves Wicket
A bit remarkable regarding Wicket statistics: about 4.24% of all classes have the string ‘Wicket’ in their name. Relative to the number of Spring classes that have Spring in their name, this is 2.3 times as much!
In general, the class names of Wicket are well distributed. This probably originates in the fact that Wicket is very specialized on one subject and is not a general purpose platform.
Class Cloud (click to enlarge)
Top 10 of partial class names
- Resource: 68
- Request: 62
- Page: 56
- Abstract: 42
- Target: 37
- Stream: 36
- Validator: 36
- Web: 36
- Component: 34
- Ajax: 34
Longest class name
The grand prize goes to: BookmarkablePageRequestTargetUrlCodingStrategy, with 46 characters!
The BookmarkablePageRequestTargetUrlCodingStrategy encodes and decodes mounts for a single bookmarkable page class (source).
Stay tuned for more useless statistics for other well known projects! If you have suggestions for which projects you want to see, please let me know in the comments!