blog.martincrockett.com

Here’s a list of extensions I’m running for Firefox:

• DOM Inspector 1.0
• Web Developer 0.8
• iview 0.8
• LiveHTTPHeaders 0.9
• Magpie 3.1.1

That’s all for now.

Fitted new front and rear at 9385 miles.

Review here.

Fingers crossed!

Even if a lot of operations can be done directly from the Windows Explorer, it is still necessary, sometimes, to open a DOS prompt to perform a particular task. Typing the full path of a directory can be really annoying. Recently, I’ve learned a way of starting a DOS prompt with its current directory set to a particular folder The following steps will show you how to add an entry in the pop-up menu that appears when you right-click on a folder from the Windows Explorer. Selecting this entry will open a DOS prompt with its current directory set to the folder you just right-clicked.

1. Open your registry (regedit)
2. Go to the following key: HKEY_CLASSES_ROOTFoldershell
3. Add this key: CmdPrompt and set its default value to: “Command Prompt”
4. Under this new key, add the following key: Command and set its default value to: “c:/windows/system32/cmd.exe”

You should now have this tree in your registry:

That’s it. Now, whenever you will right-click on a folder, the pop-up menu will contain an entry called “Command Prompt”.

My Security Clearance for UK Government work is BC (Basic Check) and expires on 26/07/2012.

Wow.

Found some good points on a Sitepoint forum, made by one of the PHP London user group members:

1. Shared code ownership. It forces code review and cooperation, rather than a single person owning a package and effectively freezing it. Anybody is allowed to edit your code. If that frightens someone then an examination must be made of their motives.
2. No attribution of authors. If there is less vested interest in the codebase the goal becomes the utility of the library and nothing more.
3. Completely archived discussion during construction. People are more willing to allow people the free editing of their code if they talk to them often. No rudeness and no private e-mails.
4. If nobody understands something out it goes. Code has no reuse if nobody ever reuses it. That means examples or docs or the writing of stuff thats intuitively obvious.
5. Refactoring by someone other than the person that wrote the first draught. It forces two people to have written everything and means that there is some redundancy if someone drops out for a bit. Libraries written by a single person tend to be quirky.
6. Fine grained unit tests shipped with the code. You cannot refactor without them and they reduce necessary documentation by effectively providing interface examples.
7. Always responding to users comments. Usability is important and you only get this from the users. The customer doesn’t always know best, but being forced to justify a position also forces a constant reevaluation of it.
8. A clear tiering of code from stable down to experimental.
9. Refactoring to reuse other library objects. There is a limit to this because you don’t want to force people to use the whole library for just a few classes. If the library were decomposed properly the issues should not be major.
10. No framework stuff.

Sitepoint

Magpie 3.1.1 – very cool and useful. Ctrl + Shift + S grabs all linked images on a page.

Magpie 3.0 (formerly known as Tab Downloader) provides a number of tools to make media collection more efficient. It can save files (images, movies, whatever) that are open in background tabs automatically to a time stamped folder, as well as saving all links on a page of a particular type. This makes it very easy to bulk download images from websites. Also included is a URL Interceptor to strip valid URLs out of CGI redirects, and a numeric digit flipper for the page location.

Magpie

I managed to get around to updating my development area. I’m running Mantis BugTracker 0.18.3.

Mantis BugTracker