The power of the reports.rsp approach is great, but with hundreds of reports in our current app, we really need a visual designer to recreate the reports, and even move further in the area of visual design for reports.
It would be great if, in addition, we could design our own "gadgets" for inclusion in reports, and have those available to drop on subsequent reports.
thanks,
Hank
So what's wrong with using pages? The section headers can be turned off at runtime and you can print the page. We are not planning to build a visual report designer but that's something that could be developed as a tool or plugin.
Maybe I'm not getting the full import of your suggestion to print the page. Our reports can (based on user selection criteria) run 20 pages. They can have 3 levels of grouping. Layout is crucial. Having many, detailed, and flexible reports is a pre-requisite for selling to our Enterprise customers, where looking at sales, inventory, and orders is what retail managers do a lot of every day.
It would be better to generate reports in HTML5 in a webview as these can be printed or generated as PDF files. That's how the attachment reports were generated and uploaded as attachments. This functionality works across desktop, web and mobile.
You should be able to generate reports in a webview component which is a class in the framework.
After v1.0 ships we will look at enhancement requests and prioritize their development based on demand. Thanks for you continued feedback hank, we appreciate it.
You can include template code inside .rsp pages using:
Special treatment is given to files with the following extensions; htm, html, css, js. These are injected into the html output as it is generated.Code:<%@ include="filename.ext" %>
Also you can run codebehind:
Code:<%@ codebehind="filename.prg" %>
Yes, I'm impressed with the base-level capabilities. We can do a lot with that, for sure.
Originally Posted by lianjasupport
Posting Permissions
Reply With Quote
Bookmarks