Skip to main content

12 posts tagged with "Charticulator"

View All Tags

Charticulator app deployment

· One min read
Ilfat Galiev
Ilfat Galiev
Software Engineer

Since the version of Charticulator from Microsoft is retiring, I decided to deploy to GitHub Pages the latest version with fixes and some new functionality. Unfortunately all this new stuff is not included in the Power BI Visual. In the next 2 months I plan to prepare alternative versions of visuals.

Charticulator app

The first stage is practically accomplished. In which I upgrade the UI library to Fluent UI 9. Since the first version doesn't work with React 18+ fully.

The upcoming work is fixing critical bugs in the current version of the visual, which block the implementation of the full cycle of chart development in the Power BI report.

Charticulator visual

· 2 min read
Ilfat Galiev
Ilfat Galiev
Software Engineer

It past a year after the first attemp to give breath Charticulator visual. I didn't get any feedback on the first version at the time, neither bad, good, or error message, but they were there.

Here's a second attempt. I will have the opportunity to publish a version on AppSource, I think it should help to find the old audience.

I forked the Charticulator source to my repository on GitHub, which is used internally by the new visual.

https://github.com/zbritva/charticulator

It already contains fixes and features that were not included in the original.

Editor is avialable for preview on https://ilfat-galiev.im/charticulator/.

And, yes, there is no httpS. Do not use for production

The source code for the new visual has been published on Github:

https://github.com/zBritva/charticulator-visual-community

The main difference from orginal Charticulator​

The visual will be split into two parts. The first includes the Charticulator editor UI. The second includes only engine to render charts.

Report authors will have to use one visual to edit the chart and switch to the second visual before saving the report.

This approach allows:

  • significantly decrease the package size.
  • easier to obtain certification for the second, because less code for review.
  • Keeping the first (editorial) version uncertified opens your hands for more technical possibilities, (downloading from the gallery or moving part of the editor code to CDN and so on).

Community​

Fell free to open any discussion on GitHub, even it is about closing.

The road map is stabilization and close workflow of the visual. Then submitting the first versions to AppSource.