July 23, 2008

The time has come for a new update to the my plugin generator; there are new things for 2.6 that need to be included. But at the same time I have been considering changeing the way the plugins work a little bit.

Right now the plugin generator creates code that is all contained within a single class. There are good reasons for this but I would like to abstract some of the code away so that it doesn’t need to be dealt with.

What I am considering is creating a small class library to accompany the plugin template that contains a lot of the code that interacts with WordPress.

To give you an idea of how this would work, instead of creating a function to load and save the plugin settings you would create a new settings class and pass it the name of the settings file. The rest would be dealt with within the class.

Now this is fine when it comes to writing my own plugins, but I honestly have no idea about the level of knowledge and experience that the users of the tool have. Nor do I know how much of the code is amended after it is generated.

So here is my question for anyone that has used my plugin generator, or might use it: Would you be comfortable with this? with a plugin template that comes with a class library?

  every 1737s, 1s ago, in 0.02s.