scratchpad:dojo_upgrade_notes
This is an old revision of the document!
Table of Contents
Dojo Upgrade Notes
These notes are observations made by Joseph Lewis about what needs/can be changed upon upgrading dojo versions, as well as pitfalls that may be encountered. Anyone else with ideas/propositions is welcome to edit.
Evergreen Specific Changes
- Dojo 1.4.* includes dijit.Calendar, after converting we should be able to remove jscalendar (/Open-ILS/web/opac/common/js/jscalendar) which includes 74 files at 6760 lines of code (300kb) and will properly style to the chosen dijit theme unlike the jscalendar.
- It is probably prudent to upgrade all instances of dojo.Grid to dojox.EnhancedGrid to allow easy multiple column sorting if not they should be replaced by dojox.Grid.DataGrid.
Upgrade Notes From Dojo
Upgrading Here are some common issues people have had when upgrading (ie, migrating) from 1.3 to 1.4: 1. If your widgets are using templatePath you should ideally update them to use templateString with dojo.cache() instead, or alternately, minimally, make sure that they set templateString to null (to override the templateString setting from a superclass). 2. ContentPane acts more as a layout widget than before, defining isLayoutContainer: true. This may break some custom subclasses. 3. The startup code for widgetsInTemplate has changed; if you have a custom widget that manually adds sub-widgets into its DOM, be sure to add those sub-widgets to this._startupWidgets[] and also this._supportingWidgets[]. Alternately you can set _earlyTemplatedStartup to true to get the 1.3 behavior 4. If your TabContainer is too wide (you must have set width=100% in your markup?), specify controllerWidget=”“dijit.layout.TabController” (see Ticket #10495).
scratchpad/dojo_upgrade_notes.1312228756.txt.gz · Last modified: 2022/02/10 13:33 (external edit)