Roundup Wiki

Don't even bother spamming this page, or any other in the wiki - the text will be removed within 12 hours

No, really. Spam text does not stay here, or on any page in this wiki. I get email. I remove spam. Just don't *bother*.

- I wouldn't have even *tried* to spam this without your multiple suggestions to the contrary. >=(

From wiki Tue Dec 20 21:58:06 +1100 2005 From: wiki Date: Tue, 20 Dec 2005 21:58:06 +1100 Subject: TestingFirefoxOneFive Message-ID: <20051220215806+1100@www.mechanicalcat.net>

Betcha this'll work too http://www.google.com

From wiki Sat Feb 3 20:25:27 +1100 2007 From: wiki Date: Sat, 03 Feb 2007 20:25:27 +1100 Subject: Make it work with roundup 1.x+ Message-ID: <20070203202527+1100@www.mechanicalcat.net>

With some small changes, this works with Roundup 1.x, too:

- the "issue" class is changed in schema.py rather than dbinit.py

- MergeAction class is put in an existing or separate Python file in the "extensions" subdirectory

Restart the Roundup server to recognise the schema change and the new extension.

- to put the form for the merge action in the ...issue.item.html... template, I did as follows:

- added a slot to the ... in page.html

  • <div id="searchbox">

    • <form method="GET" action="issue" metal:define-slot="search-form">

      • <!-- ... -->

      </form> <metal:slot define-slot="more-forms"/>

  • </div>

- filled this new slot in ...issue.item.html...

  • <tal:if condition="context/is_edit_ok">

    • <form metal:fill-slot="more-forms" tal:condition="not:context/merged"

      • class="additional" method="POST"

        name="mergeForm">

      • <input type="hidden" name="@action" value="merge"> <label for="merge_into" i18n:translate="">Merge into</label> <input type="text" id="merge_into" name="merge_into" size="5"> <span tal:replace="structure python:db.issue.classhelp('id,title', property='merge_into', inputtype='radio', form='mergeForm')" /> <input type="submit" value=" Merge " i18n:attributes="value">

      </form>

    </tal:if>

From wiki Sat Feb 3 20:31:04 +1100 2007 From: wiki Date: Sat, 03 Feb 2007 20:31:04 +1100 Subject: Make it work with roundup 1.x+ Message-ID: <20070203203104+1100@www.mechanicalcat.net>

With some small changes, this works with Roundup 1.x, too:

- the ...issue... class is changed in schema.py rather than dbinit.py

- the ...MergeAction... class is put in an existing or separate Python file in the ...extensions... subdirectory

Restart the Roundup server to recognise the schema change and the new extension.

- to put the form for the merge action in the ...issue.item.html... template, I did as follows:

- added a slot to the ...searchbox... div in page.html

  • <div id="searchbox">

    • <form method="GET" action="issue" metal:define-slot="search-form">

      • <!-- ... -->

      </form> <metal:slot define-slot="more-forms"/>

    </div>

- filled this new slot in ...issue.item.html...

  • <tal:if condition="context/is_edit_ok">

    • <form metal:fill-slot="more-forms" tal:condition="not:context/merged"

      • class="additional" method="POST"

        name="mergeForm">

      • <input type="hidden" name="@action" value="merge"> <label for="merge_into" i18n:translate="">Merge into</label> <input type="text" id="merge_into" name="merge_into" size="5"> <span tal:replace="structure python:db.issue.classhelp('id,title', property='merge_into', inputtype='radio', form='mergeForm')" /> <input type="submit" value=" Merge " i18n:attributes="value">

      </form>

    </tal:if>

From wiki Sat Feb 3 20:39:48 +1100 2007 From: wiki Date: Sat, 03 Feb 2007 20:39:48 +1100 Subject: One more try Message-ID: <20070203203948+1100@www.mechanicalcat.net>

With some small changes, this works with Roundup 1.x, too:

- the "issu" class is changed in schema.py rather than dbinit.py

- the "MergeAction" class is put in an existing or separate Python file in the "extensions" subdirectory

Restart the Roundup server to recognise the schema change and the new extension.

- to put the form for the merge action in the "issue.item.html" template, I did as follows:

- added a slot to the "searchbox" div in page.html

  • <div id="searchbox">

    • <form method="GET" action="issue" metal:define-slot="search-form">

      • <!-- ... -->

      </form> <metal:slot define-slot="more-forms"/>

    </div>

- filled this new slot in "issue.item.html"

  • <tal:if condition="context/is_edit_ok">

    • <form metal:fill-slot="more-forms" tal:condition="not:context/merged"

      • class="additional" method="POST"

        name="mergeForm">

      • <input type="hidden" name="@action" value="merge"> <label for="merge_into" i18n:translate="">Merge into</label> <input type="text" id="merge_into" name="merge_into" size="5"> <span tal:replace="structure python:db.issue.classhelp('id,title', property='merge_into', inputtype='radio', form='mergeForm')" /> <input type="submit" value=" Merge " i18n:attributes="value">

      </form>

    </tal:if>

Of course, this can be improved further; there is no GUI method so far to undo a merge. You can restore and unmerge issueXXXX using the "roundup-admin" script, using the following commands::

The file attachments and messages will stay double-linked, but this might be ok and can be changed TTW.

From wiki Thu Apr 26 18:32:56 +1000 2007 From: wiki Date: Thu, 26 Apr 2007 18:32:56 +1000 Subject: IndexBackLink Message-ID: <20070426183256+1000@www.mechanicalcat.net>

This looks very interesting and useful!

However, a more "pythonic" way of doing::

(creating a one-key dictionary on the fly and handing it over by reference) would be::

which should do exactly the same.

Only for logged-in users:

might be clever to have the links only created for those, e.g. using::

and::

or directly, since only one link per template is created,::

- Nikolausi

From wiki Thu Apr 26 18:42:33 +1000 2007 From: wiki Date: Thu, 26 Apr 2007 18:42:33 +1000 Subject: Only for logged-in users Message-ID: <20070426184233+1000@www.mechanicalcat.net>

Since Roundup's session mechanism works for logged-in users only, it would be clever to have the links only created for those (avoiding errors when anonymous users try to use them), e.g. using (untested)::

If performance is an issue, and since tal:define is always evaluated first (but the condition in this case doesn't depend on it), the links an be put in a surrounding (tal) element, e.g.:

- Nikolausi

From wiki Thu Apr 26 18:43:49 +1000 2007 From: wiki Date: Thu, 26 Apr 2007 18:43:49 +1000 Subject: Only for logged-in users Message-ID: <20070426184349+1000@www.mechanicalcat.net>

Since Roundup's session mechanism works for logged-in users only, it would be clever to have the links only created for those (avoiding errors when anonymous users try to use them), e.g. using (untested)::

If performance is an issue, and since tal:define is always evaluated first (but the condition in this case doesn't depend on it), the links an be put in a surrounding (tal) element, e.g.::

- Nikolausi