Jim Fulton wrote:
Historically, we've had Packages, Products, Packages3 and Products3
directories in the CBS repository. I wonder of we need these going
forward. Perhaps we should just have top-level projct directories
in the new subversion repository.
+1
Philipp
While we're all waiting for Zope 3 and Plone 3, I'd like to know what the
standard practice way of using Unicode with Zope 2. In particular, we'd
like to store all text as Unicode in the ZODB, and have Zope do the
encoding/decoding as automatically and transparently as possible.
We've been using
Jim Fulton wrote:
[decouple interface implementation]
*falls into a dead faint* *wakes up and starts bouncing around*
*Loud cheering!*
Awesome, thanks, Jim! A good start of my working week, too.
*cough* *regains composure* *ahum*
+1
Regards,
Martijn
On Monday 26 April 2004 09:27, Bjorn Stabell wrote:
While we're all waiting for Zope 3 and Plone 3, I'd like to know what the
standard practice way of using Unicode with Zope 2. In particular, we'd
like to store all text as Unicode in the ZODB, and have Zope do the
encoding/decoding as
Hi Bjorn,
I always believed that unicode and utf-8 were same encoding, but reading
you let me think i was wrong.
Can you tell me what the difference is between unicode and utf-8 ?
Bjorn Stabell wrote:
While we're all waiting for Zope 3 and Plone 3, I'd like to know what the
standard practice
--On Montag, 26. April 2004 10:53 Uhr +0200 David Convent
[EMAIL PROTECTED] wrote:
I always believed that unicode and utf-8 were same encoding, but
reading you let me think i was wrong.
Can you tell me what the difference is between unicode and utf-8 ?
Andreas Jung wrote:
Unicode is
Jim Fulton wrote:
Historically, we've had Packages, Products, Packages3 and Products3
directories in the CBS repository. I wonder of we need these going
forward. Perhaps we should just have top-level projct directories
in the new subversion repository.
I think having a distinction between Zope 2
On Sunday 25 April 2004 06:57 am, Jim Fulton wrote:
If we drop the requirement to make the interfaces interoperate (e.g.
extend one another, or be used in the same declarations), then, with a small change
that
Martijn has suggested, we can use zope.interface in Zope 2 without any other
Does anyone have the source code to the Addressit
sample program found in the Zope Bible? If not all
of it, I'm mainly looking for the Addressit.py file.
Thanks!
__
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25ยข
[Max M, tests a zip file of .pyd files in Zope3, on Windows]
I finally got around to testing this, and it works *exactly* as I
hoped. I downloaded Z3 from CVS, and Tim's zip file.
I unpacked the zip file into the Z3 directory, and it started the
first time.
Yippee! That's what I expected,
Maik Jablonski wrote:
Sounds cool... I'm not sure if it's easy as you describe, but I hope so...:)
Basically you just grep for URL1 in all dtml files, anywhere you see
dtml-URL1; or dtml-var URL1 html_quote and change it to
dtml-var REQUEST.URL1 html_quote IIRC REQUEST is safe to use.
The
Martijn Faassen wrote:
Dieter Maurer wrote:
Martijn Faassen wrote at 2004-4-24 22:49 +0200:
...
In practice right now the picture is 'Use all of the CMF or none of it'.
No, not really...
We use SkinsTool, ActionsTool and DCWorkflow a lot,
MembershipTool sometimes and most other tools not
Tres Seaver wrote at 2004-4-26 11:46 -0400:
Martijn Faassen wrote:
Dieter Maurer wrote:
...
We use SkinsTool, ActionsTool and DCWorkflow a lot,
MembershipTool sometimes and most other tools not at all.
Okay, point taken. :)
How much do the tools listed interdepend on each other?
Chris Withers wrote at 2004-4-25 18:50 +0100:
When I click on the Advanced tab of one of my ZSQL Methods, I see this:
Traceback (innermost last):
...
- __traceback_info__: XXdF
Module ZODB.Connection, line 149, in __getitem__
- __traceback_info__: ('\x00\x00\x00\x00\x00\x08dF',
I'm working on the cvs to subversion conversion for the ZODB, Zope 2, and
Zope 3 projects. I'm currently doing the conversion of the full history with
tags and branches. This is taking a long time and creating a huge
repository, which is OK, but, do we really need that much history?
I see 3
On Mon, 2004-04-26 at 15:23, Jim Fulton wrote:
2. Convert the mainline history, but leave off the branches.
Would this mean we'd lose the log messages too? If so -1 because often
merge messages aren't very helpful. merged foo-bar-branch to head
would suck if you couldn't at least see the log
On Monday 26 April 2004 03:23 pm, Jim Fulton wrote:
2. Convert the mainline history, but leave off the branches.
This sounds good to me.
-Fred
--
Fred L. Drake, Jr. fred at zope.com
PythonLabs at Zope Corporation
___
Zope-Dev maillist -
The standard subversion repository layout is by project:
proj1
/trunk
/branches
/br1
/br2
...
/tags
/tag1
/tag2
...
proj2
/trunk
/branches
/br1
Barry Warsaw wrote:
On Mon, 2004-04-26 at 15:23, Jim Fulton wrote:
2. Convert the mainline history, but leave off the branches.
Would this mean we'd lose the log messages too?
Yes, you'd lose the branch log messages.
If so -1 because often
merge messages aren't very helpful. merged
Jim Fulton wrote:
Barry Warsaw wrote:
On Mon, 2004-04-26 at 15:23, Jim Fulton wrote:
2. Convert the mainline history, but leave off the branches.
Would this mean we'd lose the log messages too?
Yes, you'd lose the branch log messages.
If so -1 because often
merge messages aren't very
On Mon, 2004-04-26 at 15:42, Jim Fulton wrote:
The reason that I hate merge messages like this is that I find it
very difficult to find the branch checkin messages in thye log. It's
possible, but so difficult that I generally would rather not
bother.
I agree, but history is history, so we
On Mon, 2004-04-26 at 15:48, Tim Peters wrote:
[Jim]
I read some subversion docs over the weekend, and so am sufficiently
prepared to live with the oddities of a standard subversion layout. I
think that if you make a non-standard layout, then everyone coming to, or
going from, Zope from/to
Barry Warsaw wrote:
On Mon, 2004-04-26 at 15:23, Jim Fulton wrote:
2. Convert the mainline history, but leave off the branches.
Would this mean we'd lose the log messages too? If so -1 because often
merge messages aren't very helpful. merged foo-bar-branch to head
would suck if you couldn't
Barry Warsaw wrote:
On Mon, 2004-04-26 at 15:42, Jim Fulton wrote:
The reason that I hate merge messages like this is that I find it
very difficult to find the branch checkin messages in thye log. It's
possible, but so difficult that I generally would rather not
bother.
I agree, but history is
On Mon, Apr 26, 2004 at 07:47:39PM +0200, Dieter Maurer wrote:
Our minimal tool usage is probably: Actions, Membership,
Skins, Types, Workflow.
I'm curious... do you use these with sites that are not
in any other way based on CMFCore/CMFDefault ?
--
Paul Winkler
http://www.slinkp.com
Look!
Tim Peters wrote:
I read some subversion docs over the weekend, and so am sufficiently
prepared to live with the oddities of a standard subversion layout. I
think that if you make a non-standard layout, then everyone coming to, or
going from, Zope from/to other subversion projects will be forever
[Chris McDonough]
...
- The ZODBMountPoint product relies on a method of Connection objects
named _getMountedConnection, which apparently no longer exists.
Connection objects never had such a method, but they still do wink.
This breaks any mounted databases (which breaks dbtab, which breaks
Bjorn Stabell wrote:
Formulator:
* gets charset from manage_page_charset (same as ZMI), but can be overridden
* stores field values as encoded text (not Unicode), but lets you specify
which encoding to use
(confusingly calls this unicode mode)
* messages are stored as UTF-8 (hardcoded)
While
David Convent wrote:
Hi Bjorn,
I always believed that unicode and utf-8 were same encoding, but reading
you let me think i was wrong.
Can you tell me what the difference is between unicode and utf-8 ?
Unicode should not be seen as an encoding as such. While Python
internally uses an encoding
On Mon, 2004-04-26 at 18:06, Tim Peters wrote:
Connection objects never had such a method, but they still do wink.
Ya, I figured this out later. ;-)
This breaks any mounted databases (which breaks dbtab, which breaks
sessions, which breaks lots of other things). Hopefully this is
simple
[Tim Peters]
...
IOW, the existing subversion docs cover the standard layout quite
well. If we do something unique, I'm afraid it becomes another piece
of folklore that will be impossible to guess and difficult to find
out about.
[Martijn Faassen]
I don't know much about subversion, but
On 11/03/2004, at 7:25 PM, Chris McDonough wrote:
On Wed, 2004-03-10 at 23:14, michael wrote:
Thanks for your excellent isolation here.
I don't get a KeyError thrown until *after* at least one rendering of
standard_error_message that includes an access to a session variable.
And I'm only
On Mon, 2004-04-26 at 15:48, Tim Peters wrote:
[Jim]
The standard subversion repository layout is by project:
proj1
/trunk
/branches
/br1
/br2
...
/tags
/tag1
/tag2
Hi Syver,
Please add this issue to the Collector, including the test (prefereably
without the twisted bits)
On Thu, 2004-04-22 at 12:57, Syver Enstad wrote:
[...]
I have a strange case here with ReadConflictErrors. I don't know if
this is covered already but anyway. I am using ZODB 3.2 so
None of the above components handles Unicode in this way,
but it seems to be how the Unicode support in Zope 2 was meant to be
used.
Martijn wrote:
You're actually wrong about Formulator. :)
Apologies. We were using older versions of Formulator before, and I was
just doing code inspection
[Kapil Thangavelu]
...
I like the layouts Jim's presented (specifically #2 of 3), i think when
considering the subversion docs, the important distinctions are made
between the directories used for branches and tags, as long as that
information is clearly communicated the semantics are exactly
On Mon, 2004-04-26 at 22:30, Tim Peters wrote:
[Kapil Thangavelu]
...
I like the layouts Jim's presented (specifically #2 of 3), i think when
considering the subversion docs, the important distinctions are made
between the directories used for branches and tags, as long as that
37 matches
Mail list logo
