[Chandler-dev] Moving color/etc out of ContentCollection
alecf at osafoundation.org
Wed Mar 22 13:30:56 PST 2006
Phillip J. Eby wrote:
> At 11:57 AM 3/22/2006 -0800, Morgen Sagen wrote:
>> If UserCollection is truly a Chandler-specific concept, then that is
>> fine to put it in osaf.app.
> No, actually, I'm afraid it isn't, as that goes against the 0.7 tenet
> of modularity -- i.e., no circular dependencies.
I don't think anyone is suggesting circular dependencies .. but then
again, I didn't realize we weren't supposed to depend on osaf.app...
> Instead, create a usercollections module, and have osaf.app and
> whatever else *depend* on it.
I could do this in the meantime. I'll try it in my tree and see how it
> Note that nothing should depend on osaf.app, as osaf.app is supposed
> to be the top of the dependency hierarchy.
this runs into our shared but mismatched notion of what osaf.app is :) -
I think unfortunately it has grown beyond your original intent and there
are all sorts of parts of the app which depend on it. Not that we can't
fix this of course..
I'm curious, if osaf.app is the 'root' then where does the ui
(osaf/views/main) fit into this? I guess I imagined the UI as being the
most chandler-specific of all, and that as long as nothing depended on
the UI, we'd be fine.. perhaps this isn't quite right.
> If that's too difficult to implement in 0.7, we should create a
> different module (osaf.root?) to be the top of the dependency
> hierarchy and refactor osaf.app to be general-purpose app facilities.
I'll see how osaf.usercollections pans out, then I'll try this.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
More information about the chandler-dev