Writing a bit of PHP tonight and found that if you use parse_ini_file to load an INI file in PHP, there is a slightly hacky way of having double quotes in strings. For example, I tried these:
somevalue = "This ""string"" has quotes"
somevalue = "This \"string\" has quotes"
But none of them worked! Turns out a quick look at the PHP manual reveals a simple (but a bit hacky) solution to this is to define a constant e.g. QUOTE to be “, and use that in the INI string.
// In the PHP:
define('QUOTE', '"');; and in the INI file
somevalue = "This "QUOTE"string"QUOTE" has quotes"
So the “Microsoft Browser Choice Screen Update For EEA Users” has arrived in my list of potential updates. Interestingly though, Microsoft have not selected this update by default. That might put a dampener on Opera’s big day…
So here’s a few useless usage statistics about this website I found using Google Analytics…
Browser Distribution
- Firefox – 58.93%
- Internet Explorer – 15.58%
- Chrome – 10.33%
- Safari – 9.64%
- Mozilla – 2.92%
Flash Usage
- 8.31% of visitors do not report to have Flash installed
Operating Systems
- Windows – 55.95%
- Linux – 29.54%
- Mac – 8.61%
- Android – 4.90%
- iPhone – 0.31%
- iPod – 0.17%
- FreeBSD – 0.06%
- Playstation 3 – 0.06%
- Blackberry – 0.02%
Java Support
Top 10 Countries Ordered By Visits
- United States
- United Kingdom
- Spain
- Germany
- Canada
- Australia
- France
- Netherlands
- India
- Italy
Other Figures…
- 1.23 average page views per visit
- 59 seconds average time on site (yikes!)
- 86.51% new visitors versus 13.49% returning visits
It’s been live for a couple of weeks now, although I haven’t done much promotion of it, so here is word of an “official” announcement of my new portfolio site. Please take a look around and if you have any constructive criticism, feedback or advice, feel free to let me know through the usual channels…
So without further ado, I pronounce www.jamestitcumb.com officially open!
At our company we currently all work on one shared network drive. The source code is not under any kind of source control, which for me is a big no-no. I’d love to be able to set up SVN and us all work of separate repositories and just commit back to a trunk or branch, but our tech manager doesn’t agree. The way I see it, there are two major issues:
- The source has no history – if there is a problem, we can’t roll back
- We overwrite each other’s changes if we work on the same file
How do other people manage this situation? Having source control on the network drive is fine, but that doesn’t solve the problem of overwriting each other’s changes does it… And setting everyone up with VMs or local repos doesn’t wash with the tech manager. Would a solutions such as each having their own checkout and then the shared network drive automatically update work? What about slowness in updating – people making a change and having to wait a while before it takes effect probably wouldn’t wash with our tech team, and committing back every tiny change seems a bit silly.
What about other source control (i.e. not SVN) – do you think it would suit us? I’m open to suggestions, except for Visual SourceSafe. Preferably something that integrates well with Eclipse, and is also cross platform (we use a mix of Windows, OSX and Linux), but something that also works well without Eclipse… tall order perhaps?
