Skip to main content

Show HN: Create auto-updating charts-as-images with low-code/nocode https://ift.tt/oEugnpz

Show HN: Create auto-updating charts-as-images with low-code/nocode Hello, we just released Image Charts 2.0, a way to create and show a chart as an image anywhere using our custom API and integrations with Zapier and Make. My friend Francois-Guillaume made Image Charts in 2015 to replace Google Image Charts for a project since it was deprecated. Since then we’ve been adding features and getting it integrated with Zapier and Make to make it easy to build good-looking charts automatically. Each chart has a custom URL and HTML code so it’s easy to embed. And you can build progress bars, gradients, and really any kind of chart with it (bar, line, radar, scatter, you name it). We have a gallery of over 30 charts and counting. [Chart gallery]( https://ift.tt/g8fhcrG... ) with sample data The site with the live Editor: [ https://www.image-charts.com/](https://www.image-charts.com/... How-to with gradient fills: [ https://ift.tt/bAFIviJ... How-to progress bars: [ https://ift.tt/cwo4jx1]... Really looking for feedback and additional use cases, we know it’s used for reporting, transactional emails, and a customer suggested using it in weekly standups for a KPI’s snapshot too. Would love to hear what you think and/or how you would use this. Cheers! https://ift.tt/1QwE4Li December 13, 2022 at 01:56AM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...