This is a template App that has the basic structure already created and you just
have to modify it and insert your content.  In this document appName and AppName
are the strings you are to replace with the name of your app.  It can not
contain spaces in the name (standard perl module naming conventions).

First rename the directory to the name of your app: pcx_portal_example => 
pcx_portal_appName

Secondly, rename the Example.pm => appName.pm (starting with an upper case 
letter)
Then, move Example => appName (same case as with the .pm file)
Now, edit all .pm files and replace the package Portal::Example with package 
Portal::AppName (same case as directory).
Now, edit pcx_portal_example.spec, MANIFEST and Makefile.PL to have the correct
file names for what your .tar.gz file will eventually be, etc.

Edit the setup.pl script in install/scripts so that the correct preferences are
defined for the setup program.  Also, edit the Example.xml config file to 
reflect the correct module name and version.

Do a './distribute' to build the tarballs.

NOTE: rpm's are no longer being maintained, so the spec file may be broken.
If you want to make an rpm, cp the tarballs to /usr/src/redhat/SOURCES and the
spec file to /usr/src/redhat/SPECS.  cd to /usr/src/redhat/SPECS and issue
rpmbuild -ba specfile

After the rpm is done (with no errors) the binary and source rpms are now
available to test installing, etc.  They are in /usr/src/redhat/RPMS/i386/
and /usr/src/redhat/SRPMS/

When building the rpm, the application should not attempt to configure itself
or register itself with the portal as this will cause problems!  :)


Building Debian debs.
Use your favorite build command using the libpcxportal-App-perl tarball first
and then building the pcxportal-App tarball next (where App is the name of the
Portal Application you are building).

Make sure you update the control files to reflect the versions of the Portal
being used and of the app in question.

If you have any questions not covered here on the process of building a PCX 
Portal Application contact the mailing list at sourceforge for the pcx_portal
project.


When going to add new States to the Application base your new state off the
StateTemplate.pm file in the Example directory.  Don't forget to add it to the
known states hash in the Example.pm file and to add it to the MANIFEST file.



LANGUAGE support:
Language files are now named by their language code, not their full name.
Ex.  English, code = en.  Thus the English language module would be
Portal::Example::Language::en

In the internal documentation for the language module, use the code wherever
it references to the file itself and the language name otherwise.  See en.pm
for an example.
