Re: mini-wiki advice

2006-04-02 Thread tonemcd
Here's something I'm using in an application - it uses the 'Textile' engine so that the person entering the markup doesn't have to worry about HTML. Works well! It's in a model, and this is all MR by the way; class Person(models.Model): ... expectations = models.TextField('Expectations body'

Re: mini-wiki advice

2006-04-01 Thread Julio Nobrega
Translation from Wiki to HTML "on-the-fly" (to display) are fine. Don't prebuild and store the HTML because you might want to change the presentation of a wiki tag later. You can use the Title field to get the revisions and its sequence, if you order by the primary key, since it increments. (

Re: mini-wiki advice

2006-04-01 Thread akaihola
Wouldn't it be more useful to store the revision number as a field instead of building a chain of links for the revision history? I'm not sure how straightforward it is to fetch the record with the largest revision number in Django though, but a boolean 'current' field would be a quick work-around

mini-wiki advice

2006-03-30 Thread shredwheat
I want a pages of my site to be editable by signed in members. This seems simple enough, but I'm not sure of the best strategy. This does not need to be a full on wiki style system, since the number of pages will be fixed and only about 10 or so. The main goals I am after: - simple text markup