Re: [Zope-dev] How long below the radar?
On 10 Jul 2001 08:06:42 +0200, you wrote: >| How about treating some of the most critically needed Zope modules >| as a community project? >I agree totally. So what do you think are the most needed Zope products? Regards, René Pijlman ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog out of Zope
On Sat, 30 Jun 2001 20:47:02 +0100, you wrote: >I'm trying to work with Zope's ZCatalog in a Product >coded in python. Can anyone give some intro or point >to some links with info in this subject. There is a ZCatalog tutorial on http://www.zope.org/Documentation/How-To/ZCatalogTutorial/ The ZCatalog class is documented in the API Reference on http://www.zope.org/Members/michel/ZB/AppendixB.dtml Perhaps these are useful examples: http://www.zope.org/Members/Bill/Products/KnowledgeKit http://www.zope.org/Members/NIP/ZMailIn I found these using the search engine and I didn't check if they even use ZCatalog. Here is some python coding that shows how to use the catalog class outside of Zope: http://www.zope.org/Members/kelcmab3/catalog_out_of_zope This is a message with some code snippets from someone who tried to do the same: http://lists.zope.org/pipermail/zope/2000-April/023705.html Regards, René Pijlman ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Speed up the learning curve
[Clear error message when method in Python-based product has no doc string] > Doesn't it do precisely this when you run Zope in debug mode? I don't know, you may be right. I'll look into that. Thanks. But still, catching errors is not the same as debugging. I think Zope will be user friendlier when it gives a better error message directly. Coincidentally, I just received this Alertbox: "Established wisdom holds that good error messages are polite, precise, and constructive. The Web brings a few new guidelines: Make error messages clearly visible, reduce the work required to fix the problem, and educate users along the way." http://www.useit.com/alertbox/20010624.html This is good reading for zope-dev's :-) It contains an interesting idea with respect to the learning curve: "Users read system documentation only when they are in trouble (that's the Second Law). They are particularly attentive when they want to recover from an error. Given this, you can use error messages as an educational resource to impart a small amount of knowledge to users. Of course, error messages should be brief and to the point, as should all Web content. However, error messages can still teach users a bit about how the system works and give them information they need to use it better. To further that end, the Web's underlying technology makes another guideline possible: Hypertext links can be used to connect a concise error message to a page with additional background material or an explanation of the problem. (Don't overdo this, though.) " He's right. It really would have helped if the Zope error message linked to a page explaining the error message, listing possible causes and advising to run Zope in debug mode. Would it be possible to link Zope error messages to a website (with a unique page for every error)? Maintaining the documentation per error on this website could very well be a community effort of course. Regards, Rene Pijlman ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Speed up the learning curve
A suggestion to cut the Zope learning curve down by half a day... When the programmer forgets the docstring in a method of a Python-based product, instead of saying "Sorry, the requested resource does not exist." Zope could say: "Sorry, this method has no docstring." Yes, I know this behaviour is well-documented. But the message gives no clue to lead the unwary newbie from the error to the documentation. There are so many useful things I could have done in this half day :-/ Regards, René Pijlman ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
