Total Pageviews

Friday, January 27, 2012

Jobs @ Lakshaya Digital Premier Gaming Studio in Delhi/Gurgaon

Lakshya is one of the largest independent Video Games Development companies in South Asia with offices in Gurgaon, Pune, Singapore, San Diego  and Tokyo . We are creating original game titles on the latest platforms and technologies.

As part of our growth plans – we are looking for talented Artists (3D and 2D), Game Designers and Game Programmers to join us at our Gurgaon and Pune studios. They will have the opportunity to work with some of the best games industry veterans from across the world, and create new and exciting video games.

If you are passionate about games and excited by the prospect of working with industry leaders, creating world-class products for a global audience, then please share your updated resume with us at or call us at 0124-4309360.

To know more about the open positions, check

Subject line : Position applied for:-

Total experience :-

C- CTC:-


Preferred location:- Pune or Gurgaon

Last company name:-

Kindly mention your link for BlogSpot / Show real /  portfolio in the

Wednesday, January 25, 2012

Tuesday, January 17, 2012

Going Nuts with CSS Transitions

First we are going to make our images look like mini polaroids with captions. This means the logic is kept separate from the code that applies the polaroid effect. The polaroid class has no positioning, which allows it to be used generically anywhere that the effect is required. The pull classes set a float and add appropriate margins—they can be used for things like blockquotes as well.

 .polaroid {
  width: 150px;
  padding: 10px 10px 20px 10px;
  border: 1px solid #BFBFBF;
  background-color: white;
  -webkit-box-shadow: 2px 2px 3px rgba(135, 139, 144, 0.4);
  -moz-box-shadow: 2px 2px 3px rgba(135, 139, 144, 0.4);
  box-shadow: 2px 2px 3px rgba(135, 139, 144, 0.4);

The actual polaroid effect itself is simply applied using padding, a border and a background colour. We also apply a nice subtle box shadow, using a property that is supported by modern WebKit browsers and Firefox 3.5+. We include the box-shadow property last to ensure that future browsers that support the eventual CSS3 specified version natively will use that implementation over the legacy browser specific version.

The box-shadow property takes four values: three lengths and a colour. The first is the horizontal offset of the shadow—positive values place the shadow on the right, while negative values place it to the left. The second is the vertical offset, positive meaning below. If both of these are set to 0, the shadow is positioned equally on all four sides. The last length value sets the blur radius—the larger the number, the blurrier the shadow (therefore the darker you need to make the colour to have an effect). 


For browsers that understand it (currently our old favourites WebKit and FF3.5+) we can add some visual flair by rotating the image, using the transform CSS 3 property.

-webkit-transform: rotate(9deg);
-moz-transform: rotate(9deg);
transform: rotate(9deg);

Rotations can be specified in degrees, radians (rads) or grads). WebKit also supports turns unfortunately Firefox doesn’t just yet.
For example we want any polaroid images on the left hand side to be rotated in the opposite direction, using a negative degree value:
.pull-left.polaroid {
-webkit-transform: rotate(-9deg);
-moz-transform: rotate(-9deg);
transform: rotate(-9deg);
Multiple class selectors don’t work in IE6 but as luck would have it, the transform property doesn’t work in any current IE version either. The above code is a good example of progressive enrichment: browsers that don’t support box-shadow or transform will still see the image and basic polaroid effect.

 For Live example

Friday, January 13, 2012

Fix Browser Compatibility Issues with Internet Explorer 8 in Windows 7 – AppCompat Series

Many Web designers use browser detection techniques to ensure that their sites display properly when viewed with specific browsers. Some browser detection techniques encounter problems when viewed with later versions of the browser they’re made for. Internet Explorer has the User Agent String which is the identifier that provides data about its version and other attributes to Web servers. Many Websites and applications rely on the User Agent String to detect the Browser settings.internet-explorer-8Now the issue is that, web pages that explicitly check the User Agent String and do not support the Internet Explorer 8 User Agent String may not run properly. Applications that host Trident will default to Internet Explorer 7 using the Web Optional Component, but will not have access to Internet Explorer 8 features.

A simple Mitigation to this issue would be to ensure that your web applications properly handle the new ‘MSIE 8.0′ version in the User Agent String.

Without compatibility mode:

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)

With compatibility mode:

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)

Also, use Internet Explorer 7 Compatibility View for those applications based on Internet Explorer

This can be done either by clicking on the Compatiblity view button or by using meta tags.

Monday, January 9, 2012

My latest Work

This site is completely design by me.