Luckily, if you are a Mac user, help is at hand in the shape of CodeKit. Described by it’s developer as “like steroids for web developers”, a statement I wholeheartedly agree with, CodeKit lets you automate and streamline your development process. For jList, this reduces my cycle of change / save / run jsLint / run Uglify.js (if jsLint was ok) to the more manageable change / save. Better still it makes sure I don’t accidentally skip a step in my hurry to complete a change. With many more features such as Less compilation, file concatenation and live browser reloads, CodeKit quickly becomes an essential, time-saving app.
What all this is leading to is that I have now added the CodeKit configuration file I use for jList to the project in GitHub. To quote from the CodeKit help:
When you add a project to CodeKit, the app will look for a file named “
codekit-config.json"in the project’s root folder. If it exists, CodeKit will automatically set up the project to match the configuration file. First, it will apply the project defaults from the file. Then, it will change each file’s settings to match those recorded for that file. (If it encounters a file that is not described, it will use the project defaults to set initial options for that file.)
So, simply dragging jList into CodeKit will give you all of the settings I use while developing it. It’s a simple enough configuration but having it included in the repo is a time-saver and will allow you to easily replicate my process and settings should you be changing jList.
- CodeKit: THE Mac App For Web Developers (incident57.com)