On Mon, Oct 04, 1999 at 03:41:06PM -0500, Dan Rusch wrote:
Main A A1 A2 B B1
Now lets assume that in B1 I want to use a method that is located in A2 and for reasons to lengthy to get into here, I can't move said method to say Main.
This is sort of similar to some thoughts I'd had while hacking around in Zope. Suppose I have a bunch of utility ExternalMethods that I don't want cluttering up my root directory, and yet want to use them in various different places. Right now I put them all in a folder off of root called "bin," and then use <dtml-var "bin.method()"> to call them. But that hard wires the path into the call. Is there some way, other than acquisition, to specify something like an executable path? I know I can use various combinations of <dtml-with> to do what I want to do, but I'd rather be able to use something like the Python "import" method. Thoughts? dave
On Mon, 4 Oct 1999 davidbro@namshub.org wrote:
This is sort of similar to some thoughts I'd had while hacking around in Zope. Suppose I have a bunch of utility ExternalMethods that I don't want cluttering up my root directory, and yet want to use them in various different places. Right now I put them all in a folder off of root called "bin," and then use
<dtml-var "bin.method()">
to call them. But that hard wires the path into the call. Is there
I see your point but for the purpose your solution is fine IMO (at least this is how I do it too). All you need to do is have the bin directory somewhere in your aquisition path. Remember though that under aquisition external methods and DTML methods will behave different than other Zope objects when called in this way. Pavlos
participants (2)
-
davidbro＠namshub.org -
Pavlos Christoforou