fwiw, Simon Eisenmann checked in a SessionStorage product into the
collective which does much the same. released under the zpl
http://cvs.sourceforge.net/viewcvs.py/collective/SessionCrumbler/
-kapil
___
Zope-Dev maillist - [EMAIL PROTECTED]
On Mon, 2004-04-12 at 18:03, [EMAIL PROTECTED] wrote:
G'Day,
Well, step one is done ... I now have Zope + Ape using Subversion as it's
filesystem !!
cool!
This is step one because, as Shawn suggested (Thanks for the pointer, that's
what I needed!), this simply means that Zope uses SVN
Hi all,
I've read your discussion about version control, it seems a cool thing you
guys making good progress. Btw, can I ask is the Ape using Subversion in Zope
stable? how able CMF stuff? I wanna make/find a document management system
which can provide some kinda version control in Plone.
From: Shane Hathaway [EMAIL PROTECTED]
Making cookie authentication secure is surprisingly difficult, and you've
barely taken one step. I don't want CookieCrumbler to go in this
direction at all. A much more fruitful endeavor would be to simply add
digest authentication support to Zope's
What's the correct ZPT syntax for PlacelessTranslationService?
I tried this:
b i18n:translate= i18n:domain=ibc i18n:target=string:czGood
morning/b
This gets rendered into: bGood morning/b
No translation, although I do have an entry for 'Good morning' in my .po
file under an 'ibc' domain.
On 12 Apr 2004 at 18:03, [EMAIL PROTECTED] wrote:
Anyways, I'm just rambling by now ... Comments, thoughts and constructive
criticism welcome !
This sounds wonderful!
Regarding versions. Perhap you can have a control panel setting that selects the
branch to publish by default. The ZMI
I would like to see the following functionality when it comes to unit
testing:
1. An easy consistent way to run ONE unit test, no matter if it's made for
Zope, or CMF, and no matter it it's done with straight unittest or
ZopeTestCase.
2. An easy and consistent way to run all unit test in a
Zope 2 has a package named Zope. Zope 3 has a package named zope.
Starting with Zope 2.8, parts of Zope 3 will be included in Zope 2.
As things stand, this will require having both Zope and zope packages.
Python can handle this fine, however, it will require putting the packages
in separate
+1
It looks like in the Zope 2 trunk, there are only a very few places that
rely on import Zope or from Zope import.
It looks like it would be possible to change the name of the Zope
package in Zope 2 to zope2 or something without a tremendous amount of
work. And as long as a module alias was
On Tue, 13 Apr 2004, Tres Seaver wrote:
Given that you trust yourself ;), you can add a security context from
within the second thread; you could pass the user ID to the thread via
one of several forms of currying, e.g. via instance variables::
I'm not sure if I trust myself in real
Hello,
I was wondering if someone on this list could point me in the direction
of an appropriate place to post Zope job openings. I am looking for an
audience well-versed in Zope. Thanks for any guidance!
-Paul Brinich
___
Zope-Dev maillist -
On Tuesday 13 April 2004 01:44 pm, Paul Edward Brinich wrote:
I was wondering if someone on this list could point me in the direction
of an appropriate place to post Zope job openings. I am looking for an
audience well-versed in Zope. Thanks for any guidance!
There's the Python Job Board:
zLOG is dead
The zLOG package used for logging throughout ZODB, ZEO, and Zope 2 has
been declared obsolete. All logging for Zope products will use the
logging package from Python's standard library.
The zLOG package still exists in Zope 2 and the separate package for
Milos Prudek wrote:
What's the correct ZPT syntax for PlacelessTranslationService?
PTS is just a translation service for ZPT. It doesn't add any
functionality to ZPT.
I tried this:
b i18n:translate= i18n:domain=ibc i18n:target=string:czGood
morning/b
This gets rendered into: bGood morning/b
Hello,
Hmmm, well it's as stable as Ape and Subversion are respectively :)
I wouldn't call it stable no, it's something I did over the long week-end we
just had, and that's about it :)
Ape is at 0.8 and therefore becoming quite mature, I'd have to let others
speak as to it stability however ...
Brad,
About the branch thing ... That's basically the idea!
The bigger problem here is how to manage this both internally and from a
user/administrator perspective.
This paradigm only really makes sense in the CMF world anyways, and I want
to focus on basic Zope before moving up to the extra
Shane,
Thanks for the extra tips, I'll check out those interfaces! I'm also getting
up to speed on the whole mapper concept, where the work regarding properties
handling seems to be ?
I've done some reading, and I need to do some more, but I'll get there :)
As for the seperation of code ... I
Hi J.F,
Thanks for your comments first. I understand more about the process of SVN in
zope now. I am very eager to have/make a document management system with good
version ctrl in Plone. Some products like Silva has versions but it's just
not exactly what we need.
Wish you have a good
[EMAIL PROTECTED] wrote:
Brad,
About the branch thing ... That's basically the idea!
The bigger problem here is how to manage this both internally and from a
user/administrator perspective.
This paradigm only really makes sense in the CMF world anyways, and I want
to focus on basic Zope before
Toby Gustafson wrote:
Your code below did not work for me because I could not find the
newSecurityContext method. However, I was able to use the
SecurityManagement.newSecurityManager instead, and that worked great.
Thanks for pointing me in the right direction.
Great! Sorry for leaving off the
Chris McDonough wrote:
+1
It looks like in the Zope 2 trunk, there are only a very few places that
rely on import Zope or from Zope import.
It looks like it would be possible to change the name of the Zope
package in Zope 2 to zope2 or something without a tremendous amount of
work. And as long
On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
snip
Of course, having two packages with names differing only in case is a
bit ugly.
Do we want to consider renaming one or both of these packages
to avoid the conflict?
-1 to renaming 'Zope'; the amount of third-party code which we
On Tue, 13 Apr 2004 [EMAIL PROTECTED] wrote:
Thanks for the extra tips, I'll check out those interfaces! I'm also getting
up to speed on the whole mapper concept, where the work regarding properties
handling seems to be ?
Ape supports both annotations and Zope properties. Annotations are
Stephan Richter wrote:
On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
snip
Of course, having two packages with names differing only in case is a
bit ugly.
Do we want to consider renaming one or both of these packages
to avoid the conflict?
-1 to renaming 'Zope'; the amount of third-party
Jim Fulton noted:
Of course, having two packages with names differing only in case is a
bit ugly.
Do we want to consider renaming one or both of these packages
to avoid the conflict?
A bit ugly, but I can live with it.
On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
-1 to renaming
Fred Drake wrote:
Jim Fulton noted:
Of course, having two packages with names differing only in case is a
bit ugly.
Do we want to consider renaming one or both of these packages
to avoid the conflict?
A bit ugly, but I can live with it.
On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
-1
+1
What is the recommend way to migrate existing code?
I assume using:
import logging
logger = logging.getLogger(loggername).
When I look through the Zope HEAD code then you are using e.g.
'zodb.conn' or 'zodb.storage' but also 'Zope' as loggername. Do we
have to agree on some common usage of
27 matches
Mail list logo
