wroolie

Warming up to HTML5

December 15, 2011 by wroolie Leave a Comment

Last week, I finally got around to reading the Microsoft announcements from September about Windows 8 and WinRT. Like a lot of people, I was surprised by the dropping of Silverlight for the Metro UI. HTML5 (along with XAML) would be used prominently.

HTML5 again.

I’m old school and I can’t get rid of the memories of coding conditional blocks of code for different browsers. A lot of web apps would only adhere to one browser because of the different capabilities. In corporate environments, this was mostly IE. The difference capabilities still exists, so I was not pleased about using conditional coding again. Silverlight was a nice hiding place—write once run anywhere (except Linux, and tablets, and phones—okay just Windows and Macs!).

But, things are much better than they were before. Now, we have Modernizr and jQuery. Now we have devices which, for the most part, adhere to one browser only (If I write for IOS, I only have to worry about Safari).

I’m at the point now where I’m excited about HTML5. I’ve taken December off from my current contract to really have a good play with it. I’m very impressed with localStorage and GeoLocation. Canvas is what I’m playing with next.

And, after months of learning Android, I discovered PhoneGap. PhoneGap allows you to host html5 in a compiled application (IOS, Android, Windows Phone) and release it in an app store. It also provides a javascript library to interface with device libraries like GPS, camera, and the accelerometer. I’m struggling with the intricacies of Java (C# keeps getting in the way), but I can do just as much in javascript.

HTML5 allows for mobile apps (web and compiled) and MetroUI.

Once again, the future is bright.

I love coding for WP7

December 8, 2011 by wroolie Leave a Comment

So, I’ve spent ages trying to learn to code on an Android. I’ve read a few books. I’ve got my dev environment all set up. I’ve coded a few test apps and put them on my phone. But the going is slow. If I were a Java developer, I’d probably be all over it.

A friend asked me to do a quick Windows Phone 7 app and I could not believe how easy it was. Since I’ve been working heavily with Silverlight for the past few years, I know most of the code already. I had to do minimal reading to get a full app up and running. It was was nice to work in Visual Studio again. Using Resharper, I was flying through the code.

I only wish more people had Windows Phone 7.

I would get a phone myself, but 3 things are holding me back currently:

I don’t want to be one of 5 people in the UK with a Windows Phone 7.
It’s not open, like Android is. I would be at the mercy of the phone manufacturers for upgrades (like with an iPhone).
It doesn’t have expandable memory (to my knowledge).
My current contract isn’t up until April.

But it’s nice to be able to write apps so quickly (since I spent so much time learning the trivial details of Silverlight). Maybe.

The “View Source” belongs to me too.

October 18, 2011 by wroolie Leave a Comment

For me, the sign of a good web developer (or web application developer) is someone who can right-click a web page to view the source and tell you why he did things the way he did. “I used this div to position this element over here, and used the unordered list for a sub-menu, . . . “

A bad web developer is someone who says “It looks fine in my browser” and “Well, I’m not a designer . . . “

One of the biggest crimes of ASP.net Web Forms was to strip HTML skills from new web developers. They view the source of their code (in the browser—not Visual Studio) as gobbledy-gook. And ASP.net ensures that it is. It’s full of ViewState and control names like ctl_100_className_ctrlName which the developer didn’t put there. It tried to remove the whole stateless-http challenges and make web development accessible to desktop developers.

I’m so very pleased every time I see a new site created with the Microsoft MVC Framework. MVC is making up for the ASP.Net webform crimes. Just like Ruby on Rails or PHP (or classic ASP), it allows the developer to think about what gets sent from the web server to the browser. When I do a site in MVC framework, I can view the source and recognize my own handy-work. I can make full use of CSS3 and jQuery. I know that everything in my user’s browser is something I put there intentionally.

CSS, Javascript, and HTML (along with images, flash movies, Silverlight, or other plugins) are the ingredients of any web application. Server languages like ASP, PHP, and Ruby are only tools to deliver these ingredients to the browser in unique and creative ways. A good web application developer (like a good chef) can look at his source and tell you exactly what everything does. ASP.Net webforms are like ready-meals. Everything is done for you, but you don’t really know everything that’s in it.

Now, don’t get me wrong, I’ve known some fantastic ASP.Net devs who build apps free of ViewState and server controls. But I’ve worked with too many who could drag a control onto a web canvas, set a few properties, and call themselves web developers.

I recently worked on a DotNetNuke project where we customised a third-party component. The page was not rendering as it should. ViewSource gave me a bunch of ViewState and nested tables. I knew of a 100 ways to get css to make the site look the way I wanted, but this wasn’t my source. It wasn’t even the developer’s source—it was the clientIds of the server control. Since I was struggling, a web guy (proper Mac-using, firebug-toting, standards-compliant, web guy) asked to see the source so he could suggest something. When he saw the source, he was mortified. I was embarrassed –“It’s not mine! I didn’t write it.” In the end, I hacked it with jQuery. I didn’t have the sourcecode to modify it properly.

The legacy of Web Forms lives on. Sharepoint 2010 is full of it. Young Microsoft developers (in the last 5 years or so) know nothing but how to use WebForms. (An ASP.net dev told me a few years ago “But I don’t know html.”). But, hopefully, one day we will get around this idea of creating tools that “do everything for you” for developers who should know to do it themselves. Just like I wouldn’t create ready meals for people who call themselves chefs.