[Cosmo-dev] Refactor of cal_main.js

[Brian Moseley]

On 8/14/06, Matthew Eernisse <mde at osafoundation.org> wrote:

> Initially at least, I mainly just want to get the increasingly
> monolithic Cal object in cal_main.js broken up (before it develops its
> own gravitational field). I'm really just aiming at getting some logical
> subdivisions in the existing code -- but hopefully what we come up with
> will get us to something resembling a roadmap for evolving the codebase
> toward the more decentralized set of objects and object interactions
> that we want.

how is extracting the current code into separate files going to help a
future redesign? does chopping up the code like this help you get a
better handle on what's there? seems like you have a pretty good idea
already.

it looks like you've done a good job of listing all the different
responsibilities of the existing code. why don't we sit down and work
out how to assign those responsibilities to different classes and map
out their collaborations? i think this will address the real need,
whereas simply partitioning code into different files won't achieve
any real benefit and will just add more import statements.