| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 362 |
| Technical Name |
odoo_react_vis |
| License | OPL-1 |
| Website | https://shachain.dev |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 362 |
| Technical Name |
odoo_react_vis |
| License | OPL-1 |
| Website | https://shachain.dev |
vis.js Shared Chunks for Odoo
Timeline, network graph, and reactive DataSet primitives for odoo-react visualizations — four SystemJS shared chunks with single-instance dedupe across consumer addons.
What it does
Odoo React Vis vendors the vis.js ecosystem — vis-timeline,
vis-network, vis-data, and moment —
as four independent SystemJS shared chunks. Commercial visualization
addons (gantt charts, dependency graphs, ERD diagrams) import the
bare specifiers; the browser dedupes by chunk URL so cross-addon
imports of vis-data automatically share the same instance.
Odoo React Vis Features
Four shared chunks, one importmap, single-instance protocol — no double-bundling, no double-state surprises.
Four SystemJS Shared Chunks
Four SystemJS Shared Chunks
vis-timeline for interactive timelines (drag, zoom, group,
dependency rendering), vis-network for force-directed
network graphs (ERD diagrams, module dependency maps),
vis-data for reactive DataSet /
DataView collections (shared by both vis-timeline and
vis-network), and moment for date / time formatting
and i18n locale (single global instance required by vis-timeline axis).
Single-Instance Sharing
Single-Instance Sharing
Each chunk is published to a SystemJS importmap and resolved by URL,
so the browser dedupes automatically. Consumer addons importing
vis-data always get the same instance — critical
for cross-addon state coordination (e.g. moment.locale()
changes made by one addon are visible to vis-timeline's axis
rendering in another).
Consumer Map
Consumer Map
sc_react_gantt consumes vis-timeline +
vis-data + moment for its Gantt chart view.
sc_react_dep_graph consumes vis-network +
vis-data for module dependency / ERD visualizations.
Both share the same vis-data chunk instance — one
download, one parse, one in-memory copy.
OPL-1 Wrapper + Vendored Libraries
OPL-1 Wrapper + Vendored Libraries
Wrapper code (entries / build configuration / SystemJS register stub)
licensed under OPL-1. Vendored libraries retain their upstream licenses
— vis-timeline, vis-network,
vis-data, moment all under Apache-2.0 / MIT.
See LICENSE + NOTICE + licenses/
in the addon root for full attribution.
Built on
Powered by the vis.js ecosystem, the SystemJS module loader, and the odoo-react bridge — running natively on Odoo.
Try Odoo React Vis today
vis-timeline · vis-network · vis-data · moment · SystemJS importmap shared
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module