<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Perforce Public Depot: API Project</title>
<!-- no htdig-keywords tag in this file -->
<!-- no keywords tag in this file -->
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="../../css/pure.css" type="text/css">
<link rel="stylesheet" href="../../css/depot.css" type="text/css">
</head>
<body>
<!-- div for entire page -->
<div id="outer">
<div id="page-top"><!-- frames the logo and search -->
<!-- logo -->
<div id="logo">
<a href="../../index.html"><img src="../../images/site_logo.gif" alt="Perforce Public Depot" width="219" height="50"></a>
</div>
<div id="search"><!-- search section -->
<form method="get" action="http://www.google.com/search">
<div><!-- needed so invisible field will validate -->
<input type="hidden" name="sitesearch" value="public.perforce.com">
</div><!-- silly invisible field div -->
<ul class="search-box">
<li class="left"><input type="text" size="40" name="q" value="" class="search-form"></li>
<li class="middle"><input type="submit" value="Search" class="search-button"></li>
<li class="right" style="color: black;">Powered by Google</li>
</ul>
</form><!-- top navbar search form -->
</div><!-- end search section -->
</div> <!-- end div id page-top -->
<!-- start site content -->
<div id="main-body">
<!-- navbars -->
<div id="navbar-outer">
<ul class="navbar">
<li class="nav-top"><a href="index.html" title="Home">Home</a></li>
<li><a href="sitemap.html" title="Project Tree">Project Tree</a></li>
<!-- li><a href="search.html" title="Search">Search</a></li -->
<li><a href="browse.html" title="How to Browse" >Browse</a></li>
<li><a href="contribute.html" title="How to Contribute">Contribute</a></li>
<!-- li><a href="review.html" title="Change Review Email">Change Review Email</a></li -->
</ul>
</div>
<!-- end id.navbars -->
<div id="content-outer">
<div id="content">
<!-- Content starts here -->
<h1>The Perforce API Project</h1>
<!-- ABOUT THIS PROJECT -->
<a name="about"></a>
<h3>About This Project</h3>
<dl class="project">
<dt>Content</dt>
<dd>
<p>The Perforce API Project collects user-contributed interfaces to allow programmatic access to Perforce.
Most of these do so by providing a layer between the
<a href="http://www.perforce.com/perforce/doc.021/user/p4api.txt"> Perforce API</a> and a particular language;
some use the Perforce command line client.
</p>
<p>(Also, see <a href="../webkeeper/index.html">WebKeeper</a> for another Perforce API implementation example.)
</p>
</dd>
<dt>Contributing</dt>
<dd>
<p>Please contact <a href="mailto:opensource@perforce.com">Perforce</a> if you have any submitted contributions
you'd like integrated into the public branch of the Perforce API Project.
</p>
</dd>
</dl>
<!-- QUICKLINKS -->
<div class="quickLinks">
<ul>
<li><a href="#api">API<br>Interfaces</a></li>
<li><a href="#toolkits">Interface<br> Toolkits</a></li>
</ul>
</div>
<!-- API Interfaces -->
<a name="api"></a>
<h3>API Interfaces</h3>
<dl class="Interfaces">
<dt><a href="http://public.perforce.com:8080/@ra=s@/public/perforce/api/python/P4Client/">
//public/perforce/api/python/P4Client/</a>
</dt>
<dd>
<p>
<strong>P4Client, a Python interface</strong> to the Perforce ClientApi class. A Python review daemon script that
uses it is provided as an example. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@//mike_meyer?ac=17">Mike Meyer</a>.
</p>
</dd>
<dt><a href="http://public.perforce.com/guest/tony_smith/perforce/API/Perl/index.html">
//guest/tony_smith/perforce/API/Perl/</a>
</dt>
<dd>
<p>
A <strong>Perl interface</strong> to the Perforce API. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@/tony_smith?ac=17">Tony Smith</a>.
</p>
</dd>
<dt><a href="http://public.perforce.com/guest/tony_smith/perforce/API/Ruby/index.html">
//guest/tony_smith/perforce/API/Ruby/</a>
</dt>
<dd>
<p>
A <strong>Ruby interface</strong> to the Perforce API. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@//tony_smith?ac=17">Tony Smith</a>.
</p>
</dd>
<dt><a href="http://public.perforce.com:8080/@md=d&cd=//guest/michael_bishop/&ra=s&c=XEd@//guest/michael_bishop/P4APIForJava/?ac=83">//guest/michael_bishop/P4APIForJava/</a>
</dt>
<dd>
<p>
A <strong>Java interface</strong> to the Perforce API. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@//michael_bishop?ac=17">Michael Bishop</a>.
</p>
</dd>
</dl>
<div class="hr-dotted"></div>
<!-- Interface Toolkits -->
<a name="toolkits"></a>
<h3>Interface Toolkits</h3>
<dl class="IntfcToolkits">
<dt>
These tools provide higher level capabilities (as opposed to the basic API/language bindings in the
<a href="#api">API Interfaces</a> section above).
</dt>
<dt><a href="http://public.perforce.com:/public/perforce/api/java/p4package/index.html">
//public/perforce/api/java/p4package/</a>
</dt>
<dd>
<p>
<strong>P4Package, a high-level Java API for Perforce.</strong> These classes provide a way to encapsulate
source control objects like branches, files, users, etc. This implementation is based on the
execution of the Perforce command line client, rather than the Perforce API proper. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@//david_markley?ac=17">David Markley</a>.
</p>
</dd>
<dt><a href="http://public.perforce.com:/public/perforce/api/java/p4jsp/index.html">
//public/perforce/api/java/p4jsp/</a>
</dt>
<dd>
<p>
This application allows multiple users to access the perforce using the same web application
using their own credentials. This makes it easy to add pages that implement other perforce
functions and have them execute using appropriate authorization. An example would be a page that
handled integrations from one branch to another at the click of one button or link. Contributed by
<a href="http://public.perforce.com:8080/@md=d&ra=s@//david_markley?ac=17">David Markley</a>.
</p>
</dd>
</dl>
<div class="hr-dotted"></div>
<p class="stored-file">You're browsing a file stored as <code>$Id: //public/perforce/api/index.html#13 $</code>
</p>
<!-- Content ends here -->
</div><!-- id content -->
</div><!-- id content-outer -->
</div><!-- id main-body -->
<!-- Copyright and bottom bar -->
<div id="copyright">
Copyright &#169; 1998, 1999, 2002 Perforce
</div>
</div> <!-- id outer -->
</body>
</html>
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #18 | 8157 | michael | Archiving legacy java api projects which predate the supported P4Java api. | ||
| #17 | 6283 | Sam Stafford | Update redirects to use new short URLs. | ||
| #16 | 6276 | Sam Stafford | Change old pages to http://public.perforce.com/wiki/ redirects. | ||
| #15 | 6074 | michael | Fix a bunch of relative navbar links. | ||
| #14 | 6026 | rlo |
Public depot fixes: * Titles formatted similarly * Navbar changed and shortened * Change review taken out of navbar * Links fixed |
||
| #13 | 6025 | rlo |
Public Depot Redesign goes live * Skin matches KB and latest WWW skin * Rudimentary search mechanism based on google * did this already, but made some big mistakes and it was easier to obliterate and start over * about the above: yikes! |
||
| #12 | 1984 | rmg |
Break the listing up into "API Interfaces" (for low level API/language bindings) and "Interface Toolkits" (for higher-level stuff) Add p4jsp to the latter category. |
||
| #11 | 1701 | rmg | Don't advertise Michael's Java API for now, pending some docs. | ||
| #10 | 1698 | rmg |
Add links to the Perl, Ruby, and Java (true p4api) interfaces. For the moment, these go to //guest/tony_smith/... and //guest/michael_bishop/..., which is a departure, but I don't see any harm in it, nor any great advantage or urgency to integrating them into //public. |
||
| #9 | 1697 | rmg | Note that some implementations may not use p4api | ||
| #8 | 1155 | rmg |
The change to utils/index.html was required to get the page to render better with Netscape 6.2. (Without the closing </B> tags, the whole page from the Depot Browsers section on down rendered bold...!) I made the same logical change to the other four for consistency, though they didn't seem to suffer from the same problem. p4dti/index.html still doesn't render right under Netscape 6.2, but it's from a different patterns and I couldn't see a quick clean fix... so I didn't mess with it for now. |
||
| #7 | 1046 | rmg | Add "P4Package" (Java Perforce API bindings) from David Markley to the //public roadmap. | ||
| #6 | 968 | rmg |
Change mail addresses from "info@perforce.com" to "opensource@perforce.com" (now that the "opensource" address exists). |
||
| #5 | 780 | rmg |
Take 2 for the p4db -> p4web conversion. (change 788 redux) |
||
| #4 | 779 | rmg | Back out change 778. | ||
| #3 | 778 | rmg | Covert all p4db links into p4web links. | ||
| #2 | 177 | Laura Wingerd | Fix link on API index page. | ||
| #1 | 156 | Laura Wingerd | Publish Mike Meyer's Python interface to Perforce API. | ||
| //guest/laura_wingerd/perforce/api/index.html | |||||
| #1 | 155 | Laura Wingerd | Web page for contributed API interfaces. | ||