Hi Suho, I was thinking replacing Arc with a Gauge since it'll be more useful for real-time usecases. IMO compared to Arc, gauge will be more realistic when visualizing fast moving data points. WDYT?
Regards, Dunith On Thu, Oct 29, 2015 at 7:23 PM, Sriskandarajah Suhothayan <[email protected]> wrote: > > > On Thursday, October 29, 2015, Dunith Dhanushka <[email protected]> wrote: > >> Hi Tharik, >> >> Good intiative! >> >> I'd like to add few comments. >> >> - Upgrade Vega version to 2.0 >> - Need to eliminate few shortcomings of the line chart. E.g Tooltip not >> displaying at sometimes. >> - Let advanced users to pass vega specifictions directly with the chart >> configuration. This needs to be discussed further. This will allow users to >> manipulate vega attributes directly like legend position, label font size >> etc. >> >> - Define standard methods like init(), draw() and update() for all chart >> types. Enforce chart developers to implement them so that those methods can >> be called by Vizgrammr at runtime. >> >> - Keep the main interface of vizg object simple. E.g >> vizg.draw("#canvas,chartConfig,dataTable) >> - Remove the arc chart type. >> > Why we need to remove arc type ? > It should work for real-time use cases > > Suho > >> >> It would be nice to improve the existing drill down capability of bar >> charts and also find out other chart types that supports drill down. >> >> Regards, >> Dunith >> >> >> On Wed, Oct 28, 2015 at 3:40 PM, Tharik Kanaka <[email protected]> wrote: >> >>> Hi All, >>> >>> At the moment we have moved igvis content to VizGrammar repository [1]. >>> We are going to redesign the architecture of igviz.js and improve >>> extensibility. First igviz name will be replaced as VizGrammar. >>> >>> Currently all the chart drawing logics are written in the igviz.js and >>> it will be a tedious process to add new chart types and update. >>> >>> For that we are expecting to create structure as follows where each >>> chart type code is in a separate JS file. These JS files follows a same >>> structure when it comes to drawing, plotting and updating. If new chart >>> type is implemented, it needs to follow same structure and code will be in >>> a separate JS file under charts directory. Meanwhile samples for charts can >>> be included the samples directory. >>> >>> |- lib >>> | |- vega.min.js >>> | |- d3.min.js >>> | >>> |- samples >>> | |- bar >>> | |- line >>> | . >>> | . >>> | |- scatter >>> | >>> |- charts >>> |- |- chart.js >>> |- |- chart.bar.js >>> |- |- chart.line.js >>> |- |- chart.area.js >>> |- |- chart.map.js >>> |- |- chart.table.js >>> |- |- chart.arc.js >>> |- |- chart.scatter.js >>> | >>> |- vizgrammar.js >>> |- vizgrammar.min.js >>> >>> >>> Finally chart JS files will be combined to create vizgrammar.js and >>> vizgrammar.min.js. >>> >>> [1] https://github.com/wso2/VizGrammar >>> >>> Regards, >>> -- >>> >>> *Tharik Kanaka* >>> >>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka >>> >>> Email: [email protected] | Web: www.wso2.com >>> >> >> >> >> -- >> Regards, >> >> Dunith Dhanushka, >> Senior Software Engineer >> WSO2 Inc, >> >> Mobile - +94 71 8615744 >> Blog - dunithd.wordpress.com <http://blog.dunith.com> >> Twitter - @dunithd <http://twitter.com/dunithd> >> > > > -- > > *S. Suhothayan* > Technical Lead & Team Lead of WSO2 Complex Event Processor > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > > -- Regards, Dunith Dhanushka, Senior Software Engineer WSO2 Inc, Mobile - +94 71 8615744 Blog - dunithd.wordpress.com <http://blog.dunith.com> Twitter - @dunithd <http://twitter.com/dunithd>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
