This commit is contained in:
@@ -5,30 +5,68 @@
|
||||
REPORTING
|
||||
|
||||
Procedure:
|
||||
|
||||
read notes in project including any related spec docs
|
||||
Look at existing reports in v7 and generalize them and the features provided that are used
|
||||
pdf, email, print, download
|
||||
print / download / email / export immediately as an option no only preview and then those other things
|
||||
custom fields must be available, perhaps as widgets that handle if they are present or hidden and etc
|
||||
whatever is easiest from a design point of view
|
||||
wiki must be a type of field like any other that can be inserted into a report and will properly render
|
||||
this way they can make a report with only a wiki or a report with a hybrid data and wiki or whatever
|
||||
and it flows with how the wiki is now just a field on the data object like any other
|
||||
grid filter options and filter name must be an available field for report designer
|
||||
probably need a filter summarizer widget that can also be used inside the UI at the top of grids as well
|
||||
logo field with choice of size to correspond to the logo route
|
||||
graphs and charts that show in UI should be printable / KPI Metrics stuff
|
||||
labels wtf?
|
||||
notification needs to be able to generate reports and send them
|
||||
Schedule form reporting
|
||||
keep in mind, but ultimately it's probably a dedicated schedule thing
|
||||
REQUIREMENTS
|
||||
Look at existing reports in v7 and generalize them and the features provided that are used
|
||||
pdf, email, print, download
|
||||
print / download / email / export immediately as an option no only preview and then those other things
|
||||
custom fields must be available, perhaps as widgets that handle if they are present or hidden and etc
|
||||
whatever is easiest from a design point of view
|
||||
wiki must be a type of field like any other that can be inserted into a report and will properly render
|
||||
this way they can make a report with only a wiki or a report with a hybrid data and wiki or whatever
|
||||
and it flows with how the wiki is now just a field on the data object like any other
|
||||
grid filter options and filter name must be an available field for report designer
|
||||
probably need a filter summarizer widget that can also be used inside the UI at the top of grids as well
|
||||
logo field with choice of size to correspond to the logo route
|
||||
graphs and charts that show in UI should be printable / KPI Metrics stuff
|
||||
labels wtf?
|
||||
bar codes, holy fuck this looks good: https://github.com/metafloor/bwip-js used by jsreport too in sample
|
||||
notification needs to be able to generate reports and send them
|
||||
Schedule form reporting
|
||||
keep in mind, but ultimately it's probably a dedicated schedule thing
|
||||
|
||||
test harness UI so can quickly test out things via widget list
|
||||
if it's faster, just whip up some kind of standalone project for testing?
|
||||
|
||||
Once clear on needs, research solutions online
|
||||
This case has a lot of old research in it:
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3451
|
||||
look at commercial ones just to steal ideas
|
||||
|
||||
POTENTIAL STRATEGIES
|
||||
HTML to PDF generated at the server then downloaded or viewed
|
||||
JSREPORT commercial tool seems to do this and if you look at their samples in their designer it gives clues as to how we could do it ourselves
|
||||
|
||||
OPEN SOURCE TOO: https://github.com/jsreport
|
||||
|
||||
Their example playground for designing their sample reports shows exactly how they do it, it's like I imagined, templated like mustache / vue exactly
|
||||
probably rendered to pdf need to dig more and the samples show exactly the types of css and html features needed to do reporting
|
||||
https://playground.jsreport.net/w/admin/dI2_fUqZ (for example this sample report shows <div style="page-break-before: always;"></div> which is interesting)
|
||||
|
||||
The examples are golden for me if I want to go this route, they showcase solutions to literally all the problems I recall Joyce mentioning.
|
||||
Here is how they describe the overall concept: " The original concept based on javascript templating engines and pdf converters has been proven in time by more than 200 000 downloads."
|
||||
|
||||
|
||||
|
||||
|
||||
OPEN SOURCE TOOLS
|
||||
JSREPORT it's fucking open source completely!!!
|
||||
https://github.com/jsreport
|
||||
I can just pore over it and get the gist of what I need
|
||||
|
||||
Definitely something here but not sure if it's appropriate or not:
|
||||
https://github.com/FastReports/FastReport
|
||||
They have commercial versions, not clear what this open source one is specifically in relation to the rest but it puports to be free and work on .net core
|
||||
|
||||
COMMERCIAL REPORTING TOOLS FOR REFERENCE / IDEAS
|
||||
Seems as though they render on the server then just transport somehow to the client
|
||||
maybe canvas, as an image, etc
|
||||
https://www.telerik.com/blogs/using-telerik-reporting-in-net-core-applications
|
||||
HTML, PDF and OpenXML-based renderings are supported on Linux/macOS.
|
||||
uses GDI to draw to and requires a libgdiplus library for linux macos to replicate Windows method
|
||||
Seems like it's not a step in the right direction as it's very Windows graphical in nature and they just try to throw a shim over it on linux
|
||||
|
||||
JSREPORT
|
||||
https://playground.jsreport.net/w/admin/dI2_fUqZ
|
||||
|
||||
todo: from reporting specs doc, not vetted, was written a while ago:
|
||||
- All v7 reports ported to RAVEN
|
||||
@@ -387,4 +425,23 @@ mcao 2 hours ago [–]
|
||||
|
||||
It's all done in Photoshop. Just take screenshots, then transform, rotate, distort them to look flat. Then add some drop shadows for a 3d look.
|
||||
|
||||
reply
|
||||
reply
|
||||
|
||||
|
||||
|
||||
|
||||
Good day. I have a pricing question.
|
||||
|
||||
I have a software company and am the sole developer and am looking to add reporting to my business software product I will be selling to companies as a product they can install themselves and also will be offering that software as a SAAS rental version I will be hosting for those that don't want to install it themselves.
|
||||
|
||||
The project is an asp.net core webapi back end with a Vue html 5 based front end client. My customers will need to be able to design / modify / view / export their own reports off the provided data sources using only an HTML 5 browser at the Client end.
|
||||
|
||||
I am investigating rolling my own reporting solution however if the price is viable I might go with a commercial solution such as yours to save time.
|
||||
|
||||
Users will need to be able to design reports off our provided data sources as well as print / view and export. It needs to work with asp.net core Windows / Linux / Mac at the back end web api and any modern HTML 5 browser at the client end.
|
||||
|
||||
To be clear this would be used in a business software product I am selling directly to my customers who would be using the reporting feature to design / modify and print reports provided by my software for their business. I would provide sample reports they can customize or use as is.
|
||||
|
||||
Do you provide licensing that supports this and how much will that cost for a single developer?
|
||||
|
||||
- John
|
||||
Reference in New Issue
Block a user