I think collective.megaphonesqlstorage would be more appropriate. You should keep the depth of namespaces<http://www.martinaspeli.net/articles/the-naming-of-things-package-names-and-namespaces/?searchterm=deep%20nesting>as low as possible, and I don't think there will be more subpackages for collective.megaphone. You could also use megaphone.sqlstorage instead.
-Roel On Mon, Sep 20, 2010 at 10:59 AM, Kees Hink <[email protected]> wrote: > In order to use Products.sqlpfgadapter [1] with collective.megaphone, some > additional (zcml) setup is needed that i'd like to keep in a separate > product. > > I'd like to use the "collective.megaphone" namespace [2], > "collective.megaphone.sqlstorage" seems a good name for the product. Would > you > agree? > > On a related note: While developing a develop-egg called > "collective.megaphone.sqlstorage" with collective.recipe.omelette, i got an > import error [2] which seems to come from a namespace clash [3]. It's no > big > deal, i can just ditch omelette. But is there a workaround? > > Kees > > [1] http://pypi.python.org/pypi/Products.sqlpfgadapter > [2] ImportError: No module named i18nmessageid () ( > http://pastie.org/1169650) > [3] because it went away when i renamed my product to > collective.megaphone_sql > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers > -- Roel Bruggink http://www.fourdigits.nl/mensen/roel-bruggink Four Digits BV http://www.fourdigits.nl Willemsplein 44, 6811 KD, Arnhem tel: +31(0)26 4422700 fax: +31(0)26 7600012 KVK 091621370000 BTW 8161.22.234.B01
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
