In the previous blog entries “Orchestrate.io JavaScript Client Library” and “How to Build an NPM Package, Beginning the Symphonize Project” I kicked off a client library project. However, as things go in techlandia, they have changed. Just a few days after I created the project I learned of Steve Kaliski’s project he’d just rolled out on NPM. So he’d beaten me to the punch for a client library! I didn’t want to do a completely redundant project, so it was…
…Pivot Time!
So a quick pivot and I’ve decided to shift what would have been a client library called symphonize.js to a different project. Here’s the new plan. I’m doing the series, to be posted on the orchestrate.io blog with the first blog entry now live at, “Test Data Builder Symphonize.js with Chance.js“. The next entry will go live soon, diving more into the data structures and who, what, where, when and how to use them.
Using WebStorm for Orchestrate.js Hacking
This is a quick video I put together that outlines the steps to get Webstorm IDE setup to hack on the Orchestrate.js Code base that Steve has setup. I’ve assumed in the video that you’ve already downloaded node.js, Webstorm, and got the version of node.js setup in Webstorm already. The second assumption that I’ve made is that you’ve already downloaded the orchestrate.js code base somewhere and are opening it with Webstorm with the open directory option.
http://vimeo.com/adronhall/webstormorchestratejs
References:
- Steve’s NPM Profile
- Steve’s orcehstrate.js Github Repo
- The orcehstrate.js package on NPM
- First article @ Orchestrate.io on Data Generation