[Zope-dev] Re: TALES idea: tuple unpacking
Evan Simpson wrote: OK, I've checked in a sample implementation on evan-pathprefix-branch. It allows for registering prefixes with: from Products.PageTemplates.PathPrefixes import registerSubPathPrefix registerSubPathPrefix('call', call_compiler, call_handler) How would this interact with the Adapters stuff implements in Zope 3's TALES? I'm pretty sure the implementation there could be used to make this happen, if it was backported to Zope 2's TALES... cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: TALES idea: tuple unpacking
Shane Hathaway wrote: Guys, that line of thinking is a distraction. ZPT authors ought to learn Python. I dunno about that, I would really like to see simple ZPT require no understanding of python... language again. If DTML used TALES expressions, it would be just as clean as ZPT. I actually agree with that, but due to the likelyhood of that happening being so small, and the fact that backwards compatability will mean that the throat-slittingly bad stuff that happened as a result of DTML being used to do logic, and the bulk of really evil example stuff out there, I stick with my view that 'DTML sux'... Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: TALES idea: tuple unpacking
Jim Penny wrote: Ahh, OK. The damned here/context semantic trap again. It is too late to revisit, it is a done deed, it was a really good idea to call the concept context, self, and here, depending on what kind of object you are using, etc. But here suggests container more strongly to my mind than container does! So, I try never to use it. I believe 'here' is gone in Zope 3. You're only likely to see 'self' if writing code on the filesystem. And we're left with 'context' and 'container', which is pretty clear :-) cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
Andrew Sydelko wrote: I've seen no problems with imports. And if anything, the cache implementation in the ZODB3.1.2 version of ZEO made a remarkable performance difference. ... as compared with earlier versions or later versions? I hope it's getting faster, not slower. :-) Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
On Thu, 31 Jul 2003 8:49am, Shane Hathaway wrote: Andrew Sydelko wrote: I've seen no problems with imports. And if anything, the cache implementation in the ZODB3.1.2 version of ZEO made a remarkable performance difference. ... as compared with earlier versions or later versions? I hope it's getting faster, not slower. It's faster especially compared to ZEO 1.x, but also compared to earlier versions of ZEO 2.x/ZEO from ZODB3.1.x. At one point, changes were made to the initial cache invalidation check that caused ZEO startup time to become significantly faster. Before this change the ZEO client would take more than a minute to start (with a cache_size of 200MB). We've not tried ZEO from ZODB3.2.x yet. --andy. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
Andrew Sydelko wrote: It's faster especially compared to ZEO 1.x, but also compared to earlier versions of ZEO 2.x/ZEO from ZODB3.1.x. At one point, changes were made to the initial cache invalidation check that caused ZEO startup time to become significantly faster. Before this change the ZEO client would take more than a minute to start (with a cache_size of 200MB). We've not tried ZEO from ZODB3.2.x yet. Oh, right. I was concerned for a moment that a minor change in ZEO 3.2 had slowed it down somehow. But you weren't talking about that. Whew. Jim and PythonLabs put a bunch of work into optimizing ZEO cache validation earlier this year, and now it's quite speedy. Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] NOTICE: Final content migration and transition to new zope.org begins today!
Hi all - sorry for the wide cross-posting, but I want to be sure that the word gets out. Starting today, we will be starting the transition of zope.org to a new look and a new platform. We plan to do the final content migration later today, so if you are a frequent content contributor to zope.org, you may want to hold off on new additions until the new site goes live (expected to be Friday). I've put a prominent notice on the current zope.org homepage with the same info. Thanks, and we'll see you on Friday with a new zope.org! Brian Lloyd[EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
On Thu, Jul 31, 2003 at 10:06:08AM -0400, Shane Hathaway wrote: Jim and PythonLabs put a bunch of work into optimizing ZEO cache validation earlier this year, and now it's quite speedy. Which reminds me... Is it expected that ZEO can take quite a while to show a new object on all clients? With zope 2.6.2b3, ZEO 2.0.2, I can reliably get this behavior: 1) browser 1 looking at foofolder on client 1 adds a new object /foofolder/bar. 2) browser 2 on client 2 visits /foofolder/bar. Not found. 3) browser 2 on client 2 flushes the browser cache, quits / restarts the browser, etc. /foofolder/bar again. Still not found. 3.5) Repeat step 3 intermittently for an hour (!). Not found. 4) client 2 is restarted. Browser 2 refreshes and immediately gets the expected object bar. This is clearly problematic. At what point is client 2 supposed to see the new object?? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's SADIST ITE! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO clientdeath.
Paul Winkler wrote: Which reminds me... Is it expected that ZEO can take quite a while to show a new object on all clients? With zope 2.6.2b3, ZEO 2.0.2, I can reliably get this behavior: 1) browser 1 looking at foofolder on client 1 adds a new object /foofolder/bar. 2) browser 2 on client 2 visits /foofolder/bar. Not found. 3) browser 2 on client 2 flushes the browser cache, quits / restarts the browser, etc. /foofolder/bar again. Still not found. 3.5) Repeat step 3 intermittently for an hour (!). Not found. 4) client 2 is restarted. Browser 2 refreshes and immediately gets the expected object bar. This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] A First Look at Zope3
I checked out Zope3 from CVS yesterday and had a go at it for the first time. Granted that it is a work in progress, I did have a few comments from a user's (rather than a developer's) perspective. The API exposed to DTML and ZPT seems very sparse (compared to Zope2) at this stage. Is this the case or am I missing something? As far as I can tell there is as yet no way to even get the name of an object for doing things like the old dtml-var title_or_id. (I have figured out how to add to the API for any particular class in the source code.) About the new look to adding objects in a folder -- I see the point of going to a list of contents with a text input to assign a name (so you can see what names are already in use), but I see one problems. The text input appears at the top of the list and the button to commit the change is at the bottom of the list. This will become more inconvenient as a container's list of contents grows. Perhaps the buttons should always be near the text input. Chris Gray ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote: This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) OK... is this a known bug? Is it a bug in ZEO or Zope or what? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's MAFIOSO LETTUCE-WAVER ! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A First Look at Zope3
Chris Gray writes: I checked out Zope3 from CVS yesterday and had a go at it for the first time. Granted that it is a work in progress, I did have a few comments from a user's (rather than a developer's) perspective. Thanks for taking the time to look at Zope 3! We definately appreciate comments from users and potential users. About the new look to adding objects in a folder -- I see the point of going to a list of contents with a text input to assign a name (so you can see what names are already in use), This can vary based on the type of object and how it's been configured. but I see one problems. The text input appears at the top of the list and the button to commit the change is at the bottom of the list. This will become more inconvenient as a container's list of contents grows. Perhaps the buttons should always be near the text input. That's a good idea, and very reasonable. I will take this opportunity to note that simply pressing Enter (or Return, depending on your keyboard!) will submit the form as well. There is a zope3-dev list available that specifically deals with Zope 3; sending your comments and observations there will reach more of the active Zope 3 developers. -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO clientdeath.
Paul Winkler wrote: On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote: This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) OK... is this a known bug? Is it a bug in ZEO or Zope or what? I've seen bugs like this before. It's very likely a bug in ZEO. Lowering the ZEO log filter level might help you see what's going on. I think setting EVENT_LOG_LEVEL=-300 will do that. Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: TALES idea: tuple unpacking
Chris Withers wrote: How would this interact with the Adapters stuff implements in Zope 3's TALES? It wouldn't -- this is a Zope 2 implementation. OK, I know what you mean, but I don't know enough about the Zope 3 implementation to make an informed response. Wouldn't Zope 2's lack of the whole component framework make this really hard? Cheers, Evan @ 4-am ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A First Look at Zope3
On Thu, 31 Jul 2003, Fred L. Drake, Jr. wrote: Chris Gray writes: but I see one problems. The text input appears at the top of the list and the button to commit the change is at the bottom of the list. This will become more inconvenient as a container's list of contents grows. Perhaps the buttons should always be near the text input. That's a good idea, and very reasonable. I will take this opportunity to note that simply pressing Enter (or Return, depending on your keyboard!) will submit the form as well. Yep. I had noticed that, and it is helpful. There is a zope3-dev list available that specifically deals with Zope 3; sending your comments and observations there will reach more of the active Zope 3 developers. Thanks. I'll move it over there. Chris Gray ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )