Events Jquery
.bind()
Event Handler Attachment
Attach a handler to an event for the elements.
.blur()
Form Events, Forms
Bind an event handler to the "blur" JavaScript event, or trigger that event on an element.
.change()
Form Events, Forms
Bind an event handler to the "change" JavaScript event, or trigger that event on an element.
.click()
Mouse Events
Bind an event handler to the "click" JavaScript event, or trigger that event on an element.
.dblclick()
Mouse Events
Bind an event handler to the "dblclick" JavaScript event, or trigger that event on an element.
.delegate()
Event Handler Attachment
Attach a handler to one or more events for all elements that match the selector, now or in the future, based on a specific set of root elements.
.die()
Event Handler Attachment
Remove all event handlers previously attached using .live() from the elements.
.error()
Browser Events
Bind an event handler to the "error" JavaScript event.
event.currentTarget
Event Object
The current DOM element within the event bubbling phase.
event.data
Event Object
Contains the optional data passed to jQuery.fn.bind when the current executing handler was bound.
event.isDefaultPrevented()
Event Object
Returns whether event.preventDefault() was ever called on this event object.
event.isImmediatePropagationStopped()
Event Object
Returns whether event.stopImmediatePropagation() was ever called on this event object.
event.isPropagationStopped()
Event Object
Returns whether event.stopPropagation() was ever called on this event object.
event.pageX
Event Object
The mouse position relative to the left edge of the document.
event.pageY
Event Object
The mouse position relative to the top edge of the document.
event.preventDefault()
Event Object
If this method is called, the default action of the event will not be triggered.
event.relatedTarget
Event Object
The other DOM element involved in the event, if any.
event.result
Event Object
This attribute contains the last value returned by an event handler that was triggered by this event, unless the value was undefined.
event.stopImmediatePropagation()
Event Object
Prevents other event handlers from being called.
event.stopPropagation()
Event Object
Prevents the event from bubbling up the DOM tree, preventing any parent handlers from being notified of the event.
event.target
Event Object
The DOM element that initiated the event.
event.timeStamp
Event Object
This attribute returns the number of milliseconds since January 1, 1970, when the event is triggered.
event.type
Event Object
Describes the nature of the event.
event.which
Event Object
For key or button events, this attribute indicates the specific button or key that was pressed.
.focus()
Form Events, Forms
Bind an event handler to the "focus" JavaScript event, or trigger that event on an element.
.focusin()
Keyboard Events, Mouse Events
Bind an event handler to the "focusin" JavaScript event.
.focusout()
Keyboard Events, Mouse Events
Bind an event handler to the "focusout" JavaScript event.
.hover()
Mouse Events
Bind two handlers to the matched elements, to be executed when the mouse pointer enters and leaves the elements.
.keydown()
Keyboard Events
Bind an event handler to the "keydown" JavaScript event, or trigger that event on an element.
.keypress()
Keyboard Events
Bind an event handler to the "keypress" JavaScript event, or trigger that event on an element.
.keyup()
Keyboard Events
Bind an event handler to the "keyup" JavaScript event, or trigger that event on an element.
.live()
Event Handler Attachment
Attach a handler to the event for all elements which match the current selector, now or in the future.
.load()
Document Loading
Bind an event handler to the "load" JavaScript event.
.mousedown()
Mouse Events
Bind an event handler to the "mousedown" JavaScript event, or trigger that event on an element.
.mouseenter()
Mouse Events
Bind an event handler to be fired when the mouse enters an element, or trigger that handler on an element.
.mouseleave()
Mouse Events
Bind an event handler to be fired when the mouse leaves an element, or trigger that handler on an element.
.mousemove()
Mouse Events
Bind an event handler to the "mousemove" JavaScript event, or trigger that event on an element.
.mouseout()
Mouse Events
Bind an event handler to the "mouseout" JavaScript event, or trigger that event on an element.
.mouseover()
Mouse Events
Bind an event handler to the "mouseover" JavaScript event, or trigger that event on an element.
.mouseup()
Mouse Events
Bind an event handler to the "mouseup" JavaScript event, or trigger that event on an element.
.one()
Event Handler Attachment
Attach a handler to an event for the elements. The handler is executed at most once per element.
jQuery.proxy()
Event Handler Attachment, Utilities
Takes a function and returns a new one that will always have a particular context.
.ready()
Document Loading
Specify a function to execute when the DOM is fully loaded.
.resize()
Browser Events
Bind an event handler to the "resize" JavaScript event, or trigger that event on an element.
.scroll()
Browser Events
Bind an event handler to the "scroll" JavaScript event, or trigger that event on an element.
.select()
Form Events, Forms
Bind an event handler to the "select" JavaScript event, or trigger that event on an element.
.submit()
Form Events, Forms
Bind an event handler to the "submit" JavaScript event, or trigger that event on an element.
.toggle()
Basics, Mouse Events
Bind two or more handlers to the matched elements, to be executed on alternate clicks.
.trigger()
Event Handler Attachment
Execute all handlers and behaviors attached to the matched elements for the given event type.
.triggerHandler()
Event Handler Attachment
Execute all handlers attached to an element for an event.
.unbind()
Event Handler Attachment
Remove a previously-attached event handler from the elements.
.undelegate()
Event Handler Attachment
Remove a handler from the event for all elements which match the current selector, now or in the future, based upon a specific set of root elements.
.unload()
Document Loading
Bind an event handler to the "unload" JavaScript e
Monday, April 19, 2010
What is the difference between JavaScript and jQuery?
What is the difference between JavaScript and jQuery?
JavaScript is a language whereas jQuery is a library written using JavaScript.
What does dollar Sign ($) means in JQuery?
Dollar Sign is nothing but it's an alias for JQuery.
Over here $ sign can be replaced with jQuery...
JavaScript is a language whereas jQuery is a library written using JavaScript.
What does dollar Sign ($) means in JQuery?
Dollar Sign is nothing but it's an alias for JQuery.
Over here $ sign can be replaced with jQuery...
LINQ :: Language Integrated Query
you can find several descriptions of Language Integrated Query (LINQ), such as these:
LINQ is a uniform programming model for any kind of data. LINQ enables you to query and manipulate data with a consistent model that is independent from data sources.
LINQ is just another tool for embedding SQL queries into code.
LINQ is yet another data abstraction layer.
All of these descriptions are somewhat correct, but they each focus on just a single aspect. LINQ can do a lot more than just embed SQL queries, it is much easier to use than a “uniform programming model,” and it is far from being just another set of rules for modeling data.
LINQ is a methodology that simplifies and unifies the implementation of any kind of data access. LINQ does not force you to use a specific architecture; it facilitates the implementation of several existing architectures for accessing data. As with every tool, it can be used in both good and in bad ways. To get the most out of LINQ, you will have to master it.
Today, data managed by a program can belong to different data domains: an array, an object graph, an XML document, a database, a text file, a registry key, an e-mail message, Simple Object Access Protocol (SOAP) message content, a Microsoft Office Excel file…. The list is long.
Each data domain has its own specific access model. When you have to query a database, you typically use SQL. You navigate XML data with Document Object Model (DOM) or XQuery. You iterate an array and build algorithms to navigate an object graph. You use specific application programming interfaces (APIs) to access other data domains, such as an Office Excel file, an e-mail message, or the Microsoft Windows registry. In the end, you have different programming models to access different data sources.
The unification of data access techniques into a single comprehensive model has been tried in many ways. For example, there are Open Database Connectivity (ODBC) providers that allow you to query an Excel file as you would a Windows Management Instrumentation (WMI) repository. However, with this approach you use an SQL-like language to access data represented through a relational model. Sometimes data is naturally represented more effectively in a hierarchical or graphical model instead of a relational one. Moreover, if the data model is not tied to the language, you probably have to manage different type systems. All these differences create an “impedance mismatch” between data and code. LINQ tries to solve these issues, offering a uniform way to access and manage data without forcing the adoption of a “one size fits all” model. LINQ leverages commonalities between the operations in these data models instead of flattening the different structures between them.
LINQ is a uniform programming model for any kind of data. LINQ enables you to query and manipulate data with a consistent model that is independent from data sources.
LINQ is just another tool for embedding SQL queries into code.
LINQ is yet another data abstraction layer.
All of these descriptions are somewhat correct, but they each focus on just a single aspect. LINQ can do a lot more than just embed SQL queries, it is much easier to use than a “uniform programming model,” and it is far from being just another set of rules for modeling data.
LINQ is a methodology that simplifies and unifies the implementation of any kind of data access. LINQ does not force you to use a specific architecture; it facilitates the implementation of several existing architectures for accessing data. As with every tool, it can be used in both good and in bad ways. To get the most out of LINQ, you will have to master it.
Today, data managed by a program can belong to different data domains: an array, an object graph, an XML document, a database, a text file, a registry key, an e-mail message, Simple Object Access Protocol (SOAP) message content, a Microsoft Office Excel file…. The list is long.
Each data domain has its own specific access model. When you have to query a database, you typically use SQL. You navigate XML data with Document Object Model (DOM) or XQuery. You iterate an array and build algorithms to navigate an object graph. You use specific application programming interfaces (APIs) to access other data domains, such as an Office Excel file, an e-mail message, or the Microsoft Windows registry. In the end, you have different programming models to access different data sources.
The unification of data access techniques into a single comprehensive model has been tried in many ways. For example, there are Open Database Connectivity (ODBC) providers that allow you to query an Excel file as you would a Windows Management Instrumentation (WMI) repository. However, with this approach you use an SQL-like language to access data represented through a relational model. Sometimes data is naturally represented more effectively in a hierarchical or graphical model instead of a relational one. Moreover, if the data model is not tied to the language, you probably have to manage different type systems. All these differences create an “impedance mismatch” between data and code. LINQ tries to solve these issues, offering a uniform way to access and manage data without forcing the adoption of a “one size fits all” model. LINQ leverages commonalities between the operations in these data models instead of flattening the different structures between them.
Subscribe to:
Posts (Atom)