Update: Just a quick update for those coming from search engines, the WordCamp Gold Coast website is up and running at: http://2011.goldcoast.wordcamp.org/ head over there for updated information :) – D
Just thought I’d let everyone know that we’ve (Me, Bronson, Lachlan and Brent)Â decided upon a date and venue for WordCamp Gold Coast 2011!
Yes, Fantastic news right? But the catch, Well, There is no catch! Other than the fact neither will be announced until we’ve got everything finalised and deposits paid.
So sit tight, It’s a-happening ( October – Novemberish ), We’re currently in the paperwork section of a few things, so once we’ve got our website up and running with details of the event I’ll be posting another update to give a callout to potential sponsors and all that jazz!
Also, Don’t forget about the Brisbane WordPress meetup’s, Â being held monthly, we’re getting a nice flow of regular users, Designers, Developers and everything in between now, The next meetup is the 7th of July at the Edge in Southbank Â and is more than just a Evening meetup, We’re planning a full day of workshops! It’ll consist of a drop-in session where people can come along and chat with WordPress people, Network, get some tips on their own sites, people are putting their hands up to help out with marketing your website, etc, so it’s looking to be a great day for those of you who might only be able to spare an hour or 2 at some point on your Saturday :) Â (But if you’re one of the few that only comes along for the evening chats in the Pub, I’m sure we can still accommodate you :))
>svn blame http://core.svn.wordpress.org/trunk/license.txt@HEAD 7131 ryan GNU GENERAL PUBLIC LICENSE 7131 ryan Version 2, June 1991 7131 ryan 10085 matt Copyright (C) 1989, 1991 Free Software Foundation, Inc. 15668 scribu 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA 10085 matt 7131 ryan Everyone is permitted to copy and distribute verbatim copies 7131 ryan of this license document, but changing it is not allowed. 7131 ryan
So, Most of have seen that, and a few of us have had a need to parse it now and then.. Googling for an answer never seems to bring up a reasonable answer either.. So here you have it, an explanation of the output format of SVN Blame.
Honestly, It’s quite simple, it’s just fixed width columns, with a twist, by default the columns are 6 characters wide, but will expand to fit the largest revision ID, or the longest committers username. The author’s field is followed by a single space, and then, the line data.
Why go to the trouble of this? Well, It comes back to the fact that although it looked like fixed width.. it couldn’t just be fixed width.. and what rules are behind it? I checked the source of svn blame and this comment was what I wanted to know how the fixed width was selected:
/* The standard column width for the revision number is 6 characters. If the revision number can potentially be larger (i.e. if the end_revnum is larger than 1000000), we increase the column width as needed. */
Updated Regular expression: (Original had a bug where it didn’t handle empty lines in the file)
preg_match_all('!^\s*(?P<revision>\d+)\s+(?P<author>.+?)( (?P<data>.*))?$!m', Â $output_from_svn_blame,Â $matches,Â PREG_SET_ORDER);
array 0 => array 'revision' => string '7131' (length=4) 'author' => string 'ryan' (length=4) 'data' => string ' Version 2, June 1991' (length=41) 1 => array 'revision' => string '7131' (length=4) 'author' => string 'ryan' (length=4) 'data' => string '' (length=0) 2 => array 'revision' => string '10085' (length=4) 'author' => string 'matt' (length=4) 'data' => string ' Copyright (C) 1989, 1991 Free Software Foundation, Inc.' (length=56)
It’s probably not the most efficient, but it does the job for what I needed for now. Also note, I’ve removed the numeric keys from the example output there (preg_match returns both named and numeric results in the array set)
Last weekend was WordCamp 2011, Lots of things were said and done, there was an afterparty that not many talk about (and many suspect the organisers were still drunk the next day), and of course – there were talk from a lot of interesting people.
But of course, this isnt to write about those people, the events, or anything else, this is purely a post to post up a few things which I mentioned.
First part, My presentation: How to become a WordPress Surgeon: An introduction to WordPress Core Contributing. – in reality, it was decided 5 minutes before hand the content, so give me some slack :)
Direct Link: http://wcmelb.blip.tv/file/4826938/
Now the links I promised:
- Search and Replace – An excellent plugin for replacing text throughout WordPress, good for updating old links from other domains
- Core Control – A Plugin of mine which allows you to see inside a bit of WordPress, The main use for this today is determining which HTTP Transport is in use, and the ability to disable those which are malfunctioning.
- Theres another plugin which is useful when changing permastructures to distinctivly different structs, in most cases the canonical redirect takes care of it, but it’s not 100% perfect, I cant find the plugin, but Advanced Permalinks looks like it’ll do the job, But might not be compatible with 3.0/3.1, and might be overkill really.. but search the Permalinks tag on the extend directory and see what you can find.
And links that are just awesome:
- How to DOS a Developer – How to help out reporting issues to developers