Mark this date to the encyclopedia as the first public preview release of the revolutionary reporting platform. It took 9 months including all the weekends to finalize works and we are very proud to announce that it's done.
I was having a big pain in my brain every time I was forced to do some pdf business reports generation for our customers. It was very nasty work in WYSIWYG designers like one from Crystal Reports or one from Telerik. These designers were structuring the reports all the time in different way that I wanted them to. It was also crushing visual studio on the regular basis. When it came to merging my report definitions with other developers, I was forced to manually merge quite big and dirty xml. So we rather dedicated one poor developer guy to do only reports. When we wanted to provide a way to customer to modify report templates, we needed to buy them a developer license of these tools and then import some xml definitions back to our system. Quite complicated. There are many other pitfalls but I will stop here.
I think that everything that is just wrong in current reporting software is the concept of some super fancy WYSIWYG editors that are creating some custom xml. This is the way developers will never like. Just think how often you use html WYSIWYG editors to write html page, or JSP page, or asp.net page. Developers don't like to click into some black hole. They like to code and have full control. The problem was that I was missing a platform that would allow me to code report and let me stay productive. I was trying to use xml/xslt/fop to generate pdf report, but I realized that it's not productive. I stopped and start to think.
What is the best approach to define report output using the source code?
Other blog posts about jsreport features will come soon, so stay connected.
If you want to try fiddling with jsreport, go ahead and try free playground
If you like to try enterprise jsreportonline, go ahead and sign up
If you are lost, tweet me to @jan_blaha or see the documentation