Friday, 4 November 2016

Jquery validation Rule List

Rule Format

To add rules to your input elements follow this format:
data-rule-[rule name separate by dashes]="true"
Here are some examples:
  • Required - data-rule-required="true"
  • Email - data-rule-email="true"
  • Minimum Length = data-rule-minlength="6"

Message Format

By default the jQuery Validation Plugin will add it’s owne messages, but you can customize them to be whatever you want using another data attribute. To specify messages for each rule with data attributes follow this format:
data-msg-[rule name separate by dashes]="The message you want."
Here are some examples:
  • Required - data-msg-required="Madam/sir, this field is required."
  • Email - data-msg-email="Let us spam you, enter a valid email address."

Rule List:

If you want to know exactly what the validators are available and what they do look at the code for the validators in core or browse the additional validators.
Here is a list of them that I compiled by looking at the source on GitHub. I marked them with what part of the framework they’re from, and whether or not I tested them:
(Tested, core)
  • data-rule-required=”true”
  • data-rule-email=”true”
(Untested, core, but should work)
  • data-rule-url=”true”
  • data-rule-date=”true”
  • data-rule-dateISO=”true”
  • data-rule-number=”true”
  • data-rule-digits=”true”
  • data-rule-creditcard=”true”
  • data-rule-minlength=”6”
  • data-rule-maxlength=”24”
  • data-rule-rangelength=”5,10”
  • data-rule-min=”5”
  • data-rule-max=”10”
  • data-rule-range=”5,10”
  • data-rule-equalto=”#password”
  • data-rule-remote=”custom-validatation-endpoint.aspx”
(Untested, additional, but should work)
  • data-rule-accept=””
  • data-rule-bankaccountNL=”true”
  • data-rule-bankorgiroaccountNL=”true”
  • data-rule-bic=””
  • data-rule-cifES=””
  • data-rule-creditcardtypes=””
  • data-rule-currency=””
  • data-rule-dateITA=””
  • data-rule-dateNL=””
  • data-rule-extension=””
  • data-rule-giroaccountNL=””
  • data-rule-iban=””
  • data-rule-integer=”true”
  • data-rule-ipv4=”true”
  • data-rule-ipv6=”true”
  • data-rule-mobileNL=””
  • data-rule-mobileUK=””
  • data-rule-lettersonly=”true”
  • data-rule-nieES=””
  • data-rule-nifES=””
  • data-rule-nowhitespace=”true”
  • data-rule-pattern=””
  • data-rule-phoneNL=”true”
  • data-rule-phoneUK=”true”
  • data-rule-phoneUS=”true”
  • data-rule-phonesUK=”true”
  • data-rule-postalcodeNL=”true”
  • data-rule-postcodeUK=”true”
  • data-rule-require_from_group=””
  • data-rule-skip_or_fill_minimum=””
  • data-rule-strippedminlength=””
  • data-rule-time=””
  • data-rule-time12h=””
  • data-rule-url2=””
  • data-rule-vinUS=””
  • data-rule-zipcodeUS=”true”
  • data-rule-ziprange=””
Posted by at No comments :

Facebook Meta tag for Sharing ........

Basic Metadata

To turn your web pages into graph objects, you need to add basic metadata to your page. We've based the initial version of the protocol on RDFa which means that you'll place additional <meta> tags in the <head> of your web page. The four required properties for every page are:

og:title - The title of your object as it should appear within the graph, e.g., "The Rock".
og:type - The type of your object, e.g., "video.movie". Depending on the type you specify, other properties may also be required.
og:image - An image URL which should represent your object within the graph.
og:url - The canonical URL of your object that will be used as its permanent ID in the graph, e.g., "http://www.imdb.com/title/tt0117500/".
As an example, the following is the Open Graph protocol markup for The Rock on IMDB:

<html prefix="og: http://ogp.me/ns#">
<head>
<title>Welcome to my Blog</title>
<meta property="og:title" content="The Rock" />
<meta property="og:type" content="video.movie" />
<meta property="og:url" content="http://www.imdb.com/title/tt0117500/" />
<meta property="og:image" content="http://ia.media-imdb.com/images/rock.jpg" />
...
</head>
...
</html>

Optional Metadata

The following properties are optional for any object and are generally recommended:

og:audio - A URL to an audio file to accompany this object.
og:description - A one to two sentence description of your object.
og:determiner - The word that appears before this object's title in a sentence. An enum of (a, an, the, "", auto). If auto is chosen, the consumer of your data should chose between "a" or "an". Default is "" (blank).
og:locale - The locale these tags are marked up in. Of the format language_TERRITORY. Default is en_US.
og:locale:alternate - An array of other locales this page is available in.
og:site_name - If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb".
og:video - A URL to a video file that complements this object.

For example (line-break solely for display purposes):


<meta property="og:audio" content="http://example.com/bond/theme.mp3" />

<meta property="og:description"   content="Sean Connery found fame and fortune as the           suave, sophisticated British agent, James Bond." />

<meta property="og:determiner" content="the" />

<meta property="og:locale" content="en_GB" />

<meta property="og:locale:alternate" content="fr_FR" />

<meta property="og:locale:alternate" content="es_ES" />

<meta property="og:site_name" content="IMDb" />

<meta property="og:video" content="http://example.com/bond/trailer.swf" />


 The RDF schema (in Turtle) can be found at ogp.me/ns.


Structured Properties

Some properties can have extra metadata attached to them. These are specified in the same way as other metadata with property and content, but the property will have extra :.

The og:image property has some optional structured properties:

og:image:url - Identical to og:image.
og:image:secure_url - An alternate url to use if the webpage requires HTTPS.
og:image:type - A MIME type for this image.
og:image:width - The number of pixels wide.
og:image:height - The number of pixels high.
A full image example:

<meta property="og:image" content="http://example.com/ogp.jpg" />

<meta property="og:image:secure_url" content="https://secure.example.com/ogp.jpg" />

<meta property="og:image:type" content="image/jpeg" />

<meta property="og:image:width" content="400" />

<meta property="og:image:height" content="300" />

The og:video tag has the identical tags as og:image. Here is an example:


<meta property="og:video" content="http://example.com/movie.swf" />

<meta property="og:video:secure_url" content="https://secure.example.com/movie.swf" />

<meta property="og:video:type" content="application/x-shockwave-flash" />

<meta property="og:video:width" content="400" />

<meta property="og:video:height" content="300" />

The og:audio tag only has the first 3 properties available (since size doesn't make sense for sound):

<meta property="og:audio" content="http://example.com/sound.mp3" />


<meta property="og:audio:secure_url" content="https://secure.example.com/sound.mp3" />


<meta property="og:audio:type" content="audio/mpeg" />

Arrays

If a tag can have multiple values, just put multiple versions of the same <meta> tag on your page. The first tag (from top to bottom) is given preference during conflicts.

<meta property="og:image" content="http://example.com/rock.jpg" />
<meta property="og:image" content="http://example.com/rock2.jpg" />
Put structured properties after you declare their root tag. Whenever another root element is parsed, that structured property is considered to be done and another one is started.

For example:


<meta property="og:image" content="http://example.com/rock.jpg" />


<meta property="og:image:width" content="300" />


<meta property="og:image:height" content="300" />


<meta property="og:image" content="http://example.com/rock2.jpg" />


<meta property="og:image" content="http://example.com/rock3.jpg" />


<meta property="og:image:height" content="1000" />

Posted by at No comments :

Thursday, 27 October 2016

Dear all, Wish u and your family a very happy diwali & prosperous new year. May God fulfill all your wishes in wealth, health & happiness in your life.


Posted by at No comments :

Friday, 12 February 2016

HTML CODE FOR FORM IN CENTER (FROM ALL SIDE )

<html>
<head><title>Hello Gaurav</title></head>
<body>
<table border="0" cellpadding="0" cellspacing="0" width="100%" height="100%">
<tr><td align="center" valign="middle">
<table border="1" width="300">
<tr><td>Hey look at me! I'm in the middle!</td></tr>
</table>
</td></tr>
</table>
</body>
</html>

Posted by at No comments :

Saturday, 6 February 2016

What are the differences between %f, %e and %g format specifiers in C language? Explain with examples in which these format specifiers are emplyed.

  1. %f prints the corresponding number as a decimal floating point number (e.g. 321.65),
  2.  %e prints the number in scientific notation (e.g. 3.2165e+2), 
  3. %g prints the number in the shortest of these two representations (using the same number, the decimal floating point is shorter and hence 321.65 would be printed.  An example where %g would print the scientific notation is when the number is 6000000000.  In scientific notation, this would 6e+9 which is shorter and hence, 6e+9 would be printed.)
  4. The only difference between the lower case %e, %g and the upper case versions %E, %G is that printing scientific notation will use an upper case E instead of a lower case e to indicate the exponent.  E.g.  %E produces 3.2165E+2 when %e produces 3.2165e+2.

Posted by at No comments :

Friday, 5 February 2016

Right program of goto keyword 

int main()
{
   int age;
   

   printf("Enter you age:");
   scanf("%d", &age);
   if(age>=18)
        goto Vote;
   else
        goto NoVote;

Vote:
     printf("you are eligible for voting");
     exit();
   NoVote:
     printf("you are not eligible to vote");


    exit();

return 0;
}
Posted by at No comments :
Subscribe to: Posts ( Atom )