Morgen Sagen wrote:
Now is the best time to straighten this out (early in the release
cycle). I volunteer to modify all the code that currently depends on
osaf.app. The list of items currently in osaf.app, plus my first guess
at where they each should live, is here:
http://wiki.osafoundation.org/bin/view/Journal/FrameworkModularity
If you have an opinion about where a particular item should go, please
add it to the "Notes" column for that item on the above wiki page. I
just want to make sure folks basically agree with the goal of not having
osaf.app be a dependency for framework code.
~morgen
+1
I see osaf.app as residing in the "application" layer of the
architecture -- it should not be a dependency for any layer below it.
http://chandler.osafoundation.org/docs/0.6/overview.html#Layers
Also, assuming that we stick with our proposed tenet of "modular API"
work, this task falls squarely into that tenet.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
