Suggestions for manuals

Hello

After going through the PDF's, I could successfully build my first report, with a couple of Text objects and a Barcode object. Couldn't be easier :-)

Here's some feedback on the documentation:

1. The PDF starts with how to use the Designer utility (keyboard shortcuts, menus, etc.) I think it'd be better to have a short introduction to what a reporting tool does (not all developpers have used reporting tools before), the main concepts, and how to build, preview and print a "Hello, World!" text from a Delphi project, so the user is up and running fast.

2. In the User's Manual, I was unable to find how to open the report from a Delphi form, ie. "frxReport1.ShowReport;". I had to look for this in the Programmer's Manual.

3. I'm not sure it makes sense to have three manuals, User's Manual, Developer's Manual, and Programmer's Manual. Since FastReport is a development tool, I think it makes more sense to have a User's Manual, and possibly a Reference Manual for a list of methods and properties for each component.

My .15??¬

Comments

  • gordkgordk St.Catherines On. Canada.
    edited 9:45PM
    no matter where one starts you can never satisfy everybody.
    read the programmers manual as working from delphi, the users manual as working from within the report and its scripting,
    the developers manual as to how to create custom objets and function libs for fr.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.