OK, so some among you may be starting to wonder if stripShow is a dead project. I assure you, it’s not, I’ve just not had a lot of time to devote to it for the past few months.
But I’m back, and ready to get this release out the door. One of the things I’ve been doing is ensuring that stripShow 2.0 works with WordPress 2.7… and it does. But I’m starting to realize that my original idea — to file stripShow’s menus semantically among WordPress’s own rather than lumping everything under a “stripShow” menu — might not be the best method, at least if I don’t want to go insane documenting how to use the software and taking into account all the various menus in the various versions of WordPress. So I’m exploring how best to lay out the admin menus without having to provide three sets of instructions.
Changes coming in stripShow 2
OK, so some among you may be starting to wonder if stripShow is a dead project. I assure you, it’s not, I’ve just not had a lot of time to devote to it for the past few months.
But I’m back, and ready to get this release out the door. One of the things I’ve been doing is ensuring that stripShow 2.0 works with WordPress 2.7… and it does. But I’m starting to realize that my original idea — to file stripShow’s menus semantically among WordPress’s own rather than lumping everything under a “stripShow” menu — might not be the best method, at least if I don’t want to go insane documenting how to use the software and taking into account all the various menus in the various versions of WordPress. So I’m exploring how best to lay out the admin menus without having to provide three sets of instructions.