SatForms Power Tip: Hiding The SF Runtime

----------------------------------------

 

The Problem:

 

If you hide the extensions, as noted in the accompanying document, you still will have a visible runtime.  Also, on earlier versions of the Palm OS (3.3 and prior) the icon for Satellite Forms will also be visible as well as your application icon.

 

The Solution:

 

You can create a "fat" application which hides the runtime under the same Creator ID as your application.  In this document, we will assume that your Creator ID is "CRID".  You also will need RsrcEdit plus SFPocketUtils to follow these steps.

 

Note:  It should be noted that these steps have not been approved by PUMATECH.  We have tested the method, but proceed at your own risk.  You should be thoroughly comfortable with the techniques mentioned, and you are encouraged to test this thoroughly before distribution.  Improper use of these techniques may cause your application to malfunction or break other applications.

 

The following example uses version 4.1.  You will need to make appropriate changes if you are using version 5.x.  This has not been tested on versions before 4.1.

 

1.      Create your application and load into POSE, along with RsrcEdit.  As your application opens, you will need code using SFPocketUtils to change the Creator ID of  SF-EE_SysHeap (and SF-EE_SysHeapRSC if you have 5.2) to CRID.

2.      Open RscrEdit and change the name of SF41RDK to CRID_SF41RDK

3.      Change the creator of SF41RDK to CRID.

4.      Change the type of SF41RDK to HppA.  Apply your changes.

5.      Change the tSTR 1100 resource in the application prc from SF41RDK to CRID_SF41RDK.

6.      Optional:  You can also open tver 1000 and change the version number of your app.

7.      Apply your changes.

8.      Test your application.  You should just see your application icon and there should only be one visible file in the Palm Delete/Info Menu.  You can view the version number in the Info menu.

9.      Right-click on Pose and export the changed files to your desktop.  These need to be distibuted with your application.

 

Note:  SF-EE_SysHeap (and SF-EE_SysHeapRSC if you have 5.2) is created the first time that SF41RDK is run, and it has the default Creator ID of SMSE for the RDK (and SMSF for the SDK).  This file is created if it is not present, but is not created if it already exists.  Your application will change the Creator ID of this file.  If you remove your application, this file will be removed as well.  However, if there is still another application on the handheld which uses the RDK or SDK, the file will be re-created as that application opens.

 

Do not redistibute SF-EE_SysHeap with your application.  This needs to be created by the RDK or SDK on the Palm.

 

 

Jon Blackman, MD, MS

www.pocketinformatics.com

 

David Thacker

www.palmdatapro.com

 

Revised 01/07/2003