3 ms·

This is very cool and something that appeals to me as someone does a blend of web and data work. A constant problem I run into is making good reports quickly. L

This is very cool and something that appeals to me as someone does a blend of web and data work. A constant problem I run into is making good reports quickly. Like you mention, I don't have time to hand code it, but no code dashboards are both slow and tedious to make and the quality is terrible. I have a couple questions. 1. I work in research and we use a lot of strange databases and query languages, how hard would it be to add support for new databases (or alternative sources like CSVs or API calls) and to include multiple sources in the same report? 2. I had trouble telling from the docs how hard it was to drop in hand coded components (say I have some D3 creation, or I have some requirement that breaks the model and requires JavaScript and CSS to change everything)?

amcaskill 5y ago
Thanks for the kind words! 1. Yes, if you have specific DBs, please feel free to create an issue on Github. We're also working on opening up the DB connector ecosystem so that people can add their own. I've also opened an issue for CSVs, I think we could support them pretty seamlessly. 2. Evidence is actually pretty slick in this regard. This is one of the benefits from starting from a web framework and working backwards towards the data analyst, rather than starting from Jupyter and trying to work forwards (if that makes sense). The markdown documents compile to svelte components, so you can just add <script> tag, and/or a <style> tag right into your .md file. d3 works pretty seamlessly in svelte, so you can go nuts. The other neat thing is the styles scope themselves to the We haven't written the docs for this portion yet, but you can also add global svelte components to your project, so if you wanted to write something re-usable you can write it that way, and then just import it into your reports to use it as a component. In either case, you could call out to other APIs if you didn't want to retrieve data via a SQL query. As an example, an add-on component library we'd like to build is an interface to FRED data from the St Louis Fed. That way if you just need a quick chart of GDP, or you want to add recession shading to one of your charts, you can just drop it in without having to load that data into your database. <FredTimeSeries ref=gdp/> that type of thing.

amcaskill 5y ago

Thanks for the kind words! 1. Yes, if you have specific DBs, please feel free to create an issue on Github. We're also working on opening up the DB connector ecosystem so that people can add their own. I've also opened an issue for CSVs, I think we could support them pretty seamlessly. 2. Evidence is actually pretty slick in this regard. This is one of the benefits from starting from a web framework and working backwards towards the data analyst, rather than starting from Jupyter and trying to work forwards (if that makes sense). The markdown documents compile to svelte components, so you can just add <script> tag, and/or a <style> tag right into your .md file. d3 works pretty seamlessly in svelte, so you can go nuts. The other neat thing is the styles scope themselves to the We haven't written the docs for this portion yet, but you can also add global svelte components to your project, so if you wanted to write something re-usable you can write it that way, and then just import it into your reports to use it as a component. In either case, you could call out to other APIs if you didn't want to retrieve data via a SQL query. As an example, an add-on component library we'd like to build is an interface to FRED data from the St Louis Fed. That way if you just need a quick chart of GDP, or you want to add recession shading to one of your charts, you can just drop it in without having to load that data into your database. <FredTimeSeries ref=gdp/> that type of thing.