This is the first part of a new application I am creating using Node-RED on BlueMix. With very little programming, I show how you can get a basic URL rating application up and running very quickly using Node-RED. In this first part I focus on the two primary web services, posting a rating and getting a rating for a URL.
Quick Tip of the Day – don’t have a mobile device? Then use Chrome to test your responsive design on many kinds of devices! I have used this technique specifically to test what the site will actually look like on a mobile device. Even though responsive designs “work” when you resize the browser, sometime it’s not perfect.
This has really changed the way I work and doing mockups and proof of concepts. Check out the new Tip of Day video to see how you can edit the CSS for a website live using Google Chrome and the developer tools.
I have a lot of bookmarks and many times when I am working on a project or doing some of my own personal things I like to have a “workbench” of tabs open in Google Chrome. I use this both at work and at home. For instance, at work I have many IBM Connections communities I would like to read the news from or contribute to so I have a folder of bookmarks for all the common Communities I contribute to. I also have a folder for other administrative work like travel, expenses, my opportunities, and my field sales reports. This feature really helps me organize my thoughts when working on the particular task by automating the opening of these tabs.
In this video I show how you can bookmark all of your open tabs and then open all of those tabs with a single click.
In the process of creating an internal tool for my team I found that trying to zoom an image and move it around was not as simply as a single “zoom” CSS attribute. While Chrome supports “zoom” and it works quite well, the other browsers don’t work consistently, especially if you store the zoom and position values in a script. I stored the positions on the images to be replayed and I found all kinds of inconsistencies across browsers. What did work consistently is the transform CSS property, but that brought another challenge.
The video in the previous post did not do the test justice as many could not tell it truly is a smoother animation so here you go, you can view this web page yourself on the different browsers.
What I see on my machine is a much smoother animation of both the outer box and the growing text. Notice it is not choppy at all in IE, very smooth. And just an FYI, I am a solid Chrome user for a few years now, before that FireFox, and before that IE. With all of these IE commercials on television I had to see if this really was “faster”, at least in this space. I would be interested to hear what others see.
I downloaded the Adobe’s new Edge Animate and played around with the tutorials for a bit and even did a basic animation. After I saved the HTML I then launched it into my default browser (Chrome) and was not very impressed. The animation was very choppy and even left blit marks throughout the animation, some really bad double buffering going on…
I then went back into Edge Animate and added even more animation, the text growing over the time line. This made it even worse in Chrome! I then opened the file in all of the major browsers (IE, FireFox, and Safari) and was amazed how great Internet Explorer did! It was by far the smoothest animation, with FireFox coming in a close second. You can’t completely tell by the video but you can definitely see how horrible Chrome is. And yes, these are all the latest browsers, except FireFox (I can’t keep up with their weekly updates).
I know this is a basic test but its pretty clear who the winner is here, without any “special” HTML5 code. It could also be that Adobe is in Microsofts pockets and intentionally made it perform better in IE but someone would have to prove that to me.
In the video I show Chrome, Safari, FireFox, then Internet Explorer.
In this video I show how easy it is to get the xPath from Google Chrome. You can use the xPath when processing the DOM tree in your code. I use the javax.xml.xpath in Java to process DOM tree; the API is very powerful and easy to use.
As Neil predicted last year about Chrome, I will make one myself – the Chrome web browser will be the number one browser in the world by the end of 2011. That is probably a crazy prediction considering its only at about 15% of market share today.
My blog is by far not a complete census but it clearly shows Chrome way ahead of every other browser besides FireFox. Interestingly, I still use FireFox most of the time but I do find myself going over to Chrome every now and then. Chrome was about 15% of browsers hitting my site just a month ago and IE 8.0 was close behind, the gap is getting larger.
Here is a chart of the browsers that hit my site in a single day:
Google Chrome OS (learn about the operating system) is scheduled to be released mid 2011, is your site ready for it? Is your company ready for it? Do you even care about it? Say goodbye to rich applications! The entire concept of the operating system is 100% web. There is no doubt this will entice companies to move and to “trust” the cloud. The concepts that are touted here are ground breaking to say the least. The question is, will companies and the public in general “trust the cloud” with everything? I am not sure I would today, but it seems inevitable as more and more things move off of the device and onto some server. So to follow my previous post about web applications and the rich client this is a great leap forward altogether – ie. no rich applications! Will the casual business user see 100% web based desktops in less than a year? I guess we will see…