Recently I was working on an e-commerce website that had a custom modal box show a Youtube embed. The Youtube video is embedded using an iFrame (seems to be the best approach for embedding) and a close button need to be absolutely positioned above the video to close the modal.
After scratching my head for what felt like ages, reading documentation I found the solution. Append ?wmode=transparent to the end of your video URL, see below for an example.
I recently worked on a project where the wonderful jQuery Isotope plugin was needed to sporadically reposition items for depending on the height of the browser and the size of each item being positioned (in my case, unordered list items). Everything was going well, looking great in Firefox and surprisingly IE until I had a look in Google Chrome.
Basically what was happening is that some of the items are being stacked on top of each other and looked completely broken, sometimes several of these items would stack. The fix? Well after much trial and error the following code in the main JS script on the site within a DOM ready call was all that was needed. The issue is due to the fact that Isotope applies before everything has loaded, so waiting for the page to load before applying fixes the issue in Chrome and any other browser.
There seems to be a lot of outdated code out there from WordPress 2.x days on how to redirect a user to any page of your choosing after logging in, the below code will redirect a user to the homepage directly after logging in without taking them to the usual admin panel (in-case you have a custom page you want users to see).
This post is more of a self-reference for future projects, but thought I would share.
I am a developer, not a designer/developer which to me is a fallacy. There is no such thing as a designer and developer, you’re using two different parts of your brain for both tasks. You’re either a design or you’re a developer. Anyway, that discussion is for another time.
Having said that, recently a music blog I operate needed a redesign and because I am cheap and like making things hard on myself, I decided to re-design the entire site myself. You all know my stance on web design, so naturally I used Adobe Fireworks and not Photoshop to design the site.
I think the last straw has been drawn and I’m no longer going to use Firefox as my default web browser any more. The rapid release cycle decision only played a small part in my decision, the main reason is the fight to remove versioning numbers from the browser about box, seriously?
Instead of talking about things of substance, there is a current debate whether or not to make Firefox a versionless web browser and just show if you’re using the latest version or not in the about dialogue instead of the version number, the version number will still be available but not shown in the about dialog any more.
If there is one thing that I could name besides the extensible plugin system that I love about WordPress it would have to be the theming and templating system. Most of my projects consist of using WordPress or Codeigniter, and one thing that I find myself wishing Codeigniter had was a template and theming library that worked similarly to how WordPress works.
WordPress works on the premise of the following files’ header, footer, sidebar and index page as well as the existence of a style.css file that defines the themes meta info such as the name, description, author and descriptive tags. If Codeigniter had something like this in the form of a library, that would be awesome.
Codeigniter’s lack of an authentication system is both a blessing and a curse. The blessing is that you don’t need to conform to a pre-written and and conventionalised auth library, the curse is that writing your own can cause severe headachaes and countless hours of developing something that comes standard in most other PHP frameworks.
I am a huge fan of CakePHP’s authentication library, it has an ACL and Auth system baked in, which works really well and is super extensible, but the framework itself is a proverbial piece of shit disguised as a PHP framework.
This post is not against electric vehicles, I’m all for electric vehicles, but sadly a lot of people don’t truly understand what eco friendly means. Non-harmful and respectful of the environment and its inhabitants, not emitting pollution into the atmosphere. If you think electric cars are truly eco friendly then you’ve been had.
Every touts electric cars as being the better alternative and the bonus is they reduce our dependence on oil (which is an awesome thing). However people fail to take into account that electricity is still produced in quite a of countries by non eco friendly means. Not every country has nuclear power (even that can cause troubles with the environment). Australia amongst others rely on coal for electricity generation.
There was an explosion at a factory in Taiwan last week, the factory just so happened to be a Foxconn owned factory that manufactures Apple parts including those for the new iPad 2, did you hear?
Apparently 3 people died and 15 were injured, but wait… DOES THAT MEAN WE ALL HAVE TO WAIT LONGER FOR AN IPAD 2 NOW!!!!?
That’s what everybody seems to be more concerned about. Never mind 3 people lost their lives, never mind they probably had children or wives/husbands at home. All everyone seems to be concerned with is a delay to the iPad 2 manufacturing process. Seriously, what the fuck?
It’s amazing the difference a year can make. This article is pretty outdated now, I’ve since written a follow-up which addresses the comparative points of both frameworks a little easier and in-depth. Both frameworks have evolved since I wrote this, check out the updated comparison here.
I’ve been getting a lot of traffic off Google from people searching “Codeigniter vs FuelPHP”, so I thought I would write a post explaining the advantages and disadvantages of each. Whilst FuelPHP might appear to be a new kid on the block, the similarities between Codeigniter and FuelPHP aren’t that much in terms of performance, coding or speed.