Part of my product's job is to create a top-level folder. Currently, I can only get it to create the folder in what ever folder the product is added in. I would like to be able to get access to the root directory object but don't know how. How do I access the root directory object? Would 'getPhysicalRoot' do that? If yes, how do I use it? -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
getPhysicalRoot() or restrictedTraverse("/") would do the job. -aj --On Sonntag, 30. März 2003 19:45 Uhr -0500 Matt Ficken <mattficken@mail.com> wrote:
Part of my product's job is to create a top-level folder. Currently, I can only get it to create the folder in what ever folder the product is added in. I would like to be able to get access to the root directory object but don't know how.
How do I access the root directory object? Would 'getPhysicalRoot' do that? If yes, how do I use it? -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Matt Ficken wrote, to both zope@zope.org and zope-dev@zope.org:
Part of my product's job is to create a top-level folder. Currently, I can only get it to create the folder in what ever folder the product is added in. I would like to be able to get access to the root directory object but don't know how.
How do I access the root directory object? Would 'getPhysicalRoot' do that? If yes, how do I use it?
Matt, Please don't post a message to both zope@zope.org and zope-dev@zope.org. You'll see this at the bottom of each message on the zope-dev@zope.org list: _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** The question you are asking should be asked on zope@zope.org, not zope-dev@zope.org. Andreas was kind enough to answer, but please do try the zope@zope.org list first. The zope-dev@zope.org list is for discussing the development of Zope and its internals, not for discussing how to use Zope and its API. -- Steve Alexander
You'll see this at the bottom of each message on the zope-dev@zope.org list:
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! **
The question you are asking should be asked on zope@zope.org, not zope-dev@zope.org. Andreas was kind enough to answer, but please do try the zope@zope.org list first.
The zope-dev@zope.org list is for discussing the development of Zope and its internals, not for discussing how to use Zope and its API.
Maybe the bottom message should be clearer on the purpose? "No cross posts" doesn't really help one decide which list to use. "zope-dev" == "development using zope" sounds plausible enough... --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum wrote:
"zope-dev" == "development using zope" sounds plausible enough...
And I again will throw in my vote for actually letting it be that, and use zope-coders for the development OF zope. :) zope@zope.org is huge, and I thing development of new products should have it's own list, becuase topics now risk drowning in zope@zope's volume. Just my 0.02 EUR. I'm not claiming to actually be right. :)
participants (5)
-
Andreas Jung -
Guido van Rossum -
Lennart Regebro -
Matt Ficken -
Steve Alexander