frames.html #1

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
	<title>Documentation by YARD 0.8.7.6</title>
</head>
<script type="text/javascript" charset="utf-8">
window.onload = function() {
  var match = unescape(window.location.hash).match(/^#!(.+)/);
  var name = match ? match[1] : 'index.html';
  name = name.replace(/^(\w+):\/\//, '').replace(/^\/\//, '');
  document.writeln('<frameset cols="20%,*">' +
    '<frame name="list" src="class_list.html" />' +
    '<frame name="main" src="' + escape(name) + '" />' +
    '</frameset>');
}
</script>
<noscript>
  <frameset cols="20%,*">
    <frame name="list" src="class_list.html" />
    <frame name="main" src="index.html" />
  </frameset>
</noscript>
</html>

#	Change	User	Description
#1	15688	Doug Scheirer	Populate -o //guest/perforce_software/helix-web-services/... //guest/doug_scheirer/helix-web-services/....
//guest/perforce_software/helix-web-services/main/build/doc/helix_web_services/frames.html
#1	15032	tjuricek	Starting config and doc revisions. System is now broken while revisions underway. Configuration of the p4d connection is now done via a single HWSSettings middleware object injected into the Rack env. The HWSP4Cleanup middleware now cleans up any p4 injected into the Rack env. The Auth::App class now mostly just contains one method to generate a p4 ticket. /auth/v1/login. Added yard documentation for the main project. Yard docs have been reconfigured to dump into build/ directories. This should probably be done with each release. Hm... The top level rake file contains a task, 'all:doc', to update our documentation. This should probably be run for each checkin. Hm... Specs are now using Rack::Test on top of a 'live' p4d. I'd suggest you still use the p4util mechanism, which now dumps to a /tmp folder, so we can safely add P4IGNORE rules back into your local .p4config file. Old 'perforce' application now called 'helix_versioning_engine'. Removing cache data. Helix Sync may be slow. It may also get axed. We'll see.