11.07.2008
cwurld
Hi,
Thanks for sharing your django code! I just added myghtyboard to my django site and it seems to be working well.
To get everything to work the way I wanted it to work I had to make some fairly consistent modifications to the views.py. I am wondering if it make sense to add them to your code.
First, my website relies on a context processor to work. So I had to add:
to the "render_to_response" function for each function in the view. I think my use of context processors is pretty standard. And adding such code, won't cause the existing app to stop working. Does it make sense to add this in the official version?
Second, in addition to the data you are already sending to the templates, it would be great to send the name and id of all the elements above that item. So in the template was for a topic, the template would also receive info about the forum and categories that contain that topic. It might make sense to add those fields using a context processor.
Thanks again,
Chuck
Thanks for sharing your django code! I just added myghtyboard to my django site and it seems to be working well.
To get everything to work the way I wanted it to work I had to make some fairly consistent modifications to the views.py. I am wondering if it make sense to add them to your code.
First, my website relies on a context processor to work. So I had to add:
context_instance=RequestContext(request)
to the "render_to_response" function for each function in the view. I think my use of context processors is pretty standard. And adding such code, won't cause the existing app to stop working. Does it make sense to add this in the official version?
Second, in addition to the data you are already sending to the templates, it would be great to send the name and id of all the elements above that item. So in the template was for a topic, the template would also receive info about the forum and categories that contain that topic. It might make sense to add those fields using a context processor.
Thanks again,
Chuck