December 2003 - Zope

Rv: Re: [Zope] How to replace catalogaware base class with catalogpathaware in a Zclass?
by Yurj 03 Dec '03

03 Dec '03

--------- Messaggio Originale -------- Da: Dieter Maurer <dieter(a)handshake.de> Per: Yurj <yurj(a)alfa.it> Cc: zope(a)zope.org Oggetto: Re: [Zope] How to replace catalogaware base class with catalogpathaware in a Zclass? Data: 01/12/03 18:28 > > Yurj wrote at 2003-11-30 19:09 -0100: > > How to replace catalogaware base class with catalogpathaware in a Zclass? > > > > Calogaware has path problem with virtual host monster... > > I would reimplement "CatalogAware" by "CatalogPathAware" > (after that, both were the same). How? :)) A new product or editing the source? > I do not know why this has not been done in the first place -- > maybe some backward compatibility issue. Zclass? :)) I don't understand why ZClass has been promoted so much in the Zope Book while they're not supported much by the comunity :P > > There is a quite difficult alternative: rebasing your ZClass. > You should find a HowTo on Zope.org. Black magic for me =) > -- > Dieter > > > > ________________________________________________ Message sent using ALFANET Caorle WEBMAIL 1.0

3 2

Managing a pool of database connections
by David Mitchell 03 Dec '03

03 Dec '03

Hello list, I have a bunch of Postgres databases, containing archived data. The number of databases is growing over time, and already numbers several thousand. I want to give my Zope users the ability to do the following: - specify a database to connect to - select from a list of "lookup" values for certain fields in that database - search the database for data based on the entered "lookup" values - display the results The only part I'm having trouble with is the first step. I don't want to pre-define thousands of database connections, and have to continually add new connections - most of the databases will only be accessed rarely, so creating all those database definitions would constitute a significant time and resource drain. What I'd like to do is: - user enters a database name - a new Zope database connection gets created programmatically, pointing to the requested database (how do I do this???) - using this database connection, we look for data in several tables and present the results as "lookup" values - user searches for data - results displayed - user disconnects, times out or logs out - database connection gets closed Is it possible to create and destroy database connections in Zope like this, and if so, what's the best way to go about it? Regards Dave Mitchell

2 1

The Uncertainty Principle Is Untenable
by Bob 03 Dec '03

03 Dec '03

please reply to hdgbyi(a)public.guangzhou.gd.cn thank you. THE UNCERTAINTY PRINCIPLE IS UNTENABLE By re-analysing Heisenberg's Gamma-Ray Microscope experiment and the ideal experiment from which the uncertainty principle is derived, it is actually found that the uncertainty principle can not be obtained from them. It is therefore found to be untenable. Key words: uncertainty principle; Heisenberg's Gamma-Ray Microscope Experiment; ideal experiment Ideal Experiment 1 Heisenberg's Gamma-Ray Microscope Experiment A free electron sits directly beneath the center of the microscope's lens (please see AIP page http://www.aip.org/history/heisenberg/p08b.htm or diagram below) . The circular lens forms a cone of angle 2A from the electron. The electron is then illuminated from the left by gamma rays--high energy light which has the shortest wavelength. These yield the highest resolution, for according to a principle of wave optics, the microscope can resolve (that is, "see" or distinguish) objects to a size of dx, which is related to and to the wavelength L of the gamma ray, by the expression: dx = L/(2sinA) (1) However, in quantum mechanics, where a light wave can act like a particle, a gamma ray striking an electron gives it a kick. At the moment the light is diffracted by the electron into the microscope lens, the electron is thrust to the right. To be observed by the microscope, the gamma ray must be scattered into any angle within the cone of angle 2A. In quantum mechanics, the gamma ray carries momentum as if it were a particle. The total momentum p is related to the wavelength by the formula, p = h / L, where h is Planck's constant. (2) In the extreme case of diffraction of the gamma ray to the right edge of the lens, the total momentum would be the sum of the electron's momentum P'x in the x direction and the gamma ray's momentum in the x direction: P' x + (h sinA) / L', where L' is the wavelength of the deflected gamma ray. In the other extreme, the observed gamma ray recoils backward, just hitting the left edge of the lens. In this case, the total momentum in the x direction is: P''x - (h sinA) / L''. The final x momentum in each case must equal the initial x momentum, since momentum is conserved. Therefore, the final x momenta are equal to each other: P'x + (h sinA) / L' = P''x - (h sinA) / L'' (3) If A is small, then the wavelengths are approximately the same, L' ~ L" ~ L. So we have P''x - P'x = dPx ~ 2h sinA / L (4) Since dx = L/(2 sinA), we obtain a reciprocal relationship between the minimum uncertainty in the measured position, dx, of the electron along the x axis and the uncertainty in its momentum, dPx, in the x direction: dPx ~ h / dx or dPx dx ~ h. (5) For more than minimum uncertainty, the "greater than" sign may added. Except for the factor of 4pi and an equal sign, this is Heisenberg's uncertainty relation for the simultaneous measurement of the position and momentum of an object. Re-analysis To be seen by the microscope, the gamma ray must be scattered into any angle within the cone of angle 2A. The microscope can resolve (that is, "see" or distinguish) objects to a size of dx, which is related to and to the wavelength L of the gamma ray, by the expression: dx = L/(2sinA) (1) This is the resolving limit of the microscope and it is the uncertain quantity of the object's position. The microscope can not see the object whose size is smaller than its resolving limit, dx. Therefore, to be seen by the microscope, the size of the electron must be larger than or equal to the resolving limit. But if the size of the electron is larger than or equal to the resolving limit dx, the electron will not be in the range dx. Therefore, dx can not be deemed to be the uncertain quantity of the electron's position which can be seen by the microscope, but deemed to be the uncertain quantity of the electron's position which can not be seen by the microscope. To repeat, dx is uncertainty in the electron's position which can not be seen by the microscope. To be seen by the microscope, the gamma ray must be scattered into any angle within the cone of angle 2A, so we can measure the momentum of the electron. dPx is the uncertainty in the electron's momentum which can be seen by microscope. What relates to dx is the electron where the size is smaller than the resolving limit. When the electron is in the range dx, it can not be seen by the microscope, so its position is uncertain. What relates to dPx is the electron where the size is larger than or equal to the resolving limit .The electron is not in the range dx, so it can be seen by the microscope and its position is certain. Therefore, the electron which relates to dx and dPx respectively is not the same. What we can see is the electron where the size is larger than or equal to the resolving limit dx and has a certain position, dx = 0. Quantum mechanics does not rely on the size of the object, but on Heisenberg's Gamma-Ray Microscope experiment. The use of the microscope must relate to the size of the object. The size of the object which can be seen by the microscope must be larger than or equal to the resolving limit dx of the microscope, thus the uncertain quantity of the electron's position does not exist. The gamma ray which is diffracted by the electron can be scattered into any angle within the cone of angle 2A, where we can measure the momentum of the electron. What we can see is the electron which has a certain position, dx = 0, so that in no other position can we measure the momentum of the electron. In Quantum mechanics, the momentum of the electron can be measured accurately when we measure the momentum of the electron only, therefore, we have gained dPx = 0. And, dPx dx =0. (6) Every physical principle is based on an Ideal Experiment, not based on MATHEMATICS, including heisenberg uncertainty principle. For example, the Law of Conservation of Momentum is based on the collision of two stretch ball in the vacuum; the Principle of equivalence(general relativity) is besed on the Einstein's laboratory in the lift. Heisenberg's Gamma-Ray Microscope experiment is an ideal experiment. Einstein said, One Experiment is enough to negate a physical principle. Heisenberg's Gamma-Ray Microscope experiment has negated the uncertainty principle. Ideal experiment 2 Single Slit Diffraction Experiment Suppose a particle moves in the Y direction originally and then passes a slit with width dx(Please see diagram below) . The uncertain quantity of the particle's position in the X direction is dx, and interference occurs at the back slit . According to Wave Optics , the angle where No.1 min of interference pattern is can be calculated by following formula: sinA=L/2dx (1) and L=h/p where h is Planck's constant. (2) So the uncertainty principle can be obtained dPx dx ~ h (5) Re-analysis According to Newton first law , if an external force in the X direction does not affect the particle, it will move in a uniform straight line, ( Motion State or Static State) , and the motion in the Y direction is unchanged .Therefore , we can learn its position in the slit from its starting point. The particle can have a certain position in the slit and the uncertain quantity of the position is dx =0. According to Newton first law , if the external force at the X direction does not affect particle, and the original motion in the Y direction is not changed , the momentum of the particle int the X direction will be Px=0 and the uncertain quantity of the momentum will be dPx =0. This gives: dPx dx =0. (6) No experiment negates NEWTON FIRST LAW. Whether in quantum mechanics or classical mechanics, it applies to the microcosmic world and is of the form of the Energy-Momentum conservation laws. If an external force does not affect the particle and it does not remain static or in uniform motion, it has disobeyed the Energy-Momentum conservation laws. Under the above ideal experiment , it is considered that the width of the slit is the uncertain quantity of the particle's position. But there is certainly no reason for us to consider that the particle in the above experiment has an uncertain position, and no reason for us to consider that the slit's width is the uncertain quantity of the particle. Therefore, the uncertainty principle, dPx dx ~ h (5) which is derived from the above experiment is unreasonable. Conclusion >From the above re-analysis , it is realized that the ideal experiment demonstration for the uncertainty principle is untenable. Therefore, the uncertainty principle is untenable. Reference: 1. Max Jammer. (1974) The philosophy of quantum mechanics (John wiley & sons , Inc New York ) Page 65 2. Ibid, Page 67 3. http://www.aip.org/history/heisenberg/p08b.htm Author : BingXin Gong Postal address : P.O.Box A111 YongFa XiaoQu XinHua HuaDu GuangZhou 510800 P.R.China E-mail: hdgbyi(a)public.guangzhou.gd.cn Tel: 86---20---86856616

1 0

Re: 2 question
by Gabriel Genellina 03 Dec '03

03 Dec '03

At 2/12/2003 14:37, you wrote: Please keep posting on the list. >I have an logo image, named logo. >When I use dtml, the <dtml-var logo> is working. > >But: when I use , then the zope replace >the <> signs in image definition, and it is don't showed, only it's >description. > >Why ? That line should give you a syntax error - I guess you wrote something different... Please read the Zope Book, there are two chapters and an Appendix about Page Templates. Try the examples, modify them, try some "what if..." variants. That's a good way to learn something new. >And why I feel that tal is known less than dtml ? Because it's newer, I presume. >2./ >I read the Book, I read every on the web, but I can't see example, how >to I access the transaction of an ZSQL method. > >There is a web-site, with apply possibility. >But I want to write more tables, and I want to protect/isolate it with >transaction. If it is get error, then I want to rollback... Just don't bother - Zope and the corresponding DA should manage that. If you dont trust them, try it yourself: raise an exception by code and see if the transaction was aborted or not. Gabriel Genellina Softlab SRL

1 0

RE: [Zope] Two more questions
by Goldthwaite, Joe 03 Dec '03

03 Dec '03

Thanks again. Still no go although it looks like it's getting closer. I tried this; <tr tal:replace="item python:here.GetISLines(FY=request.FY, Per=request.Per)"> To my programmer eyes, that looks like it might be correct. I got a really strange error though; Error Type: TypeError Error Value: unsupported operand type(s) for - Does this mean that I have an unsupported operand for the nothing after the dash or is it for the dash? There's no dash in the statement so I guess I have an unsupported operand for nothing :~{ P.S. Tim, sorry for sending this message twice. When I reply it goes directly to the source instead of the list and I forget to type the zope(a)zope.org before I send it. -----Original Message----- From: Tim Zegir [mailto:trzegir@ncable.net.au] Sent: Tuesday, December 02, 2003 6:48 PM To: joe(a)goldthwaites.com Subject: RE: [Zope] Two more questions Hi Joe, I had another look and realized I was doing the wrong thing ;) Try this instead. <tr tal:repeat="python:here.GetISLines(FY=request.FY;Per=request)"> From Tim Zegir -----Original Message----- From: zope-bounces(a)zope.org [mailto:zope-bounces@zope.org] On Behalf Of Goldthwaite, Joe Sent: Wednesday, 3 December 2003 12:23 PM To: zope(a)zope.org Subject: RE: [Zope] Two more questions Thanks Tim, It didn't work. I get a SyntaxError on the question mark. Specifically; Compilation failed TAL.TALDefs.TALError: Python expression error: GetISLines?FY=request ^ SyntaxError: invalid syntax in expression 'python:GetISLines?FY=request', at line 10, column 5 This brings up more questions. I assume that GetISLines is looked up through acquisition. FY is the name of one of my parameters. How does it know that I want the FY attribute of the request object? Also, how would I pass two parameters? "GetISLines?FY=request;Per=request"? -----Original Message----- From: Tim Zegir [mailto:trzegir@ncable.net.au] Sent: Tuesday, December 02, 2003 5:46 PM To: joe(a)goldthwaites.com Subject: RE: [Zope] Two more questions Sorry about the last email :) In answer to the second question Try something like this: <tr tal:repeat="item python:GetISLines?FY=request"> >From Tim Zegir -----Original Message----- From: zope-bounces+trzegir=ncable.net.au(a)zope.org [mailto:zope-bounces+trzegir=ncable.net.au@zope.org] On Behalf Of Goldthwaite, Joe Sent: Wednesday, 3 December 2003 11:36 AM To: zope(a)zope.org Subject: [Zope] Two more questions I really hate to keep bothering everyone but I'm still running into things I don't understand. In order to keep my table headers consistent across reports, I have them stored as a separate DTML method called IS_Ptd_Header. In my main Income Statement, I have this where I want the table header to show up; This works fine. The problem I've run into is when I want to use tal tags in the header like this; Income Statement for period Period If I have this line in the Income Statement, I get the Per parameter from the URL. The same line in IS_Ptd_Header gets ignored so the resulting page shows "Income Statement for period period". I thought that maybe the tal tags were being ignored because IS_Ptd_Header is a DTML method so I created a ZPT with the name IS_YTD_Header and used that in the tal replace command but the result came back as HTML quoted text instead of the actual HTML. Anyone know what I'm missing? Second problem. I have an external method called GetISLines. The actual function being called looks like this; def GetISLines(FY = 2, Per = 12, CatType = "Grp", Categories = ""): c = ISLines(FY, Per, CatType, Categories) return c.DefLines I've been doing all my testing using the default arguments with this tal tag; <tr tal:repeat="item here/GetISLines"> I need to pass in the URL parameters but I can't figure out how to do it. <tr tal:repeat="item here/GetISLines(request.FY)"> doesn't work. Nothing else I've tried works either. How do you pass parameters to an external function? Thanks. Joe Goldthwaite _______________________________________________ Zope maillist - Zope(a)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 ) _______________________________________________ Zope maillist - Zope(a)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 ) Property of Bar-S Foods. This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, dissemination of this communication is prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at 602.264.7272 or postmaster(a)bar-s.com.

4 8

RE: [Zope] Two more questions
by Goldthwaite, Joe 03 Dec '03

03 Dec '03

have an unsupported operand for nothing :~{ P.S. Tim, sorry for sending this message twice. When I reply it goes directly to the source instead of the list and I forget to type the zope(a)zope.org before I send it. -----Original Message----- From: Tim Zegir [mailto:trzegir@ncable.net.au] Sent: Tuesday, December 02, 2003 6:48 PM To: joe(a)goldthwaites.com Subject: RE: [Zope] Two more questions Hi Joe, I had another look and realized I was doing the wrong thing ;) Try this instead. <tr tal:repeat="python:here.GetISLines(FY=request.FY;Per=request)"> From Tim Zegir -----Original Message----- From: zope-bounces(a)zope.org [mailto:zope-bounces@zope.org] On Behalf Of Goldthwaite, Joe Sent: Wednesday, 3 December 2003 12:23 PM To: zope(a)zope.org Subject: RE: [Zope] Two more questions Thanks Tim, It didn't work. I get a SyntaxError o=request;Per=request"? -----Original Message----- From: Tim Zegir [mailto:trzegir@ncable.net.au] Sent: Tuesday, December 02, 2003 5:46 PM To: joe(a)goldthwaites.com Subject: RE: [Zope] Two more questions Sorry about the last email :) In answer to the second question Try something like this: <tr tal:repeat="item python:GetISLines?FY=request"> >From Tim Zegir -----Original Message----- From: zope-bouncele header to show up; This works fine. The problem I've run into is when I want to use tal tags in the header like this; Income Statement for period Period If I have this line in the Income Statement, I get the Per parameter from the URL. The same line in IS_Ptd_Header gets ignored so the resulting page shows "Income Statement for period period". I thought that maybe the tal tags were beingies = ""): c = ISLines(FY, Per, CatType, Categories) return c.DefLines I've been doing all my testing using the default arguments with this tal tag; <tr tal:repeat="item here/GetISLines"> I need to pass in the URL parameters but I can't figure out how to do it. <tr tal:repeat="item here/GetISLines(request.FY)"> doesn't work. Nothing else I've tried works either. How do you pass parameters to an external function? Thanks. Joe Goldthwaite ________________________________tp://mail.zope.org/mailman/listinfo/zope-dev )

1 0

INFROMATION.
by TANKO NELSON 03 Dec '03

03 Dec '03

DEAR SIR, AM WRITING THIS MAIL TO KNOW MUCH ABOUT YOUR COURSES FOR QUALIFIED TEACHERS WHO NEED A FOREIGN EXPERIENCE AND CERTIFICATE, SO THAT WE CAN ARRANGE TO ATTEND FOR THE COURSE.SO WE WILL NEED OUR COURSE PROGRAMS AND PRICES AS SOON AS POSSIBLE. THANKS FOR THE SERVICE. BEST REGARDS FROM NATIONAL ASSOCIATION OF TEACHERS (NAT) _____________________________________________________________ ez2www.com Metasearch the Invisible Web. Sign up now for your FREE email at http://ez2www.com.

1 0

RE: [Zope] Zope threads dying continuosly
by Tim Edwards 03 Dec '03

03 Dec '03

Just an update: we have now switched back to Red Hat 8 and MySQl for our primary application (the company Intranet/Portal) which we release soon. This combination seems to be far more stable. Although we still have slow-downs when the server is under heavy loads it doesn't crash - it only stops responding for a bit. This seems more like a normal load-balancing/performance issue than stability problems. Our machine is a dual P4 2ghz w/ 1gb RAM and RAID disks. I would recommend that anyone wanting to use Zope stay well away from Red Hat 9, having said I'd like to know which distributions people use for their production systems? We still may be having issues with mxODBC connecting to MS SQL Server in Red Hat 8, but we need to test that a bit more. -----Original Message----- From: Dennis Allison [mailto:allison@sumeru.stanford.EDU] Sent: Friday, 21 November 2003 5:40 PM To: Tim Edwards Cc: 'zope(a)zope.org' Subject: RE: [Zope] Zope threads dying continuosly Tim-- I've been running Zope and MySQL on RH9 but the system has been very unstable even after we upgraded to the bleeding edge (kernel and glibc), set all the magic parameters, etc. I had been using Pound as a load distributing reverse proxy under RH7.3, but it fails under RH9. I wrote my own reverse proxy modifying Pydirector but it has had its problems, possibly also related to RH9 thread problems. Still, we appear to have had an easy time of it relative to the disasterous problems you see. I run on a Athlon dual processor system, 4GB of memory, and a RAID disk. We use Zope 2.6.2b3 with Python 2.1.3. I'm curious what kind of processor you are using. Is it one of the hyperthreaded Intel P4 machines? Anyhow, the bad experiences with RH9 and the changes Redhat is making to their business model have motivated me to explore other distributions. Over the next few days, I'm planning to move our Zopes onto a new OS, one based on the Gentoo distribution. I trolled for comments a week or three ago and Gentoo got raves from several folks I trust. Moving to a different operating system might be the right thing. If you remain with RH9, you should be running the latest kernel and the latest glibc. You may find it useful to export into the environment LD_ASSUME_KERNEL=2.4.1 MySQL and Zope to turn off the new posix threading library which seems to be the culprit (or one of the culprits). On Fri, 21 Nov 2003, Tim Edwards wrote: > Hmmm... I'll try and explain a bit more about our problems. We found Zope to > be generally unstable in that, after a few mins up to an hour or so, Zope > would sometimes freeze. Also when multiple people were accessing a Zope > application that retreives or modifies data in our MS SQL Server database > the Zope server would freeze and have to be restarted - always, not just > some of the time. > > After installing a glibc update for Red Hat 9 that fixes a problem with > Python programs not being able to create threads and specifying the -t > option in the Zope start script (yes with 500 threads!) it seemed a lot more > stable. Now multiple people can use our database access application without > it crashing. As for the 500 threads I have now put it down to 9, however it > doesnt seem to make that much of a difference in resources - a ps listing > tells us we only ever have the normal 2 z2.py processes open at a time. > > I am now running the Zope server in debug mode on a terminal and can see > that it occaisionally crashes and automatically restarts iteself. Also if I > go into the management interface and click on a ZSQL method it crashes - and > then restarts itself. Applications that use those methods still seem to work > for some reason. However I cannot get to the management interface page for > any ZSQL method in the whole Zope installation. > > Thanks > > > -----Original Message----- > From: Dylan Reinhardt [mailto:zope@dylanreinhardt.com] > Sent: Friday, 21 November 2003 4:16 PM > To: Tim Edwards > Cc: 'Zope(a)zope.org' > Subject: RE: [Zope] Zope threads dying continuosly > > > On Thu, 2003-11-20 at 18:15, Tim Edwards wrote: > > Thanks for your replies, the original reason I asked is that we are having > > stability issues with Zope. > > Such as...? > > > I have tried it without the demon process, but > > that doesn't appear to help. I then reenabled the demon process and > changed > > the thread count to 500 > > 500 is a huge number of threads. You should probably stick with single > digits until you have a well-formed case for doing otherwise. > > HTH, > > Dylan > > _______________________________________________ > Zope maillist - Zope(a)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 ) >

2 1

RE: [Zope] Two more questions
by Goldthwaite, Joe 03 Dec '03

03 Dec '03

Thanks Tim, It didn't work. I get a SyntaxError on the question mark. Specifically; Compilation failed TAL.TALDefs.TALError: Python expression error: GetISLines?FY=request ^ SyntaxError: invalid syntax in expression 'python:GetISLines?FY=request', at line 10, column 5 This brings up more questions. I assume that GetISLines is looked up through acquisition. FY is the name of one of my parameters. How does it know that I want the FY attribute of the request object? Also, how would I pass two parameters? "GetISLines?FY=request;Per=request"? -----Original Message----- From: Tim Zegir [mailto:trzegir@ncable.net.au] Sent: Tuesday, December 02, 2003 5:46 PM To: joe(a)goldthwaites.com Subject: RE: [Zope] Two more questions Sorry about the last email :) In answer to the second question Try something like this: <tr tal:repeat="item python:GetISLines?FY=request"> >From Tim Zegir -----Original Message----- From: zope-bounces+trzegir=ncable.net.au(a)zope.org [mailto:zope-bounces+trzegir=ncable.net.au@zope.org] On Behalf Of Goldthwaite, Joe Sent: Wednesday, 3 December 2003 11:36 AM To: zope(a)zope.org Subject: [Zope] Two more questions I really hate to keep bothering everyone but I'm still running into things I don't understand. In order to keep my table headers consistent across reports, I have them stored as a separate DTML method called IS_Ptd_Header. In my main Income Statement, I have this where I want the table header to show up; This works fine. The problem I've run into is when I want to use tal tags in the header like this; Income Statement for period Period If I have this line in the Income Statement, I get the Per parameter from the URL. The same line in IS_Ptd_Header gets ignored so the resulting page shows "Income Statement for period period". I thought that maybe the tal tags were being ignored because IS_Ptd_Header is a DTML method so I created a ZPT with the name IS_YTD_Header and used that in the tal replace command but the result came back as HTML quoted text instead of the actual HTML. Anyone know what I'm missing? Second problem. I have an external method called GetISLines. The actual function being called looks like this; def GetISLines(FY = 2, Per = 12, CatType = "Grp", Categories = ""): c = ISLines(FY, Per, CatType, Categories) return c.DefLines I've been doing all my testing using the default arguments with this tal tag; <tr tal:repeat="item here/GetISLines"> I need to pass in the URL parameters but I can't figure out how to do it. <tr tal:repeat="item here/GetISLines(request.FY)"> doesn't work. Nothing else I've tried works either. How do you pass parameters to an external function? Thanks. Joe Goldthwaite _______________________________________________ Zope maillist - Zope(a)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 )

1 0

Two more questions
by Goldthwaite, Joe 03 Dec '03

03 Dec '03

I really hate to keep bothering everyone but I'm still running into things I don't understand. In order to keep my table headers consistent across reports, I have them stored as a separate DTML method called IS_Ptd_Header. In my main Income Statement, I have this where I want the table header to show up; This works fine. The problem I've run into is when I want to use tal tags in the header like this; Income Statement for period Period If I have this line in the Income Statement, I get the Per parameter from the URL. The same line in IS_Ptd_Header gets ignored so the resulting page shows "Income Statement for period period". I thought that maybe the tal tags were being ignored because IS_Ptd_Header is a DTML method so I created a ZPT with the name IS_YTD_Header and used that in the tal replace command but the result came back as HTML quoted text instead of the actual HTML. Anyone know what I'm missing? Second problem. I have an external method called GetISLines. The actual function being called looks like this; def GetISLines(FY = 2, Per = 12, CatType = "Grp", Categories = ""): c = ISLines(FY, Per, CatType, Categories) return c.DefLines I've been doing all my testing using the default arguments with this tal tag; <tr tal:repeat="item here/GetISLines"> I need to pass in the URL parameters but I can't figure out how to do it. <tr tal:repeat="item here/GetISLines(request.FY)"> doesn't work. Nothing else I've tried works either. How do you pass parameters to an external function? Thanks. Joe Goldthwaite

1 0