WicketPixie 2.0 Dev Blog: Plans for the Future

So in my last WicketPixie-related post, I talked about replacing images with pure CSS. In this blog post, I’m going to practically tell you I will not be working on WicketPixie until further notice.

The backend for WicketPixie right now is just a mess. As I went through it trying to clean it up, I found even more tangled code that basically forced me to add more mess back in. I believe it to be impossible to edit the code in its current state and call it 2.0. Therefore, I am going to back out of WicketPixie development until I have a large amount of time to sit down and either do a rewrite or a major refactor.

Now, this move has one big advantage. WordPress 3.0 will be out soon. Basing WicketPixie 2.0 off of WordPress 3.0 would mean a fresh API to build off of. Also, WicketPixie must be modified in order for it to work with WordPress MU installs. This would not be the case with WordPress 3.0, as WordPress MU is being merged into the WordPress core at this very moment. This along with many other features will make it worthwhile to wait for 3.0’s release.

That’s all then, I can’t wait to start back up developing this awesome WordPress theme again.