[Cosmo-dev] Refactor of cal_main.js
Matthew Eernisse
mde at osafoundation.org
Tue Aug 15 11:25:17 PDT 2006
John Townsend wrote:
> Your note here makes me immediately think.. We could come up with some
> nice abstractions and interfaces that encapsulate some of the items you
> mention above. For example taking the conflict-resolution code out of
> the main file and refactoring it into a conflict resolver abstraction
> and try to layer its work (i.e. conflict abstraction at an abstract or
> data level followed by an abstraction for rendering conflicts. I don't
> fully know the details of this code, so I might be speaking out of turn :-)
That's actually the direction I'm trying to go with this too. I proposed
something like:
app.view.cal.conflict
Event conflict calculations
Where all that code would live. I think where I need help is in making
these pieces-parts into clean and self-contained abstractions. I hope
BCM and Bobby can give me some help with that.
> I agree with BCM. Taking a step back and thinking about the overall
> design would be helpful at this stage. You now have a view of the roles
> and responsibilities within the code and we can take a hard look at that
> view and see if we can come with a way of rendering it that is more
> flexible, extensible, and maintainable. I personally am a big fan on
> clean and simple abstractions :-)
Sounds good. We need to take advantage of the time while I'm here, and
get some of this stuff up on the whiteboard. Anything that shakes out of
this, we can make sure gets posted to the list.
Matthew
More information about the cosmo-dev
mailing list