A New Workflow

After an interesting discussion on twitter with @curtismchale, @ericmann, @mikeschenkel, and @rarst I have decided its time to have another look at “local development”.

The basics so far have been the following downloads:

  1. Tortoise SVN
  2. Git
  3. WampServer
  4. PhpStorm

Tortoise SVN and Git are for the version control aspects of this project; WampServer (since I am testing on a Windows PC) is for the “local” environment; and PhpStorm is a recently discovered IDE that ties all of these together.

The next step was choosing a plugin and theme as well as setting up WordPress, my preferred CMS for development. I chose to go with the Nightly Builds version of WordPress, keeping it up to date via the core subversion access.

The plugin and theme are respectively ‘BNS Theme Add-Ins’ and ‘NoNa’. The first, a new WordPress plugin I recently released; and the second, one of my WordPress Themes due to be updated. To test the version control aspects these are now being maintained via github.

Although it has been a bit of a stumbling, grumbling affair I am finding the mix of these tools to have some interesting potential. I have been doing most of my current development work on “live” test servers (all I need is access to the Internet) and have always found everything goes quite well.

Transferring an existing project into the new process goes along these lines:

  1. Download existing project via FTP into the local environment folder.
  2. Share the new plugin/theme with GitHub.
  3. Develop and test in local environment.
  4. Deploy to a test server for online testing.
  5. Commit/push changes to GitHub.
  6. Repeat steps 3 through 5 as needed.
  7. Release to the appropriate WordPress repository.

Starting a new project would work in a similar fashion … maybe.

The discussions on twitter gave me reason to reconsider local development so I will give this some time, namely the 30 day demonstration period attached to PhpStorm. If all works out I may just spend the $99 for the application and make this my new workflow.

Revenue is a big carrot to ignore, especially when its potential is removed altogether.

BNS Theme Add-Ins 0.1 Live

Sometimes I look for any reasonable excuse to post; this one is just to hard to pass up as a new “status” post.

The following is from one of the newer Plugin repository enhancements: an email notification when an update is made to a plugin you contribute to.

Revision
445926
Author
cais
Date
2011-09-30 22:30:33 +0000 (Fri, 30 Sep 2011)

Log Message

Added Paths

Diff

Property changes: bns-theme-add-ins/tags/0.1

Added: bugtraq:number

Added: bns-theme-add-ins/tags/0.1/bns-child-theme-add-ins.php (0 => 445926)

Long story short: the first iteration of “BNS Theme Add-Ins” is now available on the WordPress Extend Plugin repository.

 

BNS Theme Add-Ins

Although it started more as a “Mallory-Everest” idea, I just submitted to the WordPress Extend Plugins repository the “BNS Theme Add-Ins” plugin. My 11th submission!

It is a collection of functions and code that can be used to extend the capabilities of WordPress Parent-Themes and Child-Themes. Current functions:

* Add BNS Extra Theme Headers
* Add BNS Child-Theme Version Control
* Add BNS Readme Menu Item
* Add BNS Changelog Menu Item
* Add BNS Child-Theme TextDomain and i18n (translation) support

Although I did offer to release each of the above functions individually, how I optimized this initial release (read: alpha version) requires the code to remain intact.

I usually make these announcements on BuyNowShop, but this plugin quickly became very special as I utilized more advanced code techniques as well as core functionality I have not implemented in the past; and I just didn’t want to wait until it get subversion access.

Besides, this seemed like a great “Aside” post to make.

Enjoy!

Week 39: Back At It

Last week was an interesting vacation; not what I expected nor had in mind but for the most part it was productive and we accomplished a few things that needed to be done.

Due to an unforeseen and most definitely unexpected accident we replaced our walk-in closet shelving with some much more sturdier industrial style racking. We also seem to have increased the open floor space in the closet, too. No pocket change for the racking (~$600) but well worth the peace of mind and additional space. The do-it-yourself aspect also made the project less of a chore and more of an accomplishment.

Unfortunately our hapless cat Roo will not be venturing into that closet anytime soon. It was one of his favorite places until he was buried under seven feet of clothing and a myriad amount of boxes and what-have-you items that were stored on the top shelf.

No worries, Roo is physically fine … just a bit nervous; although to help entice him back into his favorite haunt we made sure to allow for a special space and a brand new cat pillow for him to safely sleep on.

Now, re-charged and ready for more fun and games I am getting this week off to a start by catching up on my correspondence and other items of note.

I’ll see about getting some pictures posted … maybe I will even catch one of Roo in his new bed, too.

Not Again?

Only 12% of people solve this in under 30 seconds …

Say the opposite of these 6 words:

  1. Always
  2. Coming
  3. From
  4. Take
  5. Me
  6. Down

Arrgghh …

… well, enjoy it while you can!

Compliments of a random tweet.

Hazelnut

I have added this flavor to my regular selection of coffees. Although I was not overly impressed with the first cup, this is one of those flavors that grows on you. The only reason I actually tried this blend more than once was due to the fact I really like the flavor of the actual nut.

I usually only pick up a few K-cups of Hazelnut from Timothy’s but that satisfies my palette for this nutty flavor with hints of … something. The something is really the reason I keep drinking it; I’ll sort it out one day.