Jquery widget what is

All demos come with full source code and are presented in multiple different themes. If you want to build your own theme, you can use our Theme Builder. Our widgets feature intuitive API and come with getting started documentation.

If you have a question, please feel free to contact us at support jqwidgets. We offer free support from Monday-Friday during your days evaluation period.

We aim to respond quickly to your requests, and to adapt our plans to optimize quality. Based on customer feedback and demands, we may prioritize the development of new features and new widgets. The plan for the next 3 months can be found here: Roadmap. It is platform independent, cross-browser compatible and works on PC and mobile devices. With jQWidgets, you can target new devices such as tablets and smartphones by using the extensive range of touch enabled jQuery Widgets.

The jQWidgets framework automatically detects the device type, capabilities and browser version, and adjusts the internal behavior for optimal rendering and best user experience. It is small in size, highly modular and extensible. Individual widgets and themes can be loaded on demand to further optimize the download time and save memory.

All widgets are optimized for optimal user experience on smart phones, tablets and PCs running different operating systems and browsers. All widgets are designed from ground-up and based on a powerful common core.

The framework core provides fundamental capabilities like support for widget extensions and inheritance, widget settings, internal event handling and routing, property change notifications, device and browser compatibility detection and adjustments. The framework automatically detects the device type, capabilities and browser version, and adjusts the internal behavior for optimal rendering and best user experience. The product supports all major desktop and mobile web browsers - Internet Explorer 7.

They are everything you need to build awesome-looking applications with consistent look and feel. Widgets should not have responsibilities not related to the entity described by the widget. You must use DOM event bubbling to perform one-way communication between a child widget and its parent widget. Widgets must comply with the Law of Demeter principle.

For example, the mage. Widgets must not interact with DOM elements selected using this. This reduces the number of widget conflicts because widgets interact only with their child elements. Description: The base widget used by the widget factory. Options classes. Initialize a progressbar widget with the classes option specified, changing the theming for the ui-progressbar class: 1. Get or set the classes option, after initialization: 1. The classes to add, as a space-delimited list.

If a property of the classes option matches a key, the value will be added as well. Additional classes to add, required for layout or other reasons. Unlike the keys argument, these aren't associated with any properties of the classes option. Just like keys , they will also be automatically removed when destroying the widget. Code examples: Add the ui-progressbar class to the widget's element this. There are no parameters, but this. Code examples: Set the background color of the widget's element based on an option.

Keeps this context correct. Essentially setTimeout. Returns the timeout ID for use with clearTimeout. Type: Function or String. Code examples: Remove a class from the widget's element when the widget is destroyed. The event handlers are automatically cleaned up on destroy. Code examples: Apply focusable styling to a set of elements within the widget.

By default, no data is provided in the event, but this method can return an object which will be passed as the create event's data. Code examples: Pass the widget's options to create event handlers as an argument. The user-provided options override the options returned by this method, which override the default options. Code examples: Make the widget element's id attribute available as an option. See the hide option for possible option values. Code examples: Pass along the hide option for custom animations.

Any time the plugin is called with no arguments or with only an option hash, the widget is initialized; this includes when the widget is created. Code examples: Call the open method if the autoOpen option is set. The element s to unbind the event handlers from. Code examples: Unbind all click events from the widget's element.

Delegation is supported via selectors inside the event names, e. Automatically handles disabled widgets: If the widget is disabled or the event occurs on an element with the ui-state-disabled class, the event handler is not invoked.

Can be overridden with the suppressDisabledCheck parameter. Event handlers are automatically namespaced and cleaned up on destroy. Which element s to bind the event handlers to. If no element is provided, this. An object in which the keys represent the event type and optional selector for delegation, and the values represent a handler function to be called for the event. Code examples: Prevent the default action of all links clicked within the widget's element.

The classes to remove, as a space-delimited list. If a property of the classes option matches a key, the value will be removed as well. Additional classes to remove, required for layout or other reasons. Code examples: Remove the ui-progressbar class from the widget's element this.

Widget state should be updated based on changes. Code examples: Update a widget's element when its height or width option changes. An object containing options to set, with the name of the option as the key and the option value as the value.

Code examples: Call a resize method if the height or width options change. See the show option for possible option values. Code examples: Pass along the show option for custom animations. The classes to toogle, as a space-delimited list. If a property of the classes option matches a key, the value will be toggled as well.