[kforge-dev] view classes revisited

[John Bywater]

Just a note to say that I've nearly finished the views (again).

It was relatively difficult to develop general support for actions on 
domain objects held as collections by other domain objects, especially 
as I wanted to reuse most of the list/create/read/update/delete code 
from the basic domain object views.

I'm feeling much better about the views now (it was tricky work). But 
things are really quite neat now [1] [2]... :-)

There are some neat abstract classes which really carry the load [3], 
and the concrete view classes are really quite short statements about 
access control, template file, navigation, a bit of workflow, and 
mapping the parsed location onto the domain model. However, these 
aspects could still be refactored much more.

There's also a powerful ViewTestCase [4], which the view class unit 
tests use. There's also good coverage from webunit tests [5].

There are still a few loose ends to finished off (such as finishing 
service and member update and delete views, and redeveloping support for 
extensions to the service object, otherwise known as service plugins). 
But the major problems have been solved, and almost everything is 
working again.

Best regards,

John.

[1] 
http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/views/member.py
[2] 
http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/views/service.py
[3] 
http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/views/base.py
[4] 
http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/views/test/base.py
[5] 
http://project.knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/django/apps/kui/test