Claus Witt

How to do a Regular Expression Search Replace with Case Shifting In TextMate

Tue Feb 07 00:00:00 +0100 2012

Recently I had to clone a lot of repositories from BitBucket into a FLOW3 installation. But since FLOW3 expects that packages are named with camelcase, and bitbucket insists on saving all names as lowercase, I need to set the name of the cloned repository manually (instead of just using the last part of the repo url).

This is off course as easy as:

git clone git@bitbucket.org:username/packagename.git PackageName

But since I am lazy, and like to have my software do most of my work, this is what I did.

Locally I created a list of all packages in the FLOW3/Packages/Application directory (which should all be cloned on the remote server).

ls files.txt

Then opened the file list in TextMate, and ran the follow search/replace (as a regular expression)

#Search
(.*)\n
#Replace
git clone git@bitbucket.org:USERNAME/\L$1\E.git $1\n

\L lowercases everything until \E, between those I just pass the directoryname, which is also the name of the repo.

Finally I pasted the lines to the console on the remote server, and presto! All repos were cloned with the correct naming.

JavaScript Module with Global Scope Removal

Thu Jan 26 00:00:00 +0100 2012

Even though I regularly rant about not including jQuery as a default, without ensuring that you actually need it, I have done so myself. However I have done it in a special way (at the time of writing, this is only a proof of concept, and not really used for anything...)

I have a global scope module called "clauswitt", that gets session.js and jQuery added through parameters to the module pattern. This module then removes session.js and jQuery from the global scope, thus making the jQuery code visible only from inside the module, and not callable from the outside.

UPDATE:

As Andrew Cobby pointed out in the comments (see below), you do not need to check if a global variable exists, before deleting it.

And just to clarify - this may not have a valid use case. The reason I created this, was because I got a question about wether it was possible, and how. (A friend of mine had a colleague who always created inline eventhandlers, using jQuery dollar notation directly in the onclick attribute of a button, for instance. This code forces him to - at least - create the code within the scope where jQuery is available).

Removing Unused git branches Automatically

Mon Jan 23 00:00:00 +0100 2012

At work, our git workflow forces every issue in jira to be created in a new tracking branch. The naming convention then makes sure that the release manager can identify issue and code, and their relation.

However this means that either the release manager needs to remove unused tracking branches, or the branche count on our remote repo goes through the roof. Until now, it has been a chore that has been postponed, until today.

My colleague Jesper Rasmussen created an issue in Jira today about creating an automatizeable process to remove unused tracking branches. I jumped on the idea as soon as I saw it, since it has been bothering me for some time.

Google, git and bash to the rescue.

My idea was to create a bash script, make it list all tracking branches which is already merged to master, and then go through that list, and remove all the tracking branches.

The resulting script looks like this

I have a alias for the script and can call it from any git repo I have with cleanupBranches

How to Easily Remove a Prefix from 1800+ Files

Sun Jan 22 00:00:00 +0100 2012

Today I had an easy job of renaming 1800+ wave files which by my own fault had been uploaded to cloud storage with a prefix of 5 digits and an underscore before the correct filename. And since the filename maps directly to a matching objects id in a database, it was imperative that they be renamed, and fast.

I am - as you may know - not one for manuable labour when it can be automatized. So once again I found myself with a simple shell script in bash/zsh

It uses a simple sed regex, with a backreference to the final part of the file name.

Simple node.js Module to Get Distance Between two coordinates

Fri Jan 13 00:00:00 +0100 2012

In one of our latest projects at work, we need to calculate two world coordinates. Instead of going into details about how the calculations is made, I will just refer to this page. This explains all details of math involved in getting distances and/or bearings from lat/long pairs.

I have implemented this calculation in several languages in the last couple of months - both for work, but also for learning details about a language through implementing a known algorithm in it.

Here is a simple nodejs module extracted from the javascript code on that page. The module has one public method called getDistance.

My changes are released licensed under the WTFPL

A zsh function to Add Last Parameter of Last Command to git

Mon Jan 09 00:00:00 +0100 2012

My git worflow often has me changing several files, and testing the changes before I commit anything to any of the files. I find the easiest way to do a commit per file is to ensure that I review the code of each file just before I commit. That way I can also ensure that the commit message is just a bit accurate, as I make no assumptions to what the change was before commiting. (Admit it, it has happened to you too!).

Lazy as I am however, I was tired of writing pretty much the same command twice, or going back in history and changing diff to add before my commit.

git diff Some/Path/To/File.ext
git add Some/Path/To/File.ext
git commit -m "Commit message here"

(Yes, I know I can specify the file in the commit directly, for some reason - I never have). I created a minor zsh function to take the last parameter of the last command, and adding that parameter to the git add command.

gd Some/Path/To/File.ext
gal
c -m "Commit message here"

A Simple Create New Blogpost Script

Sat Jan 07 00:00:00 +0100 2012

As I wrote yesterday I just changed my blog platform from Wordpress to Jekyll. Today I have created some minor tweaks in my setup to allow me to easier create a post, and deploy the blog live. Now I call a simple command in the terminal, with the blog post name as a parameter, and the file is created in the correct place, and opened in TextMate.

And this is how that looks in textmate:

I did a quick search on google - figuring someone else had solved this problem before me - and found this post which was (mostly) what I needed. I have done two minor tweaks to my forked version of the gist he links to.

Changed the template file to _template.markdown
Instead of outputting the filename, open it in textmat

Then I created two small zsh functions to ensure that I can start a blogpost (and deploy my blog) from any directory on my machine.

And finally I fixed a minor thing, where my ruby scripts and, the deploy.sh file was deployed to the website. The following line was added to _config.yml

exclude: deploy.sh new.rb _template.markdown

The last entry in that file is actually redundant. The reason I changed template.markdown to _template.markdown was actually that it rendered a file on the website called template.html which was empty - the fix to change the name could not be used for the script files (well, it could, but I did not want to do that).

The How and Why of my Move to Jekyll

Fri Jan 06 20:45:00 +0100 2012

Today I decided to move my blog from Wordpress to static html files. These files are generated via Jekyll. The first version of this new blog, contains (most) blog posts from the wordpress installation. The included migration script in the jekyll package was used to move all posts to markdown format. All absolute urls to images was changed to relative urls, and all [gist]-shortcodes was changed (via a simple regular expression search and replace in Textmate2) to the standard script-include.

Search: \[gist id=([0-9]*)\]
Replace: script tag with the src: https://gist.github.com/$1.js

I have had this move planned for some time actually. I was tired of the constant surveilance and updating of wordpress (and plugins). And I was tired of the tedious creation and editing of posts. Now, whenever I want to create a new post, I just create a new markdown-file in the _posts folder - all content are also stored in a git-repo instead of in databases. All unnecessary software has been removed from my blog - and only a simple nginx server is used for serving the content. The downsides are simply outweighed by the upsides.

I use a simple two (three if you count the shebang line shell script to upload the changes to my blog.

#! /bin/bash
jekyll
rsync -avz --delete _site/ user@domain.tld:/var/www/rootDir/

The complete installation of Jekyll, move from wordpress and first deploy took me less than one hour. And I love it already. I may need to do some design work at some point though.

Per Package Unit Testing in FLOW3 using PhpStorm

Thu Nov 24 08:37:09 +0100 2011

UPDATE

Do not do this! Check Karstens comment why - and go to his blog post about setting this up correctly.

Everything below this, line is not useful for anything (except perhaps learning that you should not try to create a fix for a problem that does not exist.)

Update: you may add you pear directory as a directory in the project, to ensure that you get them indexed (and get autocomplete on for instance ). On my mac, the pear package is located in /usr/local/share/pear - find where yours is by running:

pear config-show |grep "PEAR directory"

At Arnsbo Media we don't do unit testing on everything. Whereas for some projects (mostly containing models, views and controllers) we feel unit testing [and tdd in generel] is overkill - other projects (or some modules/packages) are prime candidates for tdd. Typically when we are creating service integration we do it test driven. My own definition is that when all users of a given package/module are other packages/modules - and not databases, webservers, end users and so forth - unit testing is a viable way to ensure longevity of the APIs, and solidity of the implementation.

At the moment we are doing several parts of a very big system in FLOW3. Each part is an independent package, and most of them are service layers, and/or abstractions of external systems. Each of these packages should be testable without depending on other packages (apart from the ones required by flow3). Thus we use FLOW3s built-in test framework (based on phpunit), but we have placed our own configuration and bootstrap for testing a package as part of the package.

It makes several assumptions however:

The package is placed in the directory FLOW3/Packages/Application
The FLOW3 packages are placed in FLOW3/Packages/Framework
Phpunit is installed
VfsStream is installed

The layout of the package is pretty standard.

We have created a Build/PhpUnit directory in which we place the configuration file, and the bootstrap for the package. These files a copy-paste-able to any package. The content of both are copied from the framework supplied files in FLOW3/Build/Common/PhpUnit - and tailored to be used from the packages directory. For both files the only thing changed is how to resolve the directories from the current file. Otherwise everything is left as is.

After this all you have to do is setup a Run Configuration for PhpStorm.

All tests are placed in the Tests/Unit directory, and as a rule of thumb I place them in a matching subdirectory to where the class being tested is under the Classes directory, and name it by appending Test to the class- (and subsequently the file-) name. In this case we have a single GoogleHandler class, and a test for it.

Finally all you have to do is run the app using the phpunit run configuration, and you test results are ready for you.

A Simple ViewHelper For FLOW3

Tue Nov 15 14:56:22 +0100 2011

For some time now I have wanted to use FLOW3 for work-projects. However it was not until it recently got out of the alpha/beta cycle that we decided to use it for a critical project.

Mostly for fun, I just now finished a simple viewhelper which is a very simple version of the rails method distance_of_time_in_words. My viewhelper is much simpler than this, and were created in less than twenty minutes. I might however implement the Rails conventions since I quite like them.

As always I have created a gist where you can find the code for it:

The usage is as simple as all other FLOW3 view helpers. First include the namespace, and then call the viewhelper by name. Call it with either a DateTime object, or a string which it's constructor accepts, otherwise an exception will be thrown.

{namespace c=ClausWitt\ViewHelpers}
<c:ago date="2011-11-15T18:15:44+01:00"></c:ago>

At the time of writing, the above outputtet: "3 hours from now".