From Browser Client to Rich Client Applications (Magic xpa 3.x)
When changing your application from the Browser Client paradigm to the Rich Internet paradigm, there are some behavioral changes that you need to take into consideration.
The Rich Client application provides pulldown menus that have the look and feel of your operating system. You should use those menus instead of your own code. This will give your application a client/server look and feel.
A Rich Internet application has its own built-in Logon screen. You should consider using this screen instead of your own.
Output files (such as a PDF or HTML files) displayed in a browser can be displayed in Rich Client by using the Browser control. This will give you control over the look and feel.
Output Merge reports can be displayed in Rich Client by using the Browser control. The Output Merge reports do not have the same context, so any parameter passed by these tasks should be passed explicitly.
JavaScript functions can be executed by using a Browser control.
When changing the Task Type from Browser to Rich Client all the original Browser forms are copied to the end of the Form Editor. The original forms are then changed to a Rich Client interface.
The Rich Client form has to be recreated with all of the relevant controls, since there is no conversion path from HTML to Rich Client.
-
If the Browser Client used a CSS file, the colors and fonts should be added to the Magic xpa application color and font files.
-
A Browser Client program that contained frames should be converted to a Rich Client Frames form. All Call operations using the Destination Frame property should use the Destination property instead.
-
All images should be set with full URL paths pointing to the images. Images referred to by UNC format will not be cached.
Implementing the alternate background color on a table can be implemented using the Table Control properties.
