Tag: PHP

Review: Koding

Standard Koding layout.

First of the two posts I mentioned last time: a review of Koding, the cloud service + Chrome app. What is it? The short answer is that it’s an IDE. But that really doesn’t do this thing justice at all. You can’t actually do anything offline, really, besides fiddle with some very basic settings. That’s because you don’t work on files locally, you spin up a VM (hosted on Amazon) and the IDE connects directly to it for file editing, terminal, etc. All VMs also come with a public URL for you to plug into any browser to run your app if it has a web interface. Who is it for?…


PHP_DDNS – my latest project

While I generally like having no set topic for this blog due to the freedom it gives me over what and when to write, it also means there’s pretty much no chance of regularity to my posts. As you may have noticed, I haven’t posted anything on here for a while and it’s not because I’m incredibly busy – I just haven’t felt the urge to write about anything recently. Well, that changes today. The other day I came across a project called Remonit which is aiming to be the go-to tool for geek-types wanting to have real-time, web-accessible stats on pretty much anything on their devices – from netbooks to…


Developments Of My Developments

I’ve got a few things to cover in this post, all relating to developing web thingies, that I’ve come to realise in the past few weeks. 1. Codeivate I recently discovered a service called Codeivate which basically has a bunch of plugins for popular editors/IDEs which track your activity and report the details back to their system. This lets you see the types of files you work on and how long you spend typing at once,  which can give you some pretty great insights into your focus levels and typical workflow. It also awards you EXP against each file type which level up, and contributes to your overall level – so you feel an…


Because Debugging Into the Page is Bad Practice

Because I run into issues of locating debug output or messing up element placement it’s bad practice, I wrote a Sublime snippet to help me output stuff from PHP into the JavaScript console! To get it: open Sublime, then Tools > New Snippet… and paste this Gist over the contents of the snippet template. To use it: make sure your current syntax is PHP, type clog, hit enter, and type the output you want to display. It uses JSON so feel free to throw objects or whatever at it, though be aware of property visibility with objects.


More On The Thing I Recently Found Out About PHP And Think Is Ridiculous

If you a) haven’t read the precursor to this post, and/or b) don’t know about OO property visibility, you should start off by reading this piece of literary genius. Following on from my last post, it turns out that even after making a magical function to expose inaccessible properties of an object the empty() function will still return false. Even if isset() is returning true for you in the code, it apparently returns false when empty() calls it unless you have the magical __isset() in your class – even with the magical __get() already there. All of the sense has been made. Not.


A Thing I Found Out About PHP The Hard Way And Think Is Ridiculous

So PHP has some pretty helpful native functions like isset() and empty() which can be used to check if a variable exists and if it has a value, respectively. For those of you who don’t know, if you try to use the value of a variable that, for some reason, doesn’t exist at that point in the code your users will see a lovely error right on the page. Say if you have optional fields on a form, you can use isset($_POST[‘my_optional_field_1’]) before trying to get it’s value – because if the field was empty on form submission then my_optional_field_1 won’t be in the $_POST variable and you’ll generate an…