This commit is contained in:
2020-08-23 18:37:17 +00:00
parent 4a9c855226
commit 369de3ffaa

View File

@@ -37,7 +37,45 @@ TODO:
this way can just hit the route and view in the browser, rest is static at server
Make a test render method right inside teh controller for initial testing
headless chrome first, chrome already installed can probably just run it
TODO: SAMPLE REPORTS
Try all these with headless chrome first, if it suffices then don't bother with other renderers
Make a sample report with handlebars of each kind of report
Report off a single widget with handlebars
Report off a filtered widget list with handlebars
Report off a list with custom javascript functions for totals and subtotals
Report with logo
TODO: Sample reports from client end with passed in data like any of the data-table based ui pages
TODO: Sample reports from client with actual objects
TODO: Confirm basics before coding
Handlebars works properly
page breaks properly
Wiki renders prints
logo / graphics
custom javascript functions
Shared javascript libs
Localization
Localized dates and currency
Bar codes
Mailing labels
Alternate paper sizes A4, Letter etc
Reports on each type of data anticipated
Security of scripts / scrubbing or sandboxing
make sure can't access file system at server with a malicious report
TODO: build the report designer at client end
Need to get to a point where Joyce can do testing and whip up some reports and give feedback on improving that
Confirm it won't load extra stuff unless user actually designs report
If not then make it an external app or alternate or whatever it takes
----------- REPORTING NOTES ----------------------
CLIENT UI
At client maybe pick output format first then select report, so can pick HTML to just view immediately, can pick pdf to download or print, can pick csv to export etc