[Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Philipp von Weitershausen
Looking for your comments at http://dev.zope.org/Zope3/SimplifySkinning. This is a follow-up proposal from http://www.zope.org/Collectors/Zope3-dev/444. This message was sent using IMP, the Internet Messaging Program.

[Zope3-dev] Re: RFC: undeprecate auto-message id translation

2005-12-07 Thread Philipp von Weitershausen
Florent Guillaume wrote: Martijn Faassen wrote: Zope 2.8 *is* actually interpolating and translating message ids correctly *without* i18n:translate already. I think that this is the same as Zope 3's (deprecated) behavior. The problem is when 'structure' is used in TALES. If this isn't

[Zope3-dev] Re: RFC: undeprecate auto-message id translation

2005-12-07 Thread Philipp von Weitershausen
Jim Fulton wrote: I still don't like the implicit translation of message ids, I thought like that, too. You really would want implicit translation of message ids, though, not because implicitness is the right choice here, but because of general separation of concerns. This is along the same

Re: [Zope3-dev] Twisted Publisher and Zope 2

2005-12-07 Thread Chris Withers
Jim Fulton wrote: The most important project here, IMO, is to rewire Zope 2 to use the Zope 3 publisher. And, of course, to update the Zope 3 publisher with features from the Zope 2 publisher that are missing from the Zope 3 publisher (e.g. streaming). +10 Please don't anyone write a new

Re: [Zope3-dev] Twisted Publisher and Zope 2

2005-12-07 Thread Stephan Richter
On Tuesday 06 December 2005 19:56, Jim Fulton wrote: The most important project here, IMO, is to rewire Zope 2 to use the Zope 3 publisher.  And, of course, to update the Zope 3 publisher with features from the Zope 2 publisher that are missing from the Zope 3 publisher (e.g. streaming). For

[Zope3-dev] RE: Zope3-dev Digest, Vol 29, Issue 14

2005-12-07 Thread Fabrice Monaco
Message: 1 Date: Tue, 06 Dec 2005 18:32:47 -0500 From: Benji York [EMAIL PROTECTED] Subject: Re: [Zope3-dev] Ajax in Zope 3 To: Tarek Ziad? [EMAIL PROTECTED] Cc: zope3-dev@zope.org \(E-mail\) zope3-dev@zope.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1;

[Zope3-dev] Re: RFC: undeprecate auto-message id translation

2005-12-07 Thread Martijn Faassen
Florent Guillaume wrote: [snip] I agree that the use case of having translations containing HTML is important, and thus that we'll have to make sure do_insertStructure_tal also does correct interpolation when faced with a MessageID. I now have a monkey patch that patches in a two line

Re: [Zope3-dev] Re: RFC: undeprecate auto-message id translation

2005-12-07 Thread Martijn Faassen
Philipp von Weitershausen wrote: Florent Guillaume wrote: [snip] I agree that the use case of having translations containing HTML is important, and thus that we'll have to make sure do_insertStructure_tal also does correct interpolation when faced with a MessageID. The Zope 3's

Re: [Zope3-dev] Twisted Publisher and Zope 2

2005-12-07 Thread Martijn Faassen
Chris Withers wrote: Jim Fulton wrote: The most important project here, IMO, is to rewire Zope 2 to use the Zope 3 publisher. And, of course, to update the Zope 3 publisher with features from the Zope 2 publisher that are missing from the Zope 3 publisher (e.g. streaming). +10 Please don't

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Martijn Faassen
Philipp von Weitershausen wrote: Looking for your comments at http://dev.zope.org/Zope3/SimplifySkinning. This is a follow-up proposal from http://www.zope.org/Collectors/Zope3-dev/444. I rather like having the *concept* skin to talk about. While implementation-wise things may become

Re: [Zope3-dev] xml import / export in z2 z3

2005-12-07 Thread Martijn Faassen
Jean-Marc Orliaguet wrote: I'm about to write an xml importer for importing simple data (properties, dictionaries). Exporting is easy, importing is trickier because a parser is required. Is there any prefered framework for doing such things in zope3 (zope2)? CMFSetup uses sax, GenericSetup

Re: [Zope3-dev] xml import / export in z2 z3

2005-12-07 Thread Jean-Marc Orliaguet
Martijn Faassen wrote: Andreas Jung wrote: I'm about to write an xml importer for importing simple data (properties, dictionaries). Exporting is easy, importing is trickier because a parser is required. Is there any prefered framework for doing such things in zope3 (zope2)? Sax or

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Philipp von Weitershausen
Stephan Richter wrote: Looking for your comments at http://dev.zope.org/Zope3/SimplifySkinning. This is a follow-up proposal from http://www.zope.org/Collectors/Zope3-dev/444. I was going to write a similar proposal for 3.3 as well. I think we should simply get rid of skins and pretend they

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Stephan Richter
On Wednesday 07 December 2005 09:47, Philipp von Weitershausen wrote: If I understand you correctly, you just propose to keep layers and get rid of skins while I roughly propose to do it the other way around. I really don't see a big difference :). The difference is in effort. :-) If we keep

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Philipp von Weitershausen
Stephan Richter wrote: On Wednesday 07 December 2005 09:47, Philipp von Weitershausen wrote: If I understand you correctly, you just propose to keep layers and get rid of skins while I roughly propose to do it the other way around. I really don't see a big difference :). The difference is

Re: [Zope3-dev] Twisted Publisher and Zope 2

2005-12-07 Thread Jim Fulton
Martijn Faassen wrote: Chris Withers wrote: Jim Fulton wrote: The most important project here, IMO, is to rewire Zope 2 to use the Zope 3 publisher. And, of course, to update the Zope 3 publisher with features from the Zope 2 publisher that are missing from the Zope 3 publisher (e.g.

Re: [Zope3-dev] Twisted Publisher and Zope 2

2005-12-07 Thread Stephan Richter
On Wednesday 07 December 2005 10:51, Martijn Faassen wrote: Agreed with Andreas. I also agree with Jim that it makes sense to be ambitious. I suspect we'll end up with a two-pronged approach -- introduce the Zope 3 publisher with as much backwards compatibility we can provide, but also make

[Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Derrick Hudson
On Wed, Dec 07, 2005 at 09:26:58AM +0530, baiju m wrote: | On 12/6/05, Jim Fulton [EMAIL PROTECTED] wrote: | The Zope 3 development team is proud to announce Zope 3.2.0 beta 1. | | Can anyone recommend the best method to install Zope 3.2 in Debian 3.1 (Sarge) | | Python version: | 1. Install

Re: [Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Craeg Strong
I am using FC4 and Python 2.4.1 comes built in. This is just a play/development machine, nothing needs to be airtight. Can anyone provide a summary of what is likely to go wrong using Zope 3.2b1 with Python 2.4.1 rather than the recommended/supported 2.4.2? I checked the release notes for python

Re: [Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Andreas Jung
--On 7. Dezember 2005 14:08:29 -0500 Craeg Strong [EMAIL PROTECTED] wrote: I am using FC4 and Python 2.4.1 comes built in. This is just a play/development machine, nothing needs to be airtight. Can anyone provide a summary of what is likely to go wrong using Zope 3.2b1 with Python 2.4.1

Re: [Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Craeg Strong
-- takes you two minutes I probably have about 6 or seven major packages added to python including 4suite, pyrex, pyxml, etc. etc. all of which must be rebuilt, re-patched, retargetted, etc. hence my question. (yes, I am a Lazy Programmer...) --Craeg Andreas Jung wrote: --On 7.

Re: [Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Tim Peters
-- takes you two minutes [Craeg Strong] I probably have about 6 or seven major packages added to python including 4suite, pyrex, pyxml, etc. etc. all of which must be rebuilt, re-patched, retargetted, etc. hence my question. (yes, I am a Lazy Programmer...) You shouldn't need to

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Dominik Huber
Phillip's Proposal: Furthermore, I propose to remove the |IDefaultLayer| interface. We've been using the |default| layer as a connotation of always being available unless overridden by a more specific layer. However, this does not apply all the time: When the |default| layer is not included in

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Dominik Huber
Martijn Faassen wrote: Philipp von Weitershausen wrote: Looking for your comments at http://dev.zope.org/Zope3/SimplifySkinning. This is a follow-up proposal from http://www.zope.org/Collectors/Zope3-dev/444. I rather like having the *concept* skin to talk about. While

Re: [Zope3-dev] Re: Zope 3.2.0 Beta 1 released

2005-12-07 Thread Craeg Strong
Maybe you're right. I can probably recursively copy all of the directories from site-packages/ in 2.4.1 to 2.4.2 Or I can stop being so lazy and reinstall them properly :-) I was mostly just wondering if there were any specific Zope or Twisted problems noted for 2.4.1 or the upgrade was for

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Stephan Richter
On Wednesday 07 December 2005 16:33, Dominik Huber wrote: Phillip's Proposal: Furthermore, I propose to remove the |IDefaultLayer| interface. We've been using the |default| layer as a connotation of always being available unless overridden by a more specific layer. However, this does not

Re: [Zope3-dev] RFC: Simplify Skinning

2005-12-07 Thread Philipp von Weitershausen
Stephan Richter wrote: On Wednesday 07 December 2005 16:33, Dominik Huber wrote: Phillip's Proposal: Furthermore, I propose to remove the |IDefaultLayer| interface. We've been using the |default| layer as a connotation of always being available unless overridden by a more specific layer.