George Lee
2006-10-03 21:27:21 UTC
Hi all!
Hit by a fit of Zope3-ish inspiration, yesterday and today I've been
working on refactoring CalendarX 0.6.6 to use Zope3/Five technology,
in particular views. So far it's been going pretty well, with some
good simplification to the page templates -- getting rid of a lot of
the python logic -- and being able to move stuff out of the many
skinned .py like getEventDictMonth into Zope3 views.
I was really happy to see how some of the coding practices of
CalendarX has made it fairly straightforward to change things into
Zope3 views, because the dictionaries the different calendar views and
events were using, already had a lot of the same structure that the
views will use. At the same time, moving things into views is forcing
eliminating redundancies, centralizing code rather than reusing the
same code in many different places, and more clearly separating
unrelated code.
As things get Zope3-ified, it should be a lot easier to understand and
test the code and make programming customizations.
Anyway, I'll keep you all updated on the progress and hopefully this
will be helpful in making CalendarX easier to customize/develop/test
and moving CalendarX forward!
Peace,
George
Hit by a fit of Zope3-ish inspiration, yesterday and today I've been
working on refactoring CalendarX 0.6.6 to use Zope3/Five technology,
in particular views. So far it's been going pretty well, with some
good simplification to the page templates -- getting rid of a lot of
the python logic -- and being able to move stuff out of the many
skinned .py like getEventDictMonth into Zope3 views.
I was really happy to see how some of the coding practices of
CalendarX has made it fairly straightforward to change things into
Zope3 views, because the dictionaries the different calendar views and
events were using, already had a lot of the same structure that the
views will use. At the same time, moving things into views is forcing
eliminating redundancies, centralizing code rather than reusing the
same code in many different places, and more clearly separating
unrelated code.
As things get Zope3-ified, it should be a lot easier to understand and
test the code and make programming customizations.
Anyway, I'll keep you all updated on the progress and hopefully this
will be helpful in making CalendarX easier to customize/develop/test
and moving CalendarX forward!
Peace,
George