Opened 5 years ago
Closed 5 years ago
#3210 closed defect (wontfix)
develop stragegy for updating JavaScript toolkits embedded in ui module
Reported by: | Greg Couch | Owned by: | Greg Couch |
---|---|---|---|
Priority: | blocker | Milestone: | 1.1 |
Component: | UI | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
The UI module provides several JavaScript toolkits, namely bootgrid 1.3.1, bootstrap 3.3.7 and bootstrap 4.4.1 (need both?), and jquery 3.3.1. Bootstrap is now 4.5, and jquery is at 3.5.1.
Would like some guidance as to how we're going to maintain that. Will dependencies on the UI bundle have to be exact dependencies if it is related to the JavaScript toolkit versions?
Change History (3)
comment:1 by , 5 years ago
Owner: | changed from | to
---|
comment:2 by , 5 years ago
Milestone: | 1.0 → 1.1 |
---|
comment:3 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
There is no getting around keeping all versions that have been distributed in installers. Any bundle that references any once-available Javascript libraries should expect them to be available in new distributions (semantic versioning).
Currently, references to JS libraries are by exact versions. If we want to, we can create symlinks (a la Linux libraries) for less specific versions, e.g., use bootstrap 3.3 instead of 3.3.7. But a version number *must* be present. Boostrap 4 is not compatible with Bootstrap 3.
Bundle dependencies can be handled in two ways: (a) reference a version of UI bundle that contains the desired versions of JS libraries, or (b) supply the desired JS libraries and use no dependencies on UI at all.