A first graphic mode applicationA trivial graphic mode applicationLet's create a /pliant/myorg/appli2/converter.ui module with: module "/pliant/graphic/ui/server/api.pli" There are two possible methods for testing a Pliant graphical application: the command line, or the integrated development environment. Testing your application from the command lineYou could first test if your application compiles properly though the following command: pliant module /myorg/appli2/converter.ui If you get no error message, then your code compiles fine, so you can move to the next step and try to run it. The configuration we now choose for testing is to run both the client and the server within a single Pliant process, so that the connection will be both straight forward and secured using Pliant loopback streams. /pliant/fullpliant then connect to your application through clicking the 'url' button on the right of the screen and filling the 'URL' field that will appear in the top window with: loopback:/myorg/appli2/converter and finally press the 'go' button. You should see the 'My first graphic mode application' title application on top of the screen. Now, the drawback of this solution is that it may be long to start, and even more if you have a not that fast processor in your PC, so I'll now provide two tricks that you can use to speed up things a little bit: The first one has already been introduced the the command line development introduction and is named precompiling: pliant 'precompile /binary/ui.dump module /pliant/install/precompile.pli module /pliant/graphic/ui/client/main.pli module /pliant/graphic/ui/server/main.pli' module /pliant/fullpliant/run.pli The second one will not always work, but is much faster for testing tiny changes in your application: Apply changes to your application, then just select 'Tools' 'Development' 'Recompile' from FullPliant home menu. If you get no error reported at the top of the screen, then you can move back to your application URL to test the new code without restarting the all Pliant process. Testing your application from the integrated development environmentHere, we assume that you already created a logical computer named 'mydevel.mydomain.org' as described in the introduction to the integrated development environment. Now, we are going to create a development environment suited for our tiny graphical sample application: First, in 'General parameters' section: Remarks:
Then in 'Precompile' section: And in 'Test' section: And finaly in 'Links' section: Now, move back to the development environments pages through selecting 'Exit' twice, and select 'appli2' in the select field in the left window. Assuming that your 'mydevel.mydomain.org' logical computer has it's root path set to 'file:/logical/mydevel.mydomain.org/' then the sample application file we created earlier in this document (in the 'A trivial graphic mode application' paragraph) should be in file:/logical/mydevel.mydomain.org/pliant/myorg/appli2/converter.ui Now, you can test if the sample application compiles fine through using 'test' button at the right side of the '/myorg/appli2/converter.ui' input field. Then, when you want to run your applicatio, first check that the logical computer is running through Now, you can test your application through following the 'Converter' link. If you make some changes in your applications, you have two solutions. Et voilà ! |