Perforce Software
P4Web Release Notes
2000.2 - January 4, 2001
Documentation
·
Requirements
·
Latest Changes
Unsupported Operations
·
Limitations and Known Problems
·
Your Feedback
Documention
P4Web is documented in
"How to Use P4Web"
and in embedded help files.
Requirements
-
P4Web works with a Perforce Depot Server at Release 99.2 or higher.
-
P4Web works with any web browser. Some older browsers
do not provide the authentication support needed by P4Web;
those browsers can be used only when P4Web is running
as a read-only "Viewer".
-
On Windows and Unix, you must have p4
(the Perforce command line client program) installed
in order to interactively resolve files from within P4Web.
-
On Macintosh, Unix, and Windows, P4Web can launch an editor.
Which editor it launches is determined by the
startup environment of the p4web executable,
as described in
"How to Use P4Web."
You must set P4EDITOR before running p4web
to control which editor is launched.
Latest Changes
- 2000.2/19899
- 4709 fixed: double-quotes in filenames were not handled correctly
- 4689 fixed: erroneously submits files opened by other users sharing the same client
- 4719 fixed: "+" in path incorrectly decoded into spaces
- 2000.2/19495
- "Open for add" can now scan workspace path for new files to add
- "Interactive resolve" replaces "safe automatic resolve" as the default
- The File Browser now offers a link to the workspace copy of the current file
- Launching the editor no longer causes the browser to wait or time out
- On Unix, launching an editor or interactive resolve is allowed even if the
browser and the P4Web Helper are on different machines
- Added shortcut for "launch editor"
- Client spec form now shows abbreviations as well as verbose option descriptions
- 4693 fixed: "&" in path causes bad "return to browser" links
- 4696 fixed: file text not displayed correctly on Mac
- 4626, 4659 fixed: resolve operates on invalid/missing filepattern
- 4384 fixed: interactive resolve launched even when there are no files to resolve
- 4586 fixed: P4Web Viewer displays irrelevant client-related info
- 4596 fixed: "workspace diffs" gives wrong output when file is not at head revision
- 2000.2beta/18974
- 4424 fixed: now allows reconnecting after stopping & restarting browser
- 2000.1beta/18743
- Macintosh startup configuration dialog now available
- Support for changing filetypes added
- Support for "Show opened files -- all clients" added
- 4454 fixed: case mismatch in username makes authentication fail
- 4446 fixed: trailing "?=" in file content URLs prevents some browsers from recognizing file suffix
- 4326 fixed: can't see filetype of opened files
- 4507 fixed: can't diff opened binary files
- 4267 fixed: p4web doesn't check for port in use before starting up
- 2000.1beta/18548
- Label spec and branch spec list pages available
- "Recent activity" display now optional, not shown by default
- 4443 fixed: wrong "Go To" menu items shown in Viewer mode
- 2000.1beta/18366
- Support for moving opened files between pending changelists added
- 3532 fixed: no way to delete an empty pending changelist
- 4426 fixed: maxresults error prevents display of links to subdirectories
- 2000.1beta/18267
- 4376 fixed: Changing settings to bad port prevents access to settings page.
- 2000.1beta/18170
- Startup command flags & arguments have changed --
run p4web -h for info.
- Support for "integrate" added
- Interactive "resolve" available on Windows and Unix
- Hide/show files now available
- 4337 fixed: "return to browser" button now returns to file browser page too
- 4296 fixed: showing command results in file browser page invited futile refresh/reload
- 4291 fixed: attempt to show filelog on path (via URL) gave mangled results
- 4261 fixed: no "all files" option in "revert" form
- 4222 fixed: "open for delete" showed empty "options" heading
- 4219 fixed: "show" menu operations caused inconsistent page titles
- 4212 fixed: shortcuts worked on "matching files" not on current path
- 4167 fixed: on Mac, client root field was displayed incorrectly
- 4132 fixed: invalid URL crashed p4web
- 4100 fixed: attempted to launch editor even if browser and workspace on different machines
- 4086 fixed: p4web crashed trying to launch editor on non-existent file
- 4085 fixed: p4web crashed when certain wildcard mappings occured in client views
- 4049 fixed: some help file links not working in IE5
- 4032 fixed: path browser margins not lining up
- 3993 fixed: p4web doesn't pick a default port address; requires user to supply one
- 3937 fixed: deleted files not on workspace show up with "synced" icon
- 3654 fixed: on Mac, client root field was cleared every time client edit page was shown
- 3568 fixed: password help file now displayed at authentication error
- 3415 fixed: on Mac, now outputs a message if p4web.config file can't be found
- 3247 fixed: drop-down menus weren't pre-selected
- 2000.1beta/17344
- Introductory Help files added
- Path browser shows file revision and type info
- Interactive resolve available on Mac
- Editor launch support added
- Configuration Settings page added
- Support for MIME display of file content
- Support for extended filelog (filelog -i)
- 3843 fixed: authentication problems on Unix
- 2000.1beta/16431
- The File Browser offers shortcut buttons for common file operations.
- 3421, 3491 fixed: Macintosh memory allocation problems.
- 99.2beta/15399
- P4Web's "Client mode/depot mode" concept has been replaced with
client/depot view preferences available in the Path Browser's
"Show" menu.
Now you can view mapped files you're not synced to yet.
(Same as what you see in P4Win.)
- 3494 fixed: Offline remote depots prevent viewing top level path.
- 99.2beta/15106
- 3426 fixed: "Error: //* - must refer to client 'clientname'"
- 3399 fixed: No "resolve" page help
- 3252 new: Support for browse-only P4Web.
- 3011 fixed: P4Web stops running (or won't start up) if it can't
connect to a Perforce server
- 3438 fixed: No "unlock" help
- 3378 fixed: Problems with diff output page
- 3433 fixed: Mangled $Id examples in help pages
Unsupported Operations
The following operations will be supported in a future release:
- Doing single-file or single-directory operations from Path Browser page
- Diffing non-consecutive file revisions
- Working with branch specs (other than using them with 'integrate'),
labels, and jobs
- Changing user name and/or password from a P4Web page (2957)
- Showing unintegrated file state in Path Browser and File Browser
- Improved usability on browsers that support Javascript
Limitations and Known Problems
-
Neither P4Web nor Perforce store MIME type mappings.
P4Web commands that show file text use "text/plain" to qualify file
content sent to the browser. P4Web commands for file browsing send
unmodified, unqualified file content to the browser. This lets
the browser choose how to display content according to the file suffix,
the same way it would if a file URL was used. In some browsers, and
with some file types, this works very well. In others, it does not.
-
Using Internet Explorer on Macintosh Classic platforms (MacOS 9.x and
below) causes P4Web performance problems. P4Web users on Mac Classic
should try Netscape instead.
- On Mac and Windows, the "launch" commands are only available when
your browser and your P4Web Helper are running on the same host machine.
- Neither the "Revert" button nor the "Revert if unchanged" operation
work on files opened for branch or add. Revert those files with "Revert
even though changed." (3400)
Please Send Us Your Feedback
Your feedback will help us improve P4Web.
Please email your comments and bug reports to
[email protected].
Be prepared to tell us:
- The version ID of the P4Web and the browser you were testing with.
(Cut and paste this information from any P4Web page.)
- For bug reports, the URL of the P4Web page in question.
Thank you!
Copyright 2000 Perforce Software
$Id: //depot/r00.2/p4-doc/user/p4webnotes.html#6 $