jQuery UI Solutions for building backward compatibility with DotNetNuke 5 and 6
As part of the build of DotNetNuke 6.0 which is standard, now included is jQuery which is truly fantastic. Developers of the module no longer have to worry about the jQuery library package as this allows functionality of a component that is built-in. To get the feel and look of the DotNetNuke 6.0 that is native and to get the custom module with a look that is similar, jQuery makes it an easy task. Things can get a bit complicated only if a module has to be built that will accordingly target environments in multiples.
You may have to put in some effort to find solutions that can build compatibility backwards into the module of DotNetNuke 5 or 4 versions. This will have to be done so that the module is compatible with a DotNetNuke 6.0 version that could be supported by you. With this introduction of DotNetNuke 6.0 in just twenty four hours, releasing as well as building of a module is not yet considered as very feasible, being compatible to 6.0 only.
Understanding incorporated changes from jQuery with DotNetNuke 5 and 6
This will prove to be feasible only in the case where the module will be released into just one environment. As far as jQuery is related it is necessary to understand the changes incorporated into DotNetNuke6.0. For providing a consistent, updated and modern user interface, many of the jQuery plugins are used by DotNetNuke 6.0 module. Developers that are third party too can make use of these plugins which can be used best in conjunction with patterns of the DNN HTML form. Components like the jQuery plugins are client-side and reusable in nature.
Goals to be kept in mind and the two methods available
Different kinds of components are included in the module DotNetNuke 6.0 while keeping in mind a few goals for which the creation of plugins took place. For a user experience that is consistent in the module, all across the framework it allows reuse. Besides this, to register the script it exposes a public API method for avoiding file registrations that are duplicated in nature. From the markup, the plugin logic is separated physically. On initialization, through the settings of the plugin, all the markup context as well as information can get injected. For encouraging form pattern usage consistently and for implementation that is easier, defaults that are based on convention can be used for matching the DNN 6 form pattern.
Whenever needed, for overriding settings of default, flexibility is provided. To insert the jQuery UI libraries as well as jQuery on the DotNetNuke page there are two main methods. One is DotNetNuke.Framework.jQuery.RequestRegistration which from DNN 5.0 onwards is included. If this method is deployed, it will ensure that a reference to the library of jQuery is put into the page by DotNetNuke. The other method is DotNetNuke.Framework.jQuery.RequestUI Registration which is included from DNN 6.0 onwards. This method as well will ensure that the jQuery UI library reference is put on the page to empower unparalleled functionality.