| 1 |
Core capabilities allow simple wrapping of existing codes
|
| 2 |
Program objects is defined as an XML file e.g. my favorite physics simulation on my PC becomes: <program name="physicssimulation1"> <run domain="npac" machine="maryland" type="pc" os="nt" >c:\myprogs\a.out</run> <input button="prog1" toolbar="physics" type="htmlform" > <name>userinput</name> <field default="10" maximum="100000" >iterations</field> ............ </input> <output>
...</output> </program>
|
| 3 |
Gateway generates a distributed object with
-
the button prog1 in physics toolbar
-
This button generates HTML form reading parameters
-
Form input data are checked and backend code activated
-
Parameters can be accessed by running code through Gateway linked library (call getparm("iterations") etc.)
|
