> Would the RB Server architecture allow a Flash Remoting MX client to be
The next release will allow for custom paramters, so I would think that this would be doable (I haven't worked with Flash or seen a beta of the next version). You may want to review some of the threads posted here and see some comments from Nard @ DM about it.
I am not familiar with how Flash MX remoting works.
However I definitely think that is doable. I assume that you want to create a Flash previewer, rather than the XHTML viewer that we offer. Would you still want the report pages to be displayed in XHTML? Can you describe more details about what you want to accomplish?
One approach would be to write a custom content provider for the RB WebTier. We do yet not have any examples, so this would require my help.
Antother approach would be to not use the WebTier component at all. Instead you would use the ClientReport object to build your own. You would be losing the functionality of the WebTier that manages sessions, caching, garbage collection, etc.
The objective of doing a Flash Remoting MX front end is to get a very responsive, flexible front-end. It would allow us to create our own visual experience. The current solution (looking at the demo) is not the most visually interesting application.
We have a point of sale application to we are looking at putting on the web and due to the interactive nature of it, it will not work with html rendered pages. Hence our investigation of Flash Remoting MX.
I realize that you are trying to provide an improved user experience - that is what Flash is typically used for.
There will be two parts to creating any Viewer: One part is the fixed previewer controls - the navigation buttons, zooming controls, Search button, etc. The Viewer must be able to communicate with a web server application in order to request report pages, request that a page be scaled for zooming, request that the search dialog be displayed, etc. This looks the same for every report. The second part will be the report pages that represent the report output.
If you do not want to use XHTML for the pages, then you will need to write a TppDevice class descendant that receives the TppPage objects from the server and then translates them to flash or to to some other format the browser can render. This is how all devices such as TppPrinterDevice and TrsXHTMLDevice work. See ppFilDev.pas for in RBuilder\Source for some simple examples. The Report and ClientReport objects can be used with any TppDevice descendant. Thus, the formats supported by RB add-ons such as Waler and Pragnaan products.
Comments
The next release will allow for custom paramters, so I would think that this
would be doable (I haven't worked with Flash or seen a beta of the next
version). You may want to review some of the threads posted here and see
some comments from Nard @ DM about it.
--
Ed Dressel
Team DM
I am not familiar with how Flash MX remoting works.
However I definitely think that is doable. I assume that you want to create
a Flash previewer, rather than the XHTML viewer that we offer. Would you
still want the report pages to be displayed in XHTML? Can you describe more
details about what you want to accomplish?
One approach would be to write a custom content provider for the RB WebTier.
We do yet not have any examples, so this would require my help.
Antother approach would be to not use the WebTier component at all. Instead
you would use the ClientReport object to build your own. You would be losing
the functionality of the WebTier that manages sessions, caching, garbage
collection, etc.
Post more details here...
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
responsive, flexible front-end. It would allow us to create our own visual
experience. The current solution (looking at the demo) is not the most
visually interesting application.
We have a point of sale application to we are looking at putting on the web
and due to the interactive nature of it, it will not work with html rendered
pages. Hence our investigation of Flash Remoting MX.
Terry.
I realize that you are trying to provide an improved user experience - that
is what Flash is typically used for.
There will be two parts to creating any Viewer: One part is the fixed
previewer controls - the navigation buttons, zooming controls, Search
button, etc. The Viewer must be able to communicate with a web server
application in order to request report pages, request that a page be scaled
for zooming, request that the search dialog be displayed, etc. This looks
the same for every report. The second part will be the report pages that
represent the report output.
If you do not want to use XHTML for the pages, then you will need to write a
TppDevice class descendant that receives the TppPage objects from the server
and then translates them to flash or to to some other format the browser can
render. This is how all devices such as TppPrinterDevice and TrsXHTMLDevice
work. See ppFilDev.pas for in RBuilder\Source for some simple examples. The
Report and ClientReport objects can be used with any TppDevice descendant.
Thus, the formats supported by RB add-ons such as Waler and Pragnaan
products.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Thanks for your comments.
Terry.