Add or change the “config” parameter in the menu item link to “&config=advanced”. Then IceCap will use the “advanced” part of the icecap_config.xml file.
IceCap try to recognize the 5250 subfile, and convert it to a grid using in “optionText”, “optionField” and “subfileEndText” tags from the “advanced” part, and saved the recognition into the xml file specified in the “hintsXMLhive” and “hintsXMLpath” tag. It is the “method” tag, which tells IceCap to emulate with “advanced” functions and layout.
It is the same with the "icecaped" method as “advanced”, but use the “icecaped” part of the icecap_config.xml file. The difference between “advanced” and “icecaped” method, is primarily, that the “icecaped” method, insert option field in the grid and you get a “gear” icon in the upper right corner (described later).
You can create as many “group” tag in the icecap_config.xml file as you like, just like “advanced” and “icecaped”, and use different break out programs for each “group”.
This example is for one of own products “IceQuery”:
Re: Advanced rules and icecaped rules
Add or change the “config” parameter in the menu item link to “&config=advanced”. Then IceCap will use the “advanced” part of the icecap_config.xml file.
IceCap try to recognize the 5250 subfile, and convert it to a grid using in “optionText”, “optionField” and “subfileEndText” tags from the “advanced” part, and saved the recognition into the xml file specified in the “hintsXMLhive” and “hintsXMLpath” tag. It is the “method” tag, which tells IceCap to emulate with “advanced” functions and layout.
It is the same with the "icecaped" method as “advanced”, but use the “icecaped” part of the icecap_config.xml file. The difference between “advanced” and “icecaped” method, is primarily, that the “icecaped” method, insert option field in the grid and you get a “gear” icon in the upper right corner (described later).
Re: Advanced rules and icecaped rules
Can we have multiple break out programs to reduce their size. Is there a need for this to aid performance?
Re: Advanced rules and icecaped rules
You can create as many “group” tag in the icecap_config.xml file as you like, just like “advanced” and “icecaped”, and use different break out programs for each “group”.
This example is for one of own products “IceQuery”:
Use this “group” by specify it, in the menu item link: “&config=iceQuery”.
Re: Advanced rules and icecaped rules
Is there any documentation/guides/examples we can use?
Re: Advanced rules and icecaped rules
Currently, just the examples in the source file QSAMPLE in library ICECAP, and the documentation of the “IceCap emulator APIs” under “Administration”.