Most Common Screen Resolutions you need to know!

Desktops and Laptops:

Wide Screen desktop: 1920 x 1080 pixels  (Common)

Normal Screen desktop: 1280 x 720 pixels (Most Common)

Small Screen desktop: 1024 x 768 pixels (Less Common)

Smallest Screen desktop: 800 x 600 pixels (Not so common anymore)

 

SmartPhones:

Nokia Lumia 900 screen resolution: 480 x 800 pixels at 217 ppi

Nokia Lumia 920 screen resolution: 768 x 1280 pixels at 332 ppi (Most Common)

iPhone 3 screen resolution: 320 x 480 pixels

iPhone 4 screen resolution: 640 x 960 pixels (Most Common)

iPhone 5 screen resolution: 640 x 1136 pixels (Most Common)

Samsung Galaxy s2 screen resolution: 480 x 800 pixels at 217 ppi

Samsung Galaxy s3 screen resolution: 1280×720 resolution (Most Common)

Samsung Galaxy s4 screen resolution: 1920×1080 pixels (Most Common)

 

Tablets:

Microsoft Surface screen resolution: 1366 x 768 pixels (Most Common)

Microsoft Surface Pro screen resolution: 1920 x 1080 pixels

iPad 1 screen resolution: 1024 x 768 pixels at 132 ppi

iPad 2 screen resolution: 1024 x 768 pixels at 132 ppi

iPad 3 screen resolution: 2048 x 1536 pixels at 264 ppi (Most Common)

iPad Mini screen resolution: 1024 x 768 pixels at 163 ppi

Galaxy Note 8.0 screen resolution: 1280 x 800 pixels

Galaxy Note 10.1 screen resolution: 1280 x 800 pixels

Galaxy Tab 2 7.0 screen resolution: 1024 x 600 pixels

Galaxy Tab 2 10.1 screen resolution: 1280 x 800 pixels

Create a textbox watermark using CSS and jQuery

Step 1: –

First of all, we need to reference the latest jquery plugin (at the time being  version 1.9.1):

<script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js“></script>

Step 2:-

Add some styling to the textbox watermark, which is usually a light grey text font

<style>

.watermark
{

font-family: Calibri, Arial;

font-size: 14px;

color:gray;

}

</style>

Continue reading

Using Google API Heat Maps

Google HeatMaps

P.S full code at bottom of page

Step 1 :- Add Reference to Google JavaScript API

<script src=”https://maps.googleapis.com/maps/api/js?sensor=false&libraries=visualization ” type=”text/javascript”></script>

Parameters Explained:

1. Sensor (Obligatory)

Sensor can be either set to true or false to inform the API if the maps are being accessed from a device with location such as a smart phone or not such as a desktop.

If the sensor parameter is not passed, the API will return a “Request Denied” error.

2. libraries(optional)

When references Google API, we are still not loading everything. Therefore, we can load these libraries using parameters in the URL. The Visualization library is required when we want to visualize some sort of data using markers, heat maps, or circle size maps.

Continue reading

Securing a path/folder in an ASP.NET Web Application

Create or open your global.asax and open the code behind.

In your Application_AuthenticateRequest method create a request to check if user is logged in and check if his role is entitiled to view the path you are securing. In my case I am using Windows authentication, so I will use User.Identity.Name and if it is null it means no user is logged in. Then we will request the url path the user is requesting to check if the user is trying to access an unauthorized path. If so, we redirect him back to an error page, home page or wherever you prefer.

protected void Application_AuthenticateRequest(object sender, EventArgs e)
{
try
{

//Check if it contains our secure folder or path part

if (requestPath.Contains(“/Secure/”))

{

//Check if username is null (if null, means not logged in)
if (!string.IsNullOrEmpty(Context.User.Identity.Name))
{

bool allowed = false; // create a statement to see if user is in a role that allows or restricts access to this secure path

//Request URL in browser
string requestPath = Request.Url.AbsolutePath;

//checks if the user does not have access (!allowed means NOT ALLOWED)

if (!allowed)
{

//Redirect to error page

Response.Redirect(“ErrorPage.aspx”);
}

}

}
}
catch (Exception ex)
{

//An exception might occure if the User.Identity.Name is not set (empty / not logged in)
Response.Redirect(“ErrorPage.aspx”);
}

}