Katie Capps Parlante wrote:
For context when making suggestions, there's a rough before/after picture here:
http://wiki.osafoundation.org/bin/view/Projects/ParcelFlatteningProposal

'pim' is intended to be the location for pim related schema -- more concise than 'contentmodel'. :) Alec, are you arguing that the modules defining the pim schema should live in one big package with everything else?

No no! I just mean that the "osaf" prefix seems unnecessary to me.. I don't see the need to inject the author  organization into the namespace. It looks like Phillip has explained why we use "osaf" further down in the thread, sounds like there is already precedent from zope and the like.

I personally do like the idea of naming things what they are, rather than more abstract, i.e. instead of the proposed osaf.gui, I like perhaps osaf.cpia (the same way we'd have osaf.examples.amazon rather than osaf.examples.onlinestore)

But that's just me - Phillip, I know you're way more familiar with what goes on in other python communities than I am!

Alec


Cheers,
Katie

Alec Flett wrote:
On a related note, why osaf.pim? why not just "chandler"? I'm guessing the argument is that you could reuse these objects outside of chandler, which seems nice.. though even the osaf prefix seems superfluous to me..

So on a related note, I'd like to propose some future renames after you're done with this one
(and maybe you've already thought about this)

osaf.views.main -> chandler (in this case, this really is the chandler product)
osaf.framework.blocks -> cpia or cpia.blocks (break cpia out from being a chandler-only thing)
osaf.framework.attributeEditors -> cpia.attributeEditors (or cpia.attributeeditors?)
osaf.framework.twisted -> chandler.twisted
osaf.framework.scripting -> cpia.script
osaf.app -> chandler
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to