[What's this subject line to do with your question?] Sounds like an ideal use of TinyTables if there ever was one. I think performance will be excellent. The alternative, which is likely slightly faster but not quite as elegant in terms of object-orientational succinctness and flexibility, is to write an External Method which returns a Python dictionary of the values you need. Eg., def GetMySelectLists(): return { 'apples': 'oranges', 'pears': 'bananas', [... more items here ...] } -- Alexander Staubo http://www.mop.no/~alex/ "He could open a tin of sardines with his teeth, strike a Swan Vestas on his chin, rope steers, drive a steam locomotive and hum all the works of Gilbert and Sullivan without becoming confused or breaking down in tears." --Robert Rankin, _The Book of Ultimate Truths_
-----Original Message----- From: root@zope.codeit.com [mailto:root@zope.codeit.com]On Behalf Of Jason Sent: 14. juli 1999 00:11 To: zope@zope.org Subject: [Zope] Re: Zope digest, Vol 1 #186 - 49 msgs
Hey Zopesters,
I have large select lists that I need on my site and I was wondering if TinyTables is the best way to do an <!--#in--> tag insertion of all the possible values. It's not quite a uniqueValuesFor situation because there are some values which we don't want available. The list might be about 100-200 or so items long. Is that going to be to slow in a TinyTable?
All my best,
Jason Spisak webmaster@mtear.com
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )