jQWidgets Forums
jQuery UI Widgets › Forums › Navigation › Tabs › Leveraging multiple versions of JQWidgets on single site, grid or tab workaround
Tagged: grid tab release
This topic contains 2 replies, has 2 voices, and was last updated by techie.brandon 12 years, 5 months ago.
-
Author
-
January 17, 2013 at 10:56 pm Leveraging multiple versions of JQWidgets on single site, grid or tab workaround #13823
I am very intimately tied to the tab widget lifecycle of JQWidgets 2.0.0, however there seems to be a glaring bug regarding the grid on this release. I have tested my code on 2.6.0’s grid implementation and see perfect execution. So in order to make our product release-ready I need to leverage the 2.6.0 grid widget in isolation of the rest of the application. I do not have the cycles available to re-engineer our CMS to leverage 2.6.0 evidently new lifecycle ( using initTabContent configuration hook ).
Release 2.0.0 problem encountered: I have been unable to update existing grid view once widget is initialized with a blank array.
Resolution is to use 2.6.0 grid. Provided on this link is a example of this scenario leveraging the 2.6.0 libraries. http://jsbin.com/ifayac/2/Perfect solution would be a solution that I can replicate on the 2.0.0 widget libraries. Please provide a jsFiddle or similar immediate gratification of a visible solution.
Secondary solution would be to leverage multiple versions of JQWidgets in a single page, likely using a separate JQuery library and symbol.
Third solution is to set a flag so that the lifecycle for the tabs widget is more similar to the 2.0.0 implementation.
I have already tried to swap the 2.6.0 (2.2.1, 2.3.1, 2.4.1) grid components into the 2.0.0 codebase but as one would expect that doesn’t play nicely together (was worth a shot!).
For some details, the tabs lifecycle implementation seems to change between 2.0.0 and 2.2.1. The only working grid implementation that I can get working is against the 2.6.0 release (I didn’t try the 2.5.5 release).
January 18, 2013 at 4:49 am Leveraging multiple versions of JQWidgets on single site, grid or tab workaround #13836Hi techie.brandon.
jQWidgets 2.0 is from April 2012 and we have had 14 updates of the product since then. We suggest you upgrading to jQWidgets version 2.6. Also we do have an example about integration of a Grid and Tabs here: integration.htm. The function that is used in this version for initializing the widgets inside the tabs is called “initTabContent”.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comJanuary 18, 2013 at 6:05 am Leveraging multiple versions of JQWidgets on single site, grid or tab workaround #13843Peter, Not helpful at all. Suggesting a major version bump after my statement and referencing same method as I. Hopefully this response is not indicative.
For anyone following later; My solution:
Bring in jQuery 1.8.2 with the noConflict method invoked and true flag to reset original jQuery reference to $ (instead of one coming in from 1.8.2).
window.jQuery182 = jQuery.noConflict(true);
Wrap jqxGrid and all deps in a closure passing the jQuery182 variable in as a argument $ to be used by all library definitions inside the internal scope.
(function($){
})(jQuery182)
I can now inject the jQuery182 into my own widgets closure, or access them at will with jQuery182(“”).jqxGrid({ })
-
AuthorPosts
You must be logged in to reply to this topic.