[ 
https://issues.apache.org/jira/browse/JSPWIKI-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038994#comment-18038994
 ] 

Alex O'Ree commented on JSPWIKI-1102:
-------------------------------------

as is, it seems to loop infinitely trying to attach the script files. browser 
then fills with white space. super strange.

replacing the CDN url for a locally hosted script seems to do the same thing. 
i'm not sure what i'm doing wrong. I know i saw it work with the miniifed 
version. maybe i'll give that a shot again

if i'm reading this script right, it attached to the wiki onload event (or 
equivalent), then looks for a span with the chartist class name which is 
rendered on to the page with %%, then scans for the tabular data, renders a 
chart and replaces the table with the chartist chart.

This is such a clever way to do this. I would have never thought of it.

> Add charting library to JSPWiki distribution
> --------------------------------------------
>
>                 Key: JSPWIKI-1102
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-1102
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Templates and UI
>            Reporter: Dirk Frederickx
>            Priority: Minor
>
> Add a charting library to JSPWiki for easy rendering data in TABLE's as line, 
> pie- or bar-charts.
>  The charting library should provide well chosen defaults to keep the extra 
> markup as little as possible.
> Proposal:
>  Include [https://gionkunz.github.io/chartist-js/]  (MIT license) in the 
> standard JSPWiki's distribution.
>  * small footprint  (10K zipped JS; only loaded in pages with require charts)
>  * usage of svg; high quality device independent
>  * highly customizable;  but using 'convention over configuration'  (great 
> defaults)
>  * responsive  (great output on mobile devices)
>  
> Prereq: https://issues.apache.org/jira/browse/JSPWIKI-1040
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to