Re: [Zope] Little problem with DTML
<!--#var "monthvalues[month]"--> should work, where monthvalues is the name list. But if English names are good for you, than you can store dates as floating point numbers in Gadfly and with <!--#var "PrincipiaTime(Gadfly datefield)"--> or <!--#var "ZopeTime(Gadfly datefield)"--> tags you can show them. With fmt in #var you can specify different formats. Otherwise I prefer the floating point representation in Gadfly, it is more comfortable for me. Best regards, Arpad -----Original Message----- From: FR Chalaoux <chalaouxf@synbio.tpgnet.net> To: zope@zope.org <zope@zope.org> Date: Friday, February 05, 1999 12:32 PM Subject: Re: [Zope] Little problem with DTML Hi Arpad, All I also thought to this solution but in my zope application have to print the date with the month name not only with the month number (ideally). Finally I create a sql method with a 12 selects for each month but it is slow :) If I take your solution I should find a way to translate this month number in month name. I see to direction : 1/ If I can obtain the element i of the propriety list in my folder I win. But how select it, as simply in Python, this element? 2/ Create a Python class in the Zope Extension Folder with this translation capability. I try but had no succes (zope mailing list message :[Zope] - Sort date in gadfly/zope - Thu, 28 Jan 1999 17:50:57 +0100) What do you thinks about? Thanks a lot, FR > Hi, > It is not clear for me why you don't use the ORDER BY clause in your SQL > statement. > Of course in this case you have to store month number instead of month name > in your Gadfly database(to provide the right order). > Cheers, > Arpad François-Régis Chalaoux Bioinformatics Group Synthélabo Biomoléculaire 67080 Strasbourg Cedex FRANCE Tél : 03 88 60 87 14 Fax : 03 88 45 90 70 _______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
Hi Arpad, All, I should have a good week-end with all your tips, thanks. Where did you find all this information in zope documentation : <FontFamily><param>Times New Roman</param><<!--#var "monthvalues[month]"--><bigger> <smaller><<!--#var "PrincipiaTime(Gadfly datefield)"--> <<!--#var "ZopeTime(Gadfly datefield)"--> <FontFamily><param>Arial</param>I often have problems with zope documentation. Maybe it could be a good idea if community lake information to think about a ZDP (Zope Documentation Project) system? A+, FR. François-Régis Chalaoux Bioinformatics Group Synthélabo Biomoléculaire 67080 Strasbourg Cedex FRANCE Tél : 03 88 60 87 14 Fax : 03 88 45 90 70
Hi All, I often have problems with zope documentation. Maybe it could be an idea if community lake information to think about a ZDP (Zope Documentation Project)? FR François-Régis Chalaoux Bioinformatics Group Synthélabo Biomoléculaire 67080 Strasbourg Cedex FRANCE Tél : 03 88 60 87 14 Fax : 03 88 45 90 70
At 06:59 PM 2/5/99 +0100, FR Chalaoux wrote:
I often have problems with zope documentation. Maybe it could be an idea if community lake information to think about a ZDP (Zope Documentation Project)?
I like this idea. I would be very happy to open the documentation process up to more community participation. I understand that Zope documentation can be frustrating, and I'd love to hear about your ideas for improving things. It is my hope that now that we are getting more people on board we will be able to make improvements in documentation and in enabling community participation in general. Let me briefly give some of my views on the documentation situation: * Understanding what Zope is and what you can do with it is hard. I think we need to restructure our web site to give a better and simpler explanation of what you can do with Zope and why you'd want to use it. We also plan to include more informative and useful default content, including more examples. * Finding out how to do a specific task with Zope can be hard. The are a couple reasons for this. We do not have a simple way to search the documentation. The documentation is not as clearly labeled as it could be. Some features are still undocumented (but not many). Zope can be used for many, many different things, so the range of problems is quite large--from how to best compile and configure Apache on a given flavor of Unix, to how to best write SQL for a given type of query, to how to best produce HTML select widgets with DTML, to how to minimize FTP denial of service attacks, to the rules of Structured Text mark up, to how best to convert between different Python date and time formats. I think we need to move to a better classified documentation system, and provide a system of searching the documentation. We should probably also try to cull interesting information from the mailing list to beef up the support and how-to documentation. * Getting your question answered on the Zope list can be hard. The Zope list is getting a lot of traffic. In addition, many questions are rather involved. Despite this, many questions actually do get answered. Hopefully, the upcoming list split will help by segmenting list traffic and help more questions get answered. * Figuring out how to extend Zope can be hard. The Zope API is complex, and the Zope internals are large. It can be hard to understand the Zope overall design well enough to decide if you should create a Folderish Product, and new DTML tag, or an External Method. Figuring out what methods are available to you, and which ones you might want to use is also tough. I think that the Product API tutorial helps. Also the Object Reference is an invaluable aide. Extending Zope is not for everyone. Perhaps the lever and Zope classes will eventually lower the threshold so that more people will be able to extend the platform. I look forward to a better documentation process that will help more people get the most out of Zope. -Amos -- Amos Latteier mailto:amos@digicool.com Digital Creations http://www.digicool.com/
participants (3)
-
Amos Latteier -
Arpad Kiss -
chalaouxf＠synbio.tpgnet.net