r20950 - htdocs/branches/beta - Add a new css class for prompt command and use it.

[Cristian Marchi]

Author: cmarchi
Date: 2011-07-28 16:33:57 -0400 (Thu, 28 Jul 2011)
New Revision: 20950
Trac: http://svn.gnucash.org/trac/changeset/20950

Modified:
   htdocs/branches/beta/docs.phtml
   htdocs/branches/beta/externals/gnucash.css
Log:
Add a new css class for prompt command and use it.

Modified: htdocs/branches/beta/docs.phtml
===================================================================
--- htdocs/branches/beta/docs.phtml	2011-07-26 17:40:35 UTC (rev 20949)
+++ htdocs/branches/beta/docs.phtml	2011-07-28 20:33:57 UTC (rev 20950)
@@ -216,11 +216,11 @@
 <h3><?php echo T_("Where to get the documentation source");?></h3>
 <p class="justify"><?php echo T_("You will need a recent copy of the documentation source. For this you can check out the documentation module from the <span class=\"gnucash\">Gnucash</span> svn. Reviewers could also start from the <a href='http://sourceforge.net/projects/gnucash/files/gnucash-docs/'>current docs tarball</a>.");?></p>
 <p class="justify"><?php echo T_("For those not familiar with svn, the <span class=\"gnucash\">Gnucash</span> wiki has a <a href='http://wiki.gnucash.org/wiki/Subversion'>description</a> tailored to the <span class=\"gnucash\">Gnucash</span> code. To get the documentation source instead of the program source, replace 'gnucash' with 'gnucash-docs' in the mentioned svn commands, like this:");?></p>
-<pre>svn checkout http://code.gnucash.org/repo/gnucash-docs/trunk gnucash-docs</pre>
+<pre class="command">svn checkout http://code.gnucash.org/repo/gnucash-docs/trunk gnucash-docs</pre>
 
 <h3><?php echo T_("Writers");?></h3>
 <p class="justify"><?php echo T_("Get a copy of the documentation source as described above and start making changes. When you are satisfied with your changes you can create a patch by running the following command in the base directory of the documentation (usually gnucash-docs, unless you renamed it):");?></p>
-<pre>svn diff > my-patch-name.patch</pre>
+<pre class="command">svn diff > my-patch-name.patch</pre>
 <p class="justify"><?php echo T_("Next attach your patch to a bug report against the documentation component for the <span class=\"gnucash\">Gnucash</span> project in <a href='http://bugzilla.gnome.org/'>Gnome's bugzilla database</a> and send an email to <a href='mailto:gnucash-devel at lists.gnucash.org'>gnucash-devel</a> mailing list to inform other developers on your work. See also <a href='http://wiki.gnucash.org/wiki/Bugzilla'>GnuCash' wiki page on bugzilla</a> for more details about patch submission.");?></p>
 <div class="dialog note">
 <p class="justify"><?php echo T_("<b>NOTE:</b> It used to be ok also to send your patch directly to the gnucash-devel list. This is discouraged now, as a patch is easily forgotten between the many list discussions. Attach patches to bugs in Bugzilla instead (either an existing bug or a new one). If you insist on sending a patch to gnucash-devel, it should be attached, not inlined.");?></p>

Modified: htdocs/branches/beta/externals/gnucash.css
===================================================================
--- htdocs/branches/beta/externals/gnucash.css	2011-07-26 17:40:35 UTC (rev 20949)
+++ htdocs/branches/beta/externals/gnucash.css	2011-07-28 20:33:57 UTC (rev 20950)
@@ -416,3 +416,10 @@
    padding-left:40px;
    background: url(download-32x32.png) left no-repeat;
 }
+
+.command {
+background: gainsboro;
+border-style:dashed;
+border-width:1px;
+padding:10px;
+}