========================= What's New in Roundup 0.7 ========================= For those completely new to Roundup, you might want to look over the very terse features__ page. __ features.html .. contents:: Instant-Gratification script even more gratifying ================================================= The immensely popular ``python demo.py`` instant-gratification script has been extended to allow you to choose the backend to use with the demo. To select the "sqlite" backend (assuming it is available) you use:: python demo.py sqlite nuke This will nuke any existing demo and reinitialise it with the sqlite backend. Remember folks, if you want to restart the demo at a later point, you just need to type:: python demo.py without the "sqlite nuke" part, or you'll clear out the demo again. The backend names are: anydbm bsddb bsddb3 sqlite metakit mysql postgresql You will need support modules installed for all except the first two. If you're not sure whether you have support, run:: python run_tests.py and if you see a line saying "Including XXXX tests" where XXXX is the backend you wish to try, then you're on your way. The mysql and postgresql require their test environments to be set up. Read their respective documents in the "doc" directory to do that. Web Interface ============= Saving and sharing of user queries ---------------------------------- Due to popular demand, the user query saving mechanisms have been overhauled. As before, you may save queries in the tracker by giving the query a name. Each user may only have one query with a given name - if a subsequent search is performed with the same query name supplied, then it will edit the existing query of the same name. Queries may be marked as "private". These queries are only visible to the user that created them. If they're not marked "private" then all other users may include the query in their list of "Your Queries". Marking it as private at a later date does not affect users already using the query, nor does deleting the query. If a user subsequently creates or edits a public query, a new personal version of that query is made, with the same editing rules as described above. You *are not required* to make these changes in your tracker. You only need to make them if you wish to use the new query editing features. It's highly recommended, as the effort is minimal. 1. You will need to edit your tracker's ``dbinit.py`` to change the way queries are stored. Change the lines:: query = Class(db, "query", klass=String(), name=String(), url=String()) query.setkey("name") to:: query = Class(db, "query", klass=String(), name=String(), url=String(), private_for=Link('user')) That is, add the "private_for" property, and remove the line that says ``query.setkey("name")``. 2. You will also need to copy the ``query.edit.html`` template page from the ``templates/classic/html/`` directory of the source to your tracker's ``html`` directory. 3. Once you've done that, edit the tracker's ``page.html`` template to change::
Your Queries
Your Queries (edit)