[Checkins] SVN: zope.kgs/trunk/src/zope/kgs/ more work on master template.
Paul Carduner
paulcarduner at gmail.com
Tue Jan 27 03:12:25 EST 2009
Log message for revision 95080:
more work on master template.
Changed:
U zope.kgs/trunk/src/zope/kgs/site.py
U zope.kgs/trunk/src/zope/kgs/templates/index.html
U zope.kgs/trunk/src/zope/kgs/templates/master.pt
-=-
Modified: zope.kgs/trunk/src/zope/kgs/site.py
===================================================================
--- zope.kgs/trunk/src/zope/kgs/site.py 2009-01-27 07:55:21 UTC (rev 95079)
+++ zope.kgs/trunk/src/zope/kgs/site.py 2009-01-27 08:12:25 UTC (rev 95080)
@@ -121,7 +121,6 @@
# Generate Web Site
logger.info("Generating Web Site")
- #intro.main(['-d',versionDir])
template.generateSite(templateDir, siteDir, None)
logger.info("finished generating site.")
Modified: zope.kgs/trunk/src/zope/kgs/templates/index.html
===================================================================
--- zope.kgs/trunk/src/zope/kgs/templates/index.html 2009-01-27 07:55:21 UTC (rev 95079)
+++ zope.kgs/trunk/src/zope/kgs/templates/index.html 2009-01-27 08:12:25 UTC (rev 95080)
@@ -4,6 +4,135 @@
<title metal:fill-slot="page-title">Introduction to the KGS</title>
</head>
<body>
- <div tal:content="structure templates/menu.pt" />
+ <div metal:fill-slot="header">Introduction to the KGS</div>
+ <ul class="level-one" metal:fill-slot="left-nav">
+ <!--li tal:repeat="version self/versions">
+ <a href="#">Version <span tal:replace="version/name">1</span></a>
+ <ul class="level-two" style="display: none;">
+ <li tal:repeat="feature version/features">
+ <a href="#"
+ tal:attributes="href feature/url"
+ tal:content="feature/title">Feature 1</a>
+ </li>
+ <li tal:replace="nothing">
+ <a href="#">Feature 2</a>
+ </li>
+ <li tal:replace="nothing">
+ <a href="#">Feature 3</a>
+ </li>
+ <li tal:replace="nothing">
+ <a href="#">Feature 4</a>
+ </li>
+ </ul>
+
+</li-->
+
+
+ <li>
+ <a href="#">Version 2</a>
+ <ul class="level-two" style="display: none;">
+ <li>
+ <a href="#">Feature 1</a>
+ </li>
+ <li>
+ <a href="#">Feature 2</a>
+ </li>
+ <li>
+ <a href="#">Feature 3</a>
+ </li>
+ <li>
+ <a href="#">Feature 4</a>
+ </li>
+ </ul>
+
+ </li>
+ </ul>
+
+ <div metal:fill-slot="content">
+ <h1 id="pageheading">Known Good Sets</h1>
+
+ <h2>Usage</h2>
+
+ <p>
+ This KGS was designed to work with many of the tools developed to
+ manage and install Python pacakges. The following sub-sections will
+ explain its use in more detail.
+ </p>
+
+ <h3>The Index</h3>
+
+ <p>
+ You can use the index directly. It then behaves exactly like
+ <a href="http://pypi.python.org/simple">http://pypi.python.org/simple</a>,
+ except that only the good versions of the controlled packages are
+ available. The advantage of using the KGS as an index is that you get
+ bug fixes automatically.
+ </p>
+
+ <ul>
+ <li>
+ <div>In <strong>Buildout</strong> you can set this index in your <code>buildout.cfg</code> file:</div>
+ <pre>
+[buildout]
+index = http://download.project.org/kgs
+...</pre>
+ </li>
+ <li>
+ <div>With <strong>SetupTools</strong> you can specify the index as a command line option to the <code>easy_install</code> command:</div>
+ <pre>$ easy_install -i http://download.project.org/kgs mypackage</pre>
+ </li>
+ </ul>
+
+ <h3>Nailed or Pinned Versions</h3>
+
+ <p>
+ When deploying an application, it is often important to nail or pin down
+ the versions of all used packages, so that it can be guaranteed that the
+ setup is identical all the time.
+ </p>
+
+ <ul>
+ <li>
+ <div>In <strong>Buildout</strong>, the versions can be specified in the <code>buildout.cfg</code> file like this by either copying the contents of <code>versions-*.cfg</code> or referencing it with the <code>extends</code> option:</div>
+ <pre>
+[buildout]
+versions = versions
+...
+[version]
+zope.interface = 3.4.0
+<copy the contents of versions-*.cfg here></pre>
+ or
+ <pre>
+[buildout]
+extends = http://download.project.org/kgs/versions-1.0.0.cfg</pre>
+ </li>
+ <li>
+ <div><strong>SetupTools</strong> itself cannot use the <code>version.cfg</code>
+ file.</div>
+ </li>
+ </ul>
+
+ <h3>Find Links</h3>
+
+ <p>
+ The way of providing the installation tools with additional locations to
+ look for packages is via find links. Those URLs are expected to be an
+ HTML page with links to files or files directly.
+ </p>
+
+ <ul>
+ <li>
+ <div>Buildout, <code>buildout.cfg</code>:</div>
+ <pre>
+[buildout]
+find-links = http://download.project.org/kgs/links.html
+...</pre>
+ </li>
+ <li>
+ <div>Setup Tools, <code>easy_install</code></div>
+ <pre>$ easy_install -f http://download.project.org/kgs/links.html mypackage</pre>
+ </li>
+ </ul>
+ </div>
</body>
</html>
Modified: zope.kgs/trunk/src/zope/kgs/templates/master.pt
===================================================================
--- zope.kgs/trunk/src/zope/kgs/templates/master.pt 2009-01-27 07:55:21 UTC (rev 95079)
+++ zope.kgs/trunk/src/zope/kgs/templates/master.pt 2009-01-27 08:12:25 UTC (rev 95080)
@@ -26,146 +26,22 @@
<body>
<h1 id="header">Introduction to the KGS</h1>
- <div id="left-hand-navigation" metal:define-slot="left-nav">
+ <div id="left-hand-navigation">
<!-- Main Menu -->
<div id="menu">
- <ul class="level-one">
+ <div class="level-one" metal:define-slot="left-nav">
- <li tal:repeat="version self/versions">
- <a href="#">Version <span tal:replace="version/name">1</span></a>
- <ul class="level-two" style="display: none;">
- <li tal:repeat="feature version/features">
- <a href="#"
- tal:attributes="href feature/url"
- tal:content="feature/title">Feature 1</a>
- </li>
- <li tal:replace="nothing">
- <a href="#">Feature 2</a>
- </li>
- <li tal:replace="nothing">
- <a href="#">Feature 3</a>
- </li>
- <li tal:replace="nothing">
- <a href="#">Feature 4</a>
- </li>
- </ul>
- </li>
-
-
- <li tal:replace="nothing">
- <a href="#">Version 2</a>
- <ul class="level-two" style="display: none;">
- <li>
- <a href="#">Feature 1</a>
- </li>
- <li>
- <a href="#">Feature 2</a>
- </li>
- <li>
- <a href="#">Feature 3</a>
- </li>
- <li>
- <a href="#">Feature 4</a>
- </li>
- </ul>
-
- </li>
-
- </ul>
+ </div>
</div>
</div>
<div id="content-body">
<div id="body-main">
- <div id="content">
-
- <h1 id="pageheading">Known Good Sets</h1>
-
- <h2>Usage</h2>
-
- <p>
- This KGS was designed to work with many of the tools developed to
- manage and install Python pacakges. The following sub-sections will
- explain its use in more detail.
- </p>
-
- <h3>The Index</h3>
-
- <p>
- You can use the index directly. It then behaves exactly like
- <a href="http://pypi.python.org/simple">http://pypi.python.org/simple</a>,
- except that only the good versions of the controlled packages are
- available. The advantage of using the KGS as an index is that you get
- bug fixes automatically.
- </p>
-
- <ul>
- <li>
- <div>In <strong>Buildout</strong> you can set this index in your <code>buildout.cfg</code> file:</div>
- <pre>
-[buildout]
-index = http://download.project.org/kgs
-...</pre>
- </li>
- <li>
- <div>With <strong>SetupTools</strong> you can specify the index as a command line option to the <code>easy_install</code> command:</div>
- <pre>$ easy_install -i http://download.project.org/kgs mypackage</pre>
- </li>
- </ul>
-
- <h3>Nailed or Pinned Versions</h3>
-
- <p>
- When deploying an application, it is often important to nail or pin down
- the versions of all used packages, so that it can be guaranteed that the
- setup is identical all the time.
- </p>
-
- <ul>
- <li>
- <div>In <strong>Buildout</strong>, the versions can be specified in the <code>buildout.cfg</code> file like this by either copying the contents of <code>versions-*.cfg</code> or referencing it with the <code>extends</code> option:</div>
- <pre>
-[buildout]
-versions = versions
-...
-[version]
-zope.interface = 3.4.0
-<copy the contents of versions-*.cfg here></pre>
- or
- <pre>
-[buildout]
-extends = http://download.project.org/kgs/versions-1.0.0.cfg</pre>
- </li>
- <li>
- <div><strong>SetupTools</strong> itself cannot use the <code>version.cfg</code>
- file.</div>
- </li>
- </ul>
-
- <h3>Find Links</h3>
-
- <p>
- The way of providing the installation tools with additional locations to
- look for packages is via find links. Those URLs are expected to be an
- HTML page with links to files or files directly.
- </p>
-
- <ul>
- <li>
- <div>Buildout, <code>buildout.cfg</code>:</div>
- <pre>
-[buildout]
-find-links = http://download.project.org/kgs/links.html
-...</pre>
- </li>
- <li>
- <div>Setup Tools, <code>easy_install</code></div>
- <pre>$ easy_install -f http://download.project.org/kgs/links.html mypackage</pre>
- </li>
- </ul>
+ <div id="content" metal:define-slot="content">
+ This is where the content goes.
</div>
</div>
More information about the Checkins
mailing list