We've been discussing branching django-project-management to work with
Django 1.2.
At the moment we use django-cms [0] for a couple of things.
1. Documentation. By following the Documentation/Help Files link in the
navigation tree you get taken to a Django CMS instance. Our internal
site has a load of documentation that isn't currently available if you
download the app from Google Code. Having said that there isn't any
reason why we can't release our internal documentation publically as
it's all standard stuff really.
2. Tooltips. When you hover your mouse over a form field you get a popup
giving you a hint as to what the field is for. This also works using
Django CMS.
At the moment django-cms doesn't work with Django 1.2, [1] so it might
be that we have to stick with Django 1.1 until that component gets
updated.
I'll get in touch with the CMS people and ask if this is on their
roadmap.
Grab me on Gtalk if the above isn't clear.
Thanks!
~sm
[0] http://django-cms.org
[1] http://www.django-cms.org/documentation/2.0/installation/
No problems about your reply - work comes first!
> As for the Django-Project-Management to work with Django1.2 , i still
> think we should do some basic works about the upgradation although the
> CMS module could not work with 1.2. After all, it's a trend.
> Could tell me the technologies use by the Tooltips? maybe i can have a
> try.
I've just read on the Django-CMS mailing list [0] that the latest
development version of CMS works with Django1.2 so I'll give that a go
> I was reading a book named "Dreaming in code" recently which tells
> about story about the development of Chandler, and i think it may be
> useful for our Django-Project-Management project.
Thanks for the link, I'll read that.