Skip to main content

Google Gears up for HTML5

I am not that big fan of Google, (ok I am lying, who isn't a fan of Google?) But you like them or No, one thing you must agree, they are technology savvy and not money-power hungry, good for poor developers like me.

Google always came up with something new to surprise us and even if they did not intend to surprise us, we do get surprised with their announcements.
Devta
Google has announced that is it dumping Google Gears for HTML 5, which is a surprise yet a technically sound move.

With Google Gears, they had to build it compatible around every browser which was a headache for Google but if they do have the same technology around HTML 5, then I every browser compatible with HTML 5 will have offline access to Google products.

ReadWriteWeb says, "We question whether offline access is even necessary. After all... in today's world, you're never too far from an internet connection. We concluded that offline access is important now, but less important with each passing day." more here.

However, this sentence may be true for US and UK, but really the world is more than just that, infact most of the Google products are used in India (where I belong) that other countries. There are many places where offline access is necessary. When I was consulting a client on Salesforce, his major requirement was that the sales rep travel to the part of the world which has limited internet access. A company dealing with metric TONs of iron ore may not exactly use internet or has time to study internet. They use their MIS system is enought for them presently. So ReadWriteWeb, if you are listening, the world is very large and the internet is not yet wide spread around the world, and we do need offline access.

So, moving over Google Gears, I am enjoying Google Wave with Elizabot, for those who do not know her, a new post is coming up soon.

Till then wait for the next update.

Cheers,
Ravan

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…