Carbone Roadmap 🚂

[steevepay]

Hello everyone,

I would like to share the roadmap for CarboneJS and the team's thoughts for the future! 🚀 First of all, thanks to the Github community for contributing and spreading the project. Carbone has been created for an internal project and we decided to open source it because of the increasing demand. We are glad to see a lot of you liked it! 💕A lot of evolutions, features, and issues are coming from the community in addition to the Carbone Team and we will consider every request. There is only one main goal: to keep Carbone to be the fastest and easiest report generator 🔥

Roadmap 🚂

The following list will be updated along with newly published releases.

• [ ] Fix PDF conversion tests on Windows #101
• [ ] Fix ODT to HTML conversion with images #100
• [ ] Fix multi-directional loops #45 #64
• [ ] Fix double quotes (deleting spaces) #59
• [ ] Evolution error management: print errors/warnings when markers are missing #7 #68 #54 #27
• [ ] Fix XLSX support #86 #48 #90 #102 #109
• [ ] [EE] support dynamic charts in ODT and DOCX #110
• [ ] benchmarks
• [ ] Create a contribution guide

Done

• [x] Fix formatD Warning #85
• [x] Feature dynamic hyperlinks #53
• [x] accepts PDF & Adobe Indesign IDML as template
• [x] Feature: add dynamic colors for ODS files and fix DOCX/ODT bugs
• [x] Update the documentation
• [x] Format numbers as number for XLSX and ODS files #13
• [x] Publish Carbone examples with specific use case
• [x] Golang/Python/Node SDK
• [x] Feature: use markers into formatters, example: {d.fruit:isEqual(apple, {d.successMessage})} #65 #40
• [x] Fix #57 #44 #76
• [x] [EE] XLSX support dynamic colors #51
• [x] 2.0.0 release: synchronize our private branch with the Github branch. Next changes and features will be pushed on the open-source version to avoid branch differences.

[HeyItsJs]

Hey guys, just found this tool a couple of days ago and it felt as if all my prayers were answered!! 😍 Couldn't thank you guys more!

A humble request though. Can we prioritize XLSX support before everything else and release it earlier as compared to other features? Most of the business application users are comfortable working with Excel. Hence I believe it will be beneficial to everyone.

Also, the date of this roadmap issue worries me a little. Is there an active contribution going on it?

[steevepay]

Hello @HeyItsJs,

just found this tool a couple of days ago and it felt as if all my prayers were answered!! 😍 Couldn't thank you guys more!

You are welcome!!

A humble request though. Can we prioritize XLSX support before everything else and release it earlier as compared to other features? Most of the business application users are comfortable working with Excel. Hence I believe it will be beneficial to everyone.

Our next priority is to upgrade the error management, print accurate and relevant messages to make the design process smooth when a language typo occurs. Though I consider your request, and XLSX support improvement will come after the error upgrades. However, a solution is available for you: Design ODS templates and export with Carbone as an XLSX document.

Also, the date of this roadmap issue worries me a little. Is there an active contribution going on it?

Since the creation of the CarboneIO organization a few months ago, we have had a lot of administration and legal stuff to complete. In the meantime, we made many contributions to the Carbone Enterprise edition as the same as Carbone Community Edition. Updates are coming and I am going to update the roadmap pretty soon ;) To get the latest news, latest work, or experimentations from the team, feel free to follow us on Twitter.

Have a great day and enjoy creating with Carbone!! 🎉

[LDami]

Hello,

There is no code changes for at least one year, is this project still maintained?

[steevepay]

Hello @LDami,

Carbone is actively maintained. The team is focused on the Enterprise version (Cloud API) in that way, we can continue the development and bring new features and fixes. We plan to publish a new version on Carbone Core (this repository) soon.

Follow the development on Twitter: https://twitter.com/carbone_io The changelog: https://carbone.io/changelog.html

[graycrow]

Ok, I understand the concept of being behind by one major version and the reasons why you went that route. However, it seems that bugs are not fixed in the community version, is that true? For example, there are a few bug reports in this repository, but not a single code fix has been made in 10 months, while the Enterprise version gets patches several times a month. If possible, can someone explain why it's not as bad as I think it is? Thanks.