Related posts:

1. Getting around the dreaded Operation Aborted error in Internet Explorer with Ruby on Rails If you have ever experienced this… …you know how painful...

Related posts brought to you by Yet Another Related Posts Plugin.

When you are in a relationship, don’t intentionally say something which can hurt the other person.

But does that means you should not express yourself freely? – Well, no! There can be 10 different ways of conveying your point across. Though, fastest ways aren’t always the best ways.

That said – love you always.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I think I never cared about these – but the way David Baron from Mozilla describes these, I think I will now.
The points he was making started seeming so crucial that I jotted them down as if taking notes – something I never did with previous videos.

The things which I picked up from this video are…

From fetching the DOM over the wire to displaying it, following steps take place in order…
(1) Compute => (2) Compute Style => (3) Construct the DOM frame => (4) Layout => (5) Paint

The further Left (towards (1)) you push the browser’s rendering engine via your DOM/JS/CSS, the slower the browser would get.

Hence…

Use as specific CSS tags as possible. The more generic tag, the higher performance hit while searching the DOM. For example, a “#some-id {}” is way way faster than “body > div p {}” – as in the second tag, a larger portion of DOM is parsed to check which elements are affected by the selector. You push the browser to start from stage (2).

“:hover” style hits the browser pretty badly – as it pushes the browser back to stage (2). Coupled with the above mentioned CSS selectors problem, it can lead to real slow computation. Use it with CSS selectors which are very very specific in nature.

Programmatic scrolling of tags (some of which might have overflow property) via javascript – as that does not causes re-computation of style (stage 2). While if you do it with CSS magic, you push your browser back to stage (2).

Mozilla’s rendering tree, while building itself – does not takes any element with with CSS property “display:none” into account – it just skips it. So when this property is flipped, it triggers a full re-computation of the tree – which is expensive. However if we use the style “visibility:hidden” – the rendering tree picks up the related element while building itself. Hence when visibility is flipped, its much faster as there is no re-calculation of the rendering tree.

An old one – when javascripts are being downloaded, the browser stops itself from any other processing and waits for the script to download and execute (as script can modify the DOM anyhow it likes). During this time, the precious time is lost – which could have been used in downloading other content – like images, DOM, CSS, etc. Hence – keep the javascripts as further in the DOM as possible. Use caching is possible.

Learn more about speeding up your website at – Yahoo’s best practices (YSlow stuff) – some of which we regularly follow at AdoMado.com

Related posts:

1. OMG! Chrome-4.0 is nearly 59% and 76% faster than Firefox-3.7a1pre on my T61 (Ubuntu Jaunty) Okay, to start off – I really wanted Firefox to...
2. Getting around the dreaded Operation Aborted error in Internet Explorer with Ruby on Rails If you have ever experienced this… …you know how painful...

Related posts brought to you by Yet Another Related Posts Plugin.

Related posts:

1. Why I will pick Samsung Galaxy S i9000 over Nexus One or HTC Desire Ok, so I have to admit it – the first...

Related posts brought to you by Yet Another Related Posts Plugin.

“Cummon Samsung!! Your device is priced at INR 28,000 and you couldn’t use decent buid material…?” – was the first thought that crossed my mind.

A few days went by and I was still trying to get hold of a Nexus One or an HTC Desire – the only way to get them in India was to get it from the US. Done that way, the phone warranty wouldn’t be worth a penny! And I’ll have to rely on “importers in Gaffar market” to get the work done – no confirmation on if the device is in 100% working condition until I shell out the complete price – N1 is priced at about INR 28k and HTC Desire at INR 25k (no idea why INR 3k cheaper).

SAD story!

Thankfully, it ended when I first read about the TV out functionality in Samsung Galaxy S i9000 on AndroidAndMe.com. That was when I first went to see the device in real – and was taken aback by the cheap feeling build quality.

However, yesterday, after reading all the reviews and user experiences about SGS i9000 on xda-forums, I decided to give SGS i9000 another shot.

• Can I keep aside the build quality for a second and look at the hardware packed inside?
• Can I learn to appreciate a lighter device? - I’ve always had a heavy device in my pockets (E61, E72, G1, etc…)
• Can I trust Samsung to release a Froyo update for the device?

My answer to (most of) those questions was yes.
And yesterday, I was out in the market again – looking for another hands on with the SGS i9000.
And this time, with an open mindset towards the build quality.

I was not disappointed.

Here are a few points which prompted me to reconsider Samsung Galaxy S i9000 – over  Nexus One or HTC Desire

Super AMOLED, 4 inch Screen
Oh man! If you have ever used a Super AMOLED screen, you just cannot (I repeat, just cannot) go back to a regular AMOLED or LCD display. The screen is so bright and vivid that you just cannot miss it. Also, the 4 inch screen size Samsung has used – is just perfect. Not too huge (unlike EVO 4G or Droid X) or small (N1 or HTC Desire) – although screen size is more of a personal choice.

Technically, this screen enables a slimmer form factor, gives a wider viewing angle, is 20% brighter, is 80% less reflective & uses 20% lesser battery.

SGS screen as compared to iPhone

More powerful (Graphics) processor
Though all of the said devices (SGS i9000, N1, HCT Desire) pack a 1 Ghz processor and dish out a very snappy performance, they do have subtle differences (infact, quite some differences). They have different Graphics Processors (GPU).

• Nexus One - Qualcomm QSD8×50 with Adreno 200 GPU can render 22 million triangles/sec
• Samsung Galaxy S – S5PC110 with PowerVR SGX540 GPU can render 90 million triangles/sec

More triangles per sec => more GPU output => SGS  GPU is 3 times more powerful as compared to Nexus One’s GPU – hence smoother experience in games, movies and general UI navigation.
Also, the SGS’s Humming Bird processor is built using a 45 nm die – which should consume less power than the N1′s processor which is using a 65 nm die.

Check out this Youtube video which does a head to head comparison of the GPU’s on Nexus One & SGS – a must watch! Also, how SGS’s GPU blows away HTC Desire’s GPU in Doom 2 test.

TV Out capability
I am getting tired of constantly converting all my movies from MKV or AVI format into MPEG1/2 & use a USB stick to watch on my 32 inch Sony Bravia. A 300 megs movie in MKV format is converted to almost 3 GB size in Mpeg2 format – which is ridiculous!

Hence, the TV out capability in SGS i9000 is like god-sent!
Imagine a scenario, where I sync up SGS with the movies in my computer via WiFi and use TV out to directly mirror SGS’s screen on the TV – full HD playback with 720p resolution. No more conversions and copying. Yay

TV out in SGS

With bill and warranty
Since this phone is available from gazillions of authorized Samsung dealers, there is not even a slightest chance of me buying this phone from the grey market. I am getting this device will bill, with warranty – tax paid!

Video codec support
Samsung has done a great job in the multimedia department. Besides replacing Android’s stock media player, with their own custom implementation – which in my opinion, rocks! They have also added support for a ton of video (MP4/DivX/WMV/H.264/H.263 formats, plays .avi and .mkv wonderfully well) and audio (MP3/WAV/eAAC+/AC3/FLAC) codecs.

Now can one ask for more?

16 Gigs On-board memory
The device comes preloaded with 16 GB of memory – which is more than enough for me to store my music, photos and occasional movies. That saves me another INR 2k on a 16 Gig Micro SDHC. However, that being said, I am planning to give apps2sd a shot with an 8 Gigs Class 6 Micro SDHC.

1500 mAh Battery
A brilliant screen and demanding data requirements will only make the phone need more and more electron juice. And Samsung did it just right – by adding a 1500 mAh battery. Any lesser and the phone would have not been able to complete even one day on a single charge. Nice!

Bundled Apps…
Though, this is not important – never the less, its a factor. I think Samsung is the first Android mobile manufacturer which has decided to include a decent file explorer in the package. Though this can be done in an instant via the Android Market – but the fact that Sammy has thought this out for you – is wonderful. Samsung Galaxy S i9000 comes preloaded apps like Swype, Road SMS, Layar, Aldiko Ebook reader, All Share, Daily Briefing, Memo, Mini Diary, Social Hub, Write & Go, Car Home, and many more!

TouchWiz UI 3.0
I am really looking forward to the custom skin on top of stock Android 2.1 – I’ve always had the stock installations – so this should be fun to play with.

Checkout the detailed review (with screenshots) of the Samsung Galaxy S i9000. Feel free to let me know about how you feel about this device via the comments.
UPDATE
A lot of folks have complained that this device is slow & its GPS sucks! I believe, this is just the software.
And if this is just the software, this can always be fixed. Folks at xda-forums have already found fixes.
Next up – my unboxing video and more! Stay tuned

Related posts:

1. How do you make T61′s 14″ screen look miniscule? Simple! Put it up against a 23″ LCD screen –...

Related posts brought to you by Yet Another Related Posts Plugin.

…you know how painful it is to debug and rectify.

This error was so common that Microsoft created a knowledge base (KB927917) article for this. It even has a dedicated explanation at the IE Blog. The error basically is – “HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)”.

While building the Social sharing plugins for AdoMado, we were facing similar problems. Anywhere FB share, Orkut share or Digg buttons were being used, IE was complaining of exactly the same problem. Since social share plugins are the backbone of our community building process, fixing this ASAP was high on my agenda.

NOTE – There was no such problem on any version of Firefox or Chrome.

If you notice the IE blog entry, they mention that

Moving the location of your script block to a child of the body (this usually solves most problems, while allowing the most flexibility in terms of scenarios).

can be a possible solution.

Cool! But how do we reach here? My javascripts were spread all over the place!

First things first… I refactored the code in such a way that all possible usage of problem causing scripts was moved to one single partial. Now error was originating from only one location. The fix, as mentioned on the IE blog – was then straight forward.

In your layout, just before closing the BODY tag, use the “yield” block to render any such javascript – and render all such scripts into this “yield” block.

Here are some screen captures from our codebase…

Notice the “yield :delayed_loading” block…

Yield’ing to delayed_loading block.

If you browse over to our offer – Send Ad Free SMS using IE, you will notice that you see no such error. All the social share plugins render in harmony.
I’ve even thrown in a little jQuery fadeIn magic

Related posts:

1. Authentication using Google Accounts for your Rails App The methodology is very simple. Redirect the user to grant...
2. AdoMado… the Next Phase!! Hey everyone!! Last week we embarked on the next phase...

Related posts brought to you by Yet Another Related Posts Plugin.