FileProg has support for plug-in's. Using the plug-in's each developer
can implement it's own specific library for FileProg. FileProg will
Display these plug-in's in the FileProg menu, under plug-in.

Note that plug-in's work on devices with PalmOS 4 and above.

If you have comments or request on the interface please contact me
at PalmFileProg@Yahoo.com.


Using the libraries
-------------------
Once started FileProg will scan the RAM for existing libraries, it will
make a list of these libraries (up to 8 plug-in's) and present them in a
plug-in's menu.

The user will select the files or databases that he wants to operate on.
Once selected, using the menu options he can operate on these files, selecting
one of the menu items from the plug-in menu.


Deleting a plug-in from memory
------------------------------
Since FileProg has a list of the available plug-in's in the RAM, you have
to disable the plug-in's before deleting them from the RAM. You can disable
the plug-in's from FileProg preferences menu. Once disabled, you can delete
these plug-in's from memory, by selecting them and then tapping the Delete
button.

When FileProg is deleted from the RAM, using the application manager, all
the plug-in's will be deleted as well.



Identifying FileProg plug-in's
------------------------------
The FileProg plug-in's creator ID should be 'AGil', same as FileProg. Using
this creator ID, FileProg identifies the existing plug-in's in the RAM. The
type of the library can be anything and can be used to identify the library
creator.


Plug-in interface
-----------------
The plug-in library interface can be found in the example project: FileLib.zip.
This is a MetroWrecks 7.0 project, based on the SampleLib example provided by
Palm. You can use this project as an example on how to write a plug-in for
FileProg, you can also look at Palm's SampleLib project.


For any questions or requests please contact: PalmFileProg@yahoo.com


