Dyalog Primer - Packaging Applications
ExplorationWorkspace package.dws looks like this...
c:\dick\temp\package saved Tue Jul 10 15:03:04 2007
∇ foo w;⎕IO;⎕ML
 f←⎕NEW'Form'(('Coord' 'Pixel')('Size'(200 200))('Caption' 'Howdy'))
 f.OK←f.⎕NEW'Button'(('Caption' 'Press Me')('Size'(100 100))('Posn'(50 50)))
∇ ∇ fooclose msg
Save as Type Bound Executable
Close APL, navigate to the folder that contains your new executable file and double-click.
goal is to make an executable file that will "just run", without the
end-user being aware that the application is written in APL.
need to set a latent expression to start the code running.
the main form closes we need to make sure that APL isn't left hanging.
run APL-sourced executables on PCs that don't have APL installed you
need to make sure that the file dyalog110rt.dll is installed and
accessible via the path.
- More complex applications
(for example, using .NET components) may have additional file
only must you ensure that your application doesn't depend on the APL
session, you should also ensure that unexpected errors (is there
another sort of error?) are handled appropriately.
User Guide Chapter 1 - Runtime Applications and Components
- Dyalog Interface Guide - Writing ActiveX Controls in Dyalog APL
- Dyalog .NET Interface Guide
- Writing .NET Classes in Dyalog APL
- Writing ASP.NET Web Pages
- Writing Custom Controls for ASP.NET
- Visual Studio Integration
a workspace which contains code to do something fairly simple (for
example displaying a form showing the current date and time along with
a Close button). Save this workspace as an executable file and
run it. Confirm that you can also run it on another PC which has
not had Dyalog APL installed.
- Work through the Dual example in the "Writing ActiveX Controls" chapter of the Dyalog Interface Guide.
- Work through the examples in the "Writing Net Classes" chapter of the Dyalog .Net Interface Guide.