RGraph
HTML5 software library for charting written in native JavaScript
RGraph is an HTML5 software library for charting written in native JavaScript. It was created in 2008. RGraph started as an easy-to-use commercial tool based on HTML5 canvas only. It's currently freely available to use under the open-source GPL license and supports more than 50 chart types in both SVG and canvas.
License
RGraph is dual licensed using the open source GNU General Public License 2.0 and commercial.
Mentions
In July 2014, Salesforce made RGraph available to be plugged into the reporting and dashboard tools on its mobile platform. RGraph is among six third-party visualization tools available inside the dashboards, together with Google Charts, D3.js, CanvasJS, Chart.js, and Highcharts.
In a book "Android Cookbook: Problems and Solutions for Android Developers," RGraph is recommended as an alternative to creating Android charts in pure Java.
Releases
RGraphs follows a frequent release schedule. Major milestones includes:
Version 4.0 (2015): Introduced robust native SVG rendering alongside its legacy HTML5 canvas core.
This brief starts where responsible research should: with the source description of “RGraph” as hTML5 software library for charting written in native JavaScript. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as hTML5 software library for charting written in native JavaScript. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated May 20, 2026. The linked authority identifier is Q85795461. The first chronological checks are 2008, 2014 and 2015.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “RGraph”, its source revision and the description used here.
- Expand the search: follow RGraph primary sources, RGraph archive and RGraph research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “RGraph”?
- Which earlier names or jurisdictions may reveal additional records?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “RGraph” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.