Gaining better experience by converting input data

Alexander Bub

It is a regular situation when a developer has to deal with the input data having the structure not really suitable for the report output. Of course, it would be a lot more convenient for the developer if the input data was initially converted to a proper format, but this could cause a number of problems. First of all, if the data is presented by the subsystem the developer cannot affect, it would cause difficulties in data coordination. Secondly, as we know, many various reports can use the same data and this would make the generation of specific input data for each particular report quite an uncomfortable task . Thirdly, the report structure can vary easily and rewriting the data subsystem each time is not the best thing a developer can think of. On the other hand, the developer can use the initial data format without modifying it, but this can also be unacceptable as the report complexity would increase without a necessity.
Read the rest of this entry »

April 16th, 2014

Check the updated live demo of HTML5 (JavaScript) report viewer

Ekaterina Nebogina

We’ve just piblished the updated web demo of our SharpShooter Reports.Web reporting component. This is a native HTML5 (JavaScript) component that can be easily integraed in MS MVC and ASP.NET applications to view the professionally designed reports.
HMTL5 report viewer demo Read the rest of this entry »

April 11th, 2014

SharpShooter Reports 7.1 is announced

Ekaterina Nebogina

Perpetuum Software is glad to announce a new version of the multiplatform reporting component that features improved export to Excel and updated report viewers for Silverlight, WinForms, WPF and HTML5 – SharpShooter Reports 7.1.
.net reporting component
  Read the rest of this entry »

April 4th, 2014

Taming the CrossBand: Part 2

Alexander Bub

In our previous article we described how to display the table with the dynamic structure.
cross tab report
At this point a user may be puzzled with reducing of the table columns width, and it really seems quite logical. Basically, one of the approaches to do this, would be reducing the columns width in a template, but here we would come across a couple of problems. On one hand, we can apply our modification only to all table columns at once, and on the other hand, we cannot predict to what extent the values can grow and how big the numbers can become, thus insufficient cell space to store one of such values would make the table view unacceptable. The same thing can happen to the column that stores the parameter names. What if we should output the parameter called ‘TheReallyLongParameterName’? Most probably, the parameter name won’t fit the cell size as well. So puzzled by the question to find a workaround, we can say for sure this is a feasible task when some useful advice is available at your hand. We only need to know how to calculate the columns width. That is what we are going to talk about further in this article. Read the rest of this entry »

March 26th, 2014