Changes between Version 5 and Version 6 of Docs/Prog/Manual/Development/AppSigning

Timestamp:

09/25/12 16:11:07 (12 years ago)

Author:

Don Wilson

Comment:

--

Docs/Prog/Manual/Development/AppSigning

@@ -3 +3 @@
 Developers may create an application signature file to for their applications. A license file must be requested from Cardinal to identify the developer company name.
 
-To generate an application signature after the application executable is created. The "appsign" program is ran providing the name of the application and the path of the executable. For example:
+To generate an application signature after the application executable is created the "appsign" program is ran. The command line must provide the name of the application and the path of the executable. For example:
 
 {{{
@@ -15 +15 @@
 }}}
 
-You application program must include an "About" box or similar screen display which will display the application name your company name. In the example above this is "My App" and "MyCompany". If the application program does not contain this the signature file will not be created and an error message will appear.
+You application program must include an "About" box or similar screen display which will display the application name and your company name. In the example above this is "My App" and "MyCompany". If the application program does not contain this the signature file will not be created and an error message will appear.
 
-The signature must be regenerated after each change and compile of your program. This may be added to Eclipse as a post build step so that it is not necessary to do this each time from the command line.
+The appsign program must be ran after each change and compile of your program to regenerate the signature file. The command line may be added to Eclipse as a post build step so that it is not necessary to do this each time from a terminal window.
 
 The appsign utility is attached to this page. Contact Cardinal to have the license file generated for your company.