Re: [Zope3-dev] status of zc.page?
Martijn Faassen wrote: Jim Fulton wrote: Martijn Faassen wrote: [snip] * the snapshot is probably aging as bugs get discovered and fixed in your repository. Could you perhaps update the snapshot? Sure. Looking forward to the update, though we haven't found bugs yet in our experiments so far. I'm note sure there have been changes since the last snapshot. Initial feedback: Overall: it's definitely an improvement above the ZCML directives! We often need to build template specifically, just calling widgets/foo/render inside our own template that's completely particular to that form. This worked well, until I had to figure out how to render an action. I finally accomplished it by using view/actions/form.action.name/render, where 'name' is a lowercased from the one you put in the decorator and what will also appear on the button. Hm. I'll look at this. This didn't feel ideal; the prefixing was hard to figure out initially (should at least be better documented), and basing the internal name on the displayed one doesn't feel right. I'll look at this and at the documentation. Actions have a number of issues and I'm not sure the doctests fully reflect them. I want to take a look at this and then provide a new snapshot. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] status of zc.page?
Jim Fulton wrote: Martijn Faassen wrote: [snip] * the snapshot is probably aging as bugs get discovered and fixed in your repository. Could you perhaps update the snapshot? Sure. Looking forward to the update, though we haven't found bugs yet in our experiments so far. Initial feedback: Overall: it's definitely an improvement above the ZCML directives! We often need to build template specifically, just calling widgets/foo/render inside our own template that's completely particular to that form. This worked well, until I had to figure out how to render an action. I finally accomplished it by using view/actions/form.action.name/render, where 'name' is a lowercased from the one you put in the decorator and what will also appear on the button. This didn't feel ideal; the prefixing was hard to figure out initially (should at least be better documented), and basing the internal name on the displayed one doesn't feel right. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] status of zc.page?
Jim Fulton wrote: Still, of course, for the bits we open source, I guess we are going to have to port back to 2.3. Martijn Faassen wrote: Well, there's no need if we just say that this bit requires a Zope 3.1 running Python 2.4; why create extra work for ourselves? +1 Since 3.1 will run on 2.4 anyway, and zc.page won't be in 3.1 we should just say that zc.page requires 2.4. If we get overwhelming interest in running it on 2.3, we (or a volunteer) will back port it. And as a side effect Martijn will get to use the decorators the right way. :) -- Benji York Sr. Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] status of zc.page?
Jim Fulton wrote: Martijn Faassen wrote: [snip] We have some concerns though: * the snapshot is probably aging as bugs get discovered and fixed in your repository. Could you perhaps update the snapshot? Sure. Okay, cool! * it requires Python 2.4.1. Zope 3.1 to my knowledge is targetting Python 2.3. It looks like it's fairly easy to rewrite the few decorators that are in the package itself so they work with Python 2.3 instead, but we don't want to maintain our own fork. Obviously we want to use this with Zope 3.1. Am I mistaken about the Python version targetted by Zope 3.1? No. It supports Python 2.4 though. Ah, I didn't realize that this was the case. We should make sure that's announced when the 3.1 release is done. > I'm rather confused that you're apparently using Python 2.4.1 for internal Zope 3 projects. Why? Python 2.4 makes some things more convenient. Sure, but I thought that Zope 3.1 only supported Python 2.3, not 2.4, so this was my first hint that Zope 3.1 actually is also aimed at supporting (but not requiring) Python 2.4. In partcicular, I really have come to like the new features in Zope 3.1 that let us declare adapted interfaces and to declare provided implemented interfaces for functions. The decorator syntax makes this more readable. Still, of course, for the bits we open source, I guess we are going to have to port back to 2.3. We're happy to do this if people start using zc.page. We've gotten almost no feedback up until now. Well, there's no need if we just say that this bit requires a Zope 3.1 running Python 2.4; why create extra work for ourselves? I just didn't realize that using Python 2.4 was possible or recommended, but since you're doing it on a project I guess there's no objection to doing so with our project either. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] status of zc.page?
Martijn Faassen wrote: Hi there, Since we keep running into snags and frustrations with the zope.app.form package, we're checking out zc.page and see whether it could help us any. We're going to try using it today. Great! We have some concerns though: * the snapshot is probably aging as bugs get discovered and fixed in your repository. Could you perhaps update the snapshot? Sure. * it requires Python 2.4.1. Zope 3.1 to my knowledge is targetting Python 2.3. It looks like it's fairly easy to rewrite the few decorators that are in the package itself so they work with Python 2.3 instead, but we don't want to maintain our own fork. Obviously we want to use this with Zope 3.1. Am I mistaken about the Python version targetted by Zope 3.1? No. It supports Python 2.4 though. > I'm rather confused that you're apparently using Python 2.4.1 for internal Zope 3 projects. Why? Python 2.4 makes some things more convenient. In partcicular, I really have come to like the new features in Zope 3.1 that let us declare adapted interfaces and to declare provided implemented interfaces for functions. The decorator syntax makes this more readable. Still, of course, for the bits we open source, I guess we are going to have to port back to 2.3. We're happy to do this if people start using zc.page. We've gotten almost no feedback up until now. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
