Mercurial Repository: p/roundup/code: doc/customizing.txt comparison

comparison doc/customizing.txt @ 3818:e5043875a03d

Improved due_date and timelog customisation docs [SF#1625124]

author	Richard Jones <richard@users.sourceforge.net>
date	Thu, 15 Feb 2007 03:58:35 +0000
parents	aef19fff38dd
children	a48c514c465f

comparison

equal deleted inserted replaced

-:ce2c88d83eb6
+:e5043875a03d
 ===================
 Customising Roundup
 ===================
-:Version: $Revision: 1.216 $
+:Version: $Revision: 1.217 $
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
 .. contents::
 You add new fields by editing the ``schema.py`` file in you tracker's home.
 Schema changes are automatically applied to the database on the next
 tracker access (note that roundup-server would need to be restarted as it
 caches the schema).
-1. modify the ``schema.py``::
+1. Modify the ``schema.py``::
 issue = IssueClass(db, "issue",
 assignedto=Link("user"), topic=Multilink("keyword"),
 priority=Link("priority"), status=Link("status"),
 due_date=Date())
-2. add an edit field to the ``issue.item.html`` template::
+2. Add an edit field to the ``issue.item.html`` template::
 <tr>
 <th>Due Date</th>
 <td tal:content="structure context/due_date/field" />
 </tr>
-3. add the property to the ``issue.index.html`` page::
+If you want to show only the date part of due_date then do this instead::
+<tr>
+<th>Due Date</th>
+<td tal:content="structure python:context.due_date.field(format='%Y-%m-%d')" />
+</tr>
+3. Add the property to the ``issue.index.html`` page::
 (in the heading row)
 <th tal:condition="request/show/due_date">Due Date</th>
 (in the data row)
-<td tal:condition="request/show/due_date" tal:content="i/due_date" />
+<td tal:condition="request/show/due_date"
+tal:content="i/due_date" />
-4. add the property to the ``issue.search.html`` page::
+If you want format control of the display of the due date you can
+enter the following in the data row to show only the actual due date::
+<td tal:condition="request/show/due_date"
+tal:content="python:i.due_date.pretty('%Y-%m-%d')">&nbsp;</td>
+4. Add the property to the ``issue.search.html`` page::
 <tr tal:define="name string:due_date">
 <th i18n:translate="">Due Date:</th>
 <td metal:use-macro="search_input"></td>
 <td metal:use-macro="column_input"></td>
 <td metal:use-macro="sort_input"></td>
 <td metal:use-macro="group_input"></td>
 </tr>
-5. if you wish for the due date to appear in the standard views listed
+5. If you wish for the due date to appear in the standard views listed
 in the sidebar of the web interface then you'll need to add "due_date"
-to the columns and columns_showall lists in your ``page.html``.
+to the columns and columns_showall lists in your ``page.html``::
+columns string:id,activity,due_date,title,creator,status;
+columns_showall string:id,activity,due_date,title,creator,assignedto,status;
 Adding a new constrained field to the classic schema
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 This example shows how to add a new constrained property (i.e. a
 field to capture a new timelog item's period::
 <tr>
 <th>Time Log</th>
 <td colspan=3><input type="text" name="timelog-1@period" />
-<br />(enter as '3y 1m 4d 2:40:02' or parts thereof)
+(enter as '3y 1m 4d 2:40:02' or parts thereof)
 </td>
 </tr>
 and another hidden field that links that new timelog item (new
 because it's marked as having id "-1") to the issue item. It looks
 <input type="hidden" name="@link@times" value="timelog-1" />
 On submission, the "-1" timelog item will be created and assigned a
 real item id. The "times" property of the issue will have the new id
 added to it.
+The full entry will now look like this::
+<tr>
+<th>Time Log</th>
+<td colspan=3><input type="text" name="timelog-1@period" />
+(enter as '3y 1m 4d 2:40:02' or parts thereof)
+<input type="hidden" name="@link@times" value="timelog-1" />
+</td>
+</tr>
 4. We want to display a total of the timelog times that have been
 accumulated for an issue. To do this, we'll need to actually write
 some Python code, since it's beyond the scope of PageTemplates to
 perform such calculations. We do this by adding a module ``timespent.py``
 use of the ``totalTimeSpent`` method which will total up the times
 for the issue and return a new Interval. That will be automatically
 displayed in the template as text like "+ 1y 2:40" (1 year, 2 hours
 and 40 minutes).
-8. If you're using a persistent web server - ``roundup-server`` or
+6. If you're using a persistent web server - ``roundup-server`` or
 ``mod_python`` for example - then you'll need to restart that to pick up
 the code changes. When that's done, you'll be able to use the new
 time logging interface.
 An extension of this modification attaches the timelog entries to any
 change message entered at the time of the timelog entry:
-1. Add a link to the timelog to the msg class:
+A. Add a link to the timelog to the msg class in ``schema.py``:
 msg = FileClass(db, "msg",
 author=Link("user", do_journal='no'),
 recipients=Multilink("user", do_journal='no'),
 date=Date(),
 summary=String(),
 files=Multilink("file"),
 messageid=String(),
-inreplyto=String()
+inreplyto=String(),
 times=Multilink("timelog"))
-2. Add a new hidden field that links that new timelog item (new
+B. Add a new hidden field that links that new timelog item (new
 because it's marked as having id "-1") to the new message.
-It looks like this::
+The link is placed in ``issue.item.html`` in the same section that
+handles the timelog entry.
-<input type="hidden" name="msg-1@link@times" value="timelog-1" />
+It looks like this after this addition::
+<tr>
+<th>Time Log</th>
+<td colspan=3><input type="text" name="timelog-1@period" />
+(enter as '3y 1m 4d 2:40:02' or parts thereof)
+<input type="hidden" name="@link@times" value="timelog-1" />
+<input type="hidden" name="msg-1@link@times" value="timelog-1" />
+</td>
+</tr>
 The "times" property of the message will have the new id added to it.
-3. Add the timelog listing from step 5. to the ``msg.item.html`` template
+C. Add the timelog listing from step 5. to the ``msg.item.html`` template
-so that the timelog entry appears on the message view page.
+so that the timelog entry appears on the message view page. Note that
+the call to totalTimeSpent is not used here since there will only be one
+single timelog entry for each message.
+I placed it after the Date entry like this::
+<tr>
+<th i18n:translate="">Date:</th>
+<td tal:content="context/date"></td>
+</tr>
+</table>
+<table class="otherinfo" tal:condition="context/times">
+<tr><th colspan="3" class="header">Time Log</th></tr>
+<tr><th>Date</th><th>Period</th><th>Logged By</th></tr>
+<tr tal:repeat="time context/times">
+<td tal:content="time/creation"></td>
+<td tal:content="time/period"></td>
+<td tal:content="time/creator"></td>
+</tr>
+</table>
+<table class="messages">
 Tracking different types of issues
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Mercurial > p > roundup > code

comparison doc/customizing.txt @ 3818:e5043875a03d