OVERVIEW
-------------------------------------------------------------------------------
This project contains a P4V applet that presents a list of pending
integrations for each branch spec owned by the current user.

The applet uses the P4JsApi framework introduced in the 2010.1 beta
release.

MANIFEST
-------------------------------------------------------------------------------
README.txt          This file
screen_shot.png     Screen shot of 'Pending Integrations' tab in P4V
protect.txt         Snippet of protections table, showing how to enable 
                    centralsettings
centralsettings.js  Example central settings file, showing how to enable
                    the 'Pending Integrations' tab
interchanges.html   The applet HTML file

INSTALLATION
-------------------------------------------------------------------------------
Refer to the P4JsApi guide 
(http://www.perforce.com/perforce/r10.1/manuals/p4jsapi/p4jsapi.pdf) for more details.

1. Customize the example interchanges.html file to taste, then check in.

2. Create and check in a central settings file.  Use the centralsettings.js
file in this project as a template.  Make sure the depot path for
interchanges.html specified in centralsettings.js matches the actual depot 
path.

3. Enable the centralsettings file for the appropriate users or groups.
For example, to enable it for a group called BranchCurators.G, 
add a protections entry like:
    list group BranchCurators.G centralsettings //depot/jsapi/centralsettings.js
This entry assumes that your central settings file lives at 
//depot/jsapi/centralsettings.js.

4. To use the applet in P4V, follow the instructions in the P4JsApi guide
for enabling applets in P4V.  Then, restart P4V and select 
'Pending Integrations' from the View menu.  The applet will appear as a tab
in P4V.

FUTURE ENHANCEMENTS
-------------------------------------------------------------------------------
- Show pending changelists when the 'interchanges' command becomes available.
- Use a cleaner way to specify CSS style for the table.
- Optionally provide hyperlinks to a P4Web instance.
- Show the complete branch view, perhaps in a collapsible section.
- Allow a more flexible way to choose which branch specs to use.