markforster

Heaton park

Sat, 07 May 2011 10:47:19 +0100

Heaton park

I Can Haz Projects

Tue, 15 Feb 2011 00:49:43 +0000

We’ve had an influx of work in the past few weeks at the lab and the work load is becoming a little fucking crazy :S to say the least.

Its all good though coz I thrives under this kind of pressure. Plus the key project I’m on at the minute is an iPhone / iPad app which is turning out to be fucking beautiful. The backend is driven by a CMS and the app pulls that shit right in vi XML and iCal ;)

The frontend is a totally bespoke UI and I’ve relished in designing the UI layer. Its implemented in openGLS and cocos2d although I’ve worked around the out of the box cocos templates as I didn’t find them to be as accommodating to my components design as I needed. Suffice to say, Although the visual design was not my own, I feel that the attention to detail I’ve put into the UX has produced a pretty tasty UI experience.

Unfortunately, for the next week at least, I’, going to have to shelve my excitement and turn my attention to another project.. ..an awesomely massive Drupal portal which should be fun to get my OCD teeth into ;)

Rant and Shit!

Sun, 13 Feb 2011 18:24:00 +0000

* I’m sick of waiting for full HTML5 and CSS3 support across all browsers. Yes, people have been using it for a good while now and as it seems most IE users are finally getting their act together and shifting their shit to 8 (and 9). Its likely that sometime soon we should all be in a position to putting out some awesome websites but don’t hold your breath!

* I don’t have time to update my own website. I wish I had all the time in the world to work on a website skin but I dont! I’m too busy making money. I’m no designer but I’m pretty nifty with fireworks and after 8 years doing this shit I like to think I’ve got some HTML fu! Even if I did though.. ..I’m sick of banging out HTML. ‘ADHD + To Many Projects’ means I’d likely never be happy with the end result and / or finish it for that matter so its best I leave it there.

* I’m not a web designer / developer / deseloper.. ..I’m a software engineer. *translation - I get hard looking at patterns*. Not the knitting kind though! No! The ‘I’ve just cracked open omnigraffle and puked a dirty great class diagram’ kind! In fact I’m not even that! I’m a guy with a pad of ideas who tinkers with things. I want to make cool things. I dont want to be confined to the saturated arena of ‘up your own arse’ script kiddies. Its just the web! its just a document!

* Its getting to easy to put together awesome tools using the web, through the web and If you’ve thought of it, its probably already been done.. twice.. and done pretty well. The webs came along way in only the past three years. Its getting easier than ever to put these things together. If your’e not steeped in cash, or sucking investor dick, then your’e not going to be the cool kids ramping this shit out! sorry!

* I’m sick of the social web. I’m neither social or antisocial. I like to catchup with friends face to face for a meal or a drink. I dont want to be harassed hourly with your verbal garbage. Dont boggle me with your enigmatic wall posts! I’m, not interested in what your’e eating and the 40th set of pictures you’ve just uploaded of your makes me want to rip out my eyes and eat my own face.

With that said, I’ve decided this year to:

1) Stop using twitter. A few months back I deactivated my facebook account. Wow! Liberating + 1 :) Sorry twitter, you’ve lost me. The people I follow are great but personally, I think your’e a big waste of my time. I just don’t get you anymore. Give me something new :( oh! and eat my balls!

The same goes for Gowalla, Foursquare, GetGlue, etal.

2) I’m not interested in doing websites any more. They bore me! I havent got time to keep up with the latest javascript framework or the latest “Works in them all” web templates and frankly I couldn’t care less. I’ll use what I need to to get the job done. When I need to, I’ll build websites. I’ll build them well. I’ll use best practices, do a stella job and never cut corners. I’ll continue to build them as long they’re are bringing in the cash.

3) My true passion is software design. The web is a glorified frontend! (and a very fickle one at that). From now on my interweb efforts will be better put to building websites that work and no more. No fluff or cruft. The internet is an awesomely powerful tool but their are other ports and other protocols *remember that kids!*. Port 80’s been in the lime light to long. Next!

4) My new distraction is mobile! Mobile and API’s.. Distributed Architectures.. Rest, JSON, RPC.. ..thats where my direction will be. Connecting things! Its like lego but betterer

5) My true focus is hedgehog lab. We’ve got an awesome team of talented people and we can do great things. We’re moving into a truly exciting space. This is where the future is!

6) I’m going to start brewing my own cider. The Scrumpy kind. Its become too pricey and for £4.50 I can get about a 10 litre vat full to the brim. Good Times!

Apart from a few additional annoyances, todays been rather cheery.

.. Thats all.

Sort out default zoom in Chrom.. ..Sweet ;)

Mon, 07 Feb 2011 19:27:58 +0000

Sort out default zoom in Chrom.. ..Sweet ;)

Rip iPlayer videos - if you like ;)

Fri, 12 Nov 2010 18:09:30 +0000

Rip iPlayer videos - if you like ;)

Recent Reading List

Thu, 08 Jul 2010 12:49:00 +0100

Unweaving The Rainbow - Richard Dawkins
The Odyssey Of Homer (For The Lulz)

My thoughts on Ritalin

Sat, 19 Jun 2010 13:56:44 +0100

Its not until you see the level of work you push out in four hours that you realise that the Ritalin is taking effect. I’m always surprised an hour into my work, just how productive I have actually become and how much focus I have on a task.

My impulsive tendencies to procrastinate subtly fades replaced by a high level of interest in getting the important complete.. ..a level of calm that makes the sometimes overwhelming depth of a problem clear and approachable.. ..a sharp level of focus that makes completing the mundane, effortless.

When the fog creeps back in and the mind becomes fuzzy, when the urge to defer the boredom and seek out distractions increases, thats when you know your’e due your next fix

Really fascinating rendition of the super mario theme by the...

Tue, 08 Jun 2010 21:08:24 +0100

Really fascinating rendition of the super mario theme by the london symphony orchestra. Catchy ;)

Fixx notifications with google app engine

Mon, 31 May 2010 19:47:34 +0100

I spent a couple of hours this weekend putting together an appengine app to hook into the fixx api. I chose appengine for two reasons: First off, its python and i’m aching to do some python. Our website runs with python and although I put most of the frontend together, I’ve had little say or involvement in the backend. Its all django based which is sweet, but its too far developed now for it to necessitate my input. Secondly, I’m loving the cloud at the minute. google appengine has some sweet infrastructure in place that I really wanted to start tinkering with and as its a bare bones API, it gives me a lot of scope to make something new.

Anyway.. ..So I spent a bit of time a few months back putting together a php wrapper for fixx 1.9 and I’ve only used it in a few places to pull out some arbitrary data into my website but I’ve never really touched it since. It was more of a “Can I Do This?” kind of project. However, reading through the appengine API, the XMPP services immediately caught my eye.

It took about two hours to setup a google app, configure the routes using the google web framework, knock together a few templates and port enough of the fixx API to get out the data I needed to have a prototype notification system in place. Once I had the app pulling data from fixx, pushing it out using google XMPP api was a breeze.

The result? A sweet little chat bot that notifies you when issues have been assigned to you ;)

The current version is a very early prototype, is bound to break at some point and needs a lot of love frontend but still, its possible to register your copy of fixx using a public domain name and allow anybody for that domain to sign in and subscribe to notifications.

The roadmap is a bit up in the air at the minute but the long term goal is to have a bot that will keep you informed of changes to fixx and allow you to pull and push information to and from your fixx instance. The long term goal is to allow commands to be fired at it, for example :

/comment 238 I’ve finished working on this * To comment on an issue *

/log 838 2:40 added some awesomeness * To log time *

/resolve 882 duplicate This issue is a duplicate

..You get the idea ;)

When I’ve got a better idea of the features I’m going to add, I’ll publish a roadmap and drop the code on a google repository. For now, if your’e interested let me know and I’ll make a copy available for download.

Kickass Bluegrass

Tue, 18 May 2010 19:19:43 +0100

While I’m waiting for the ritalin to kick in, I normally find a bit of bluegrass gets me in the zone.

BlueGrass Mix.. ..enjoy :P

Fooling around with fixx 1.9 api

Thu, 12 Nov 2009 10:09:11 +0000

As the release of fixx 1.9 is drawing closer, I thought I’d jot down my thoughts about the new filtering capabilities of changes made to the api and some pointers on how you can leverage it using filters.

Fixx 1.9 has seen a revamp of a lot of the UI, a general polish that tidies up a lot of loose ends left from 1.8.* that we’ve been keen to get in for some time now. I’m loving the UI tweaks and have had a lot to do with some of these improvements but the big thing thats been getting me all excited is the inclusion of filters in the API.

As of 1.9 it is now possible to request issues using filters, something that, for the past few month has caused a headache for me and my work on a set of tools to accompany fixx notibly a time tracking tool and a PM tool to aid issue and release management.

So what can the new filters in 1.9 do that they couldn’t in 1.8.*?

Well for a start, in order to get all issues for a project the usual route would have been

/api/projects//issues

which was ok but didnt filter those issues. If you had a thousand closed issues for this project you’d have a thousand issues returned, something I felt was always a little anal!

Another example, getting issues assigned to a user

/api/users//issues

again, does the job but still returns ALL issues assigned to that user.

So what makes the new filtering functionality cool for 1.9?

well, the two queries above can now be represented as follows:

/api/issues?qProjectId=

and

/api/issues?qAssignedTo=

and of course they can be combined to form

/api/issues?qAssignedTo=&ProjectId=

Another good example is my PM tool that runs comparisons against changes to issues. before filtering I had to pull back ALL issues from fixx every time i ran a comparison which became both a memory and processing hog. Now i can break down my requests into chunks based on project, area, user and resolution as follows

/api/issues?qAssignedTo=&qProject=&qResolution=&qArea=

With multiple threads making small requests, my PM tool now runs smoother and feels like its more responsive almost providing a live feed of changes made to fixx.

One final thing… …for those who have already tinkered with the filtering, you probably have a good idea of how to construct a filter using the querystring parameters.. ..for those who havent tinkered, heres a quick list of the filter parameters you can use:

qPriority=
qCreatedBy =
qAssignedTo =
qStatus = Open | Closed | Resolved | All
qResolvedBy =
qAssignedTo =
qProject =

Note : The following query parameters are reliant on a valid project id. If you pass in a project id and one of the types below is not within the project specified theres a good chance you’ll get no results returned

qType =
qFixFor =
qAffected =
qResolution =

OK.. ..thats about it. I’m going to spend some time tinkering with this and possibly provide some tutorials on how to optimise your’e filter requests and some good practices for using filters. When I get some more time I’ll also start to publish information about my companion tools.

Photo

Sun, 18 Oct 2009 01:37:36 +0100

Name that sound

Fri, 16 Oct 2009 09:12:22 +0100

Name that sound

My New Info site

Mon, 05 Oct 2009 22:47:00 +0100

My New Info site:

I’ve been working on putting together an information site to tie together my social network. Ive totally ripped off tumblrs’ theme but who gives a fuck!

Its no where near complete, needs some serious editing and isn’t really how I want it but its a start.

Toggle Hidden Files in Finder using AppleScript

Mon, 05 Oct 2009 21:15:49 +0100

Tested on Leopard 10.5.6, I totally ripped these solutions from various sources on the net after about 5 minutes of googling.

The solutions below arent great but until I can be bothered to conjure my own more elegant implementation or have time to google further, both are enough for a mac novice to quickly view hidden files/folders without resorting to yet another app to plug a missing feature in OSX.

Solution 1 - The AppleScript Way

Navigate to ‘/System/Library/CoreServices/Menu Extras’ and double tap ‘Script Menu.menu’. This should add a script icon to your menu bar.

Grab the following apple script…

tell application “Finder”
activate
set previous to “FALSE”
set previous to do shell script “defaults read com.apple.finder AppleShowAllFiles”
display dialog “Show Hidden Files… ” & previous buttons {“TURN ON”, “TURN OFF”} default button 2
copy the result as list to {buttonpressed}

if previous is “TRUE” and the buttonpressed is “TURN OFF” then
do shell script “defaults write com.apple.finder AppleShowAllFiles FALSE”
quit
end if
if previous is “FALSE” and the buttonpressed is “TURN ON” then
do shell script “defaults write com.apple.finder AppleShowAllFiles TRUE”
quit
end if
end tell

delay 1
tell application “Finder” to launch

… and save this as “ToggleHiddenFiles.scpt” inside /Users/your-user-name/Library/Scripts folder. The folder may not exist so you will have to create it if it doesn’t.

Solution 2 - The Terminal Way

To view hidden files and folders open terminal and throw the following at it:

$ defaults write com.apple.finder AppleShowAllFiles TRUE

$ killall Finder

…and to hide them again…

$ defaults write com.apple.finder AppleShowAllFiles FALSE

$ killall Finder

Enable tab field focus for all fields on Mac OSX

Mon, 05 Oct 2009 08:29:42 +0100

Enable tab field focus for all fields on Mac OSX

Recent Reading List

Sun, 04 Oct 2009 05:49:25 +0100

A whole new mind - Dan Pink
Getting Things Done - David Allen
Brain Rules - John Medina