Jay Hollingum - Works in IT

If you're short on time or lack a certain flair for design, then this may be worth a quick punt at getting a decent layout and design set up for a site quickly. http://www.blueprintcss.org/

Here's a little tutorial about sorting out the colour bleed in Internet Explorer with CSS when using fieldsets and legends. http://www.communitymx.com/content/article.cfm?page=1&cid=DD9F3

Having recently posted about new operating systems for mobile phones and the multitude of platforms that developers would have to develop for it, seems that a whole group of organisations, from network operators to handset makers, are clubbing together to create a common standard that developers can work with. It could be a while before any real progress is made and this tree begins to bear fruit, bearing in mind the hundreds of platforms, software, and hardware that exists already. The original article is from the Guardian and can be found here , where I first read about this being announced at the Mobile World Congress. The press release can be found on Marketwatch . This new consortium's website is at  http://www.wholesaleappcommunity.com .

When Google's web browser, Chrome , first came out, as quick and simple as it was, it seemed to lack a few of the extensions and features that were useful in Mozilla FireFox , especially for developers. Recently though, after having trouble with massive memory leaks in FireFox ( http://kb.mozillazine.org/Memory_Leak ), Chrome got another try out ( Internet Explorer still seems to take forever to load up and feels like its dominating the browsing experience). No surprises in Chrome's simplicity, speed and efficiency, and the way it neatly lets you get on with browsing the web. It also come with nifty little developer tools, showing download speeds, CSS/HTML structure, access to scripts, all of which can be found from the page button link as shown in the video below, using the Page button > Developer > Developer tools link (or key combination CTRL + SHIFT + I). As always it boils down to personal preference and it's good that there is this choice (nevermind the be...

Reading through some reviews and articles of the Mobile World Congress 2010  and seeing Samsung's new Wave phone using their new platform Bada , reminded me of this post about MeeGo , that I made a while ago. The fact is that it is yet another system to develop on and then support, or if the angle of the phone companies is to have a selling point for their phones, whether the average consumer on the street even cares about what operating system their phone uses, unless buying in to a brand like Apple, Google or Microsoft. Developer documentation for Bada can be found at this site - http://developer.bada.com/apis/index.do .

Finally dragged myself in to the Twitter  era with a Twitter account. I'm still unsure as to its usefulness, objectives and what can be achieved with it, and I certainly won't be posting things like "filling kettle with water", "waiting for water to boil", "OMG! Still waiting for kettle to boil water", "Made cup of tea", so on and so forth. At the moment I'll probably just "tweet" new blog entries through it, which i'll mention in my next post and which seems like a pretty good first use as Twitter appears to ultimately be a tiny rapid fire blogging engine. This isn't to say it's totally useless or meaningless and i'm sure after reading  http://business.twitter.com/twitter101 , ideas on how to best use and take advantage of the site will become clear. Anyways, "follow me" on Twitter at  http://twitter.com/jayhollingum .

Sometimes javaScript files need to be sourced in the head of an HTML document; however the >net framework does not appear to update tIf you add a link element into the head of the .Net master page, e.g to use a style sheet, then the .Net framework takes care of sorting out the relative URI resource, so that the correct path for the style sheet is always used. e.g. linking to a style sheet in the head of a master page <link href="StyleSheetFile.css" rel="stylesheet" type="text/css" /> would be automatically converted, if you went in to a sub directory, to <link href="../StyleSheetFile.css" rel="stylesheet" type="text/css" /> However a source used to load a JavaScript file does not behave in the same way and the path remains as defined in the master page. e.g. linking to a javascript file in the head of a master page, no matter how deep in to the directory structure you go, will stay as <script sr...