AnyChart custom plugin

Hey team :wave:t3:

I’m looking to build a component that uses AnyChart’s Mekko chart. The component will need to be bindable and ideally have access to AnyChart properties in a similar way to the Chart.js ‘options.’

I’d love to use the existing charting plugin but unfortunately Chart.js doesn’t have Mekko charts available and these charts are the crux of the app I’m building!

AnyChart is a javascript library however, and as such will need some custom work to build a Vue component for it. They’ve already built a Vue 2 integration but I know that WeWeb needs Vue 3…

I’ve got no idea where to start here and would love any pointers!

Sorry for the confusing brief :face_with_spiral_eyes:

If you know js and vue you can start from the developer documentation

Thanks @dorilama! Unfortunately I hardly know js and don’t know vue at all - might need to contract someone in to build it.

Alternatively, I also thought about embedding the HTML (not as an iframe) and just binding the variables I need. Can you think of any reason why this might be a bad idea? Security, speed, scalability?

you can definetly use an html element at least for testing and assessing the idea. If you need to put user generated code in the html there are some thing to consider.
Of course a custom component is the preferred way.

1 Like

I took a run at livecoding a basic connection with a mekko chart. It was fun, illustrated some useful aspects of weweb, and hopefully helps with your question!


Wow. @raydeck I am speechless!

Thank you so much - will take my own run at it and let you know how I get on.

I’m looking forward to signing up to State Change. Currently we’re bootstrapped and I’m just working on this in my spare time, so once I’ve got more time to devote to it, you’ll be seeing a lot of me in your office hours :nerd_face:

Thank you again for your invaluable help. You’re a legend.

Hey @casey.hemingway Were you able to publish anycharts to production environment?

Hi @snehalparate - I’ve only played around in testing so far. Production will need a little bit of a different workflow.

Have you got a similar use case?