WP Plugin Dependency: CMC 1.5

Comments

1. craig (1 comments.) says:

   3/30/2005 at 5:24 pm

   Mark,
   Could you post a translation for this so us simpletons can understand what you are saying? Thanks! :p
2. Mark (118 comments.) says:

   3/30/2005 at 9:42 pm

   I can be pretty obscure!
   Well, when plugin developers write functions as part of their plugins, or add database tables etc, they need to know whether a previous plugin might have written that table or declared that function in order to prevent serious breakage. This person has started to develop a framework to support future development in the “click” area.
3. Andy Skelton (1 comments.) says:

   3/31/2005 at 12:38 pm

   Craig,
   What I’ve tried to do with CMC is unify the whole click-counter genre of plugins. Why? Because there are so many possible ways of displaying the stats but very few ways to generate them. I thought that if I could create the perfect click counter to generate the stats, other plugins could specialize in displaying those stats: in text (a la Ozh’s ClickCounter), as graphical meters (see my sidebar for that one), as varying text sizes (like Flickr’s list of tags), or anything else you can think of.

   If each of these plugins kept its own private stats table, the server would be doing a lot of extra work, as would the developers. CMC does the one thing that all click-statistics plugins have in common and because it focuses on only counting clicks, it does it very well. I hope is explains it.