Chris Withers wrote:
Tres Seaver wrote:
who's the CTO?
Jim is.
Okay, I get the joke now :-)
* "persistent" references are effectively required to be immortal:
it is _mandated_ that one be able to stringify the IOR, copy it
to a piece of paper, put

At the request of a Zopista who found my earlier work toward Zope-CORBA
integration,
I have created a fishbowl proposal at:
http://dev.zope.org/Wikis/DevSite/Proposals/CorbaClientIntegration
Tres.
___
Zope-Dev maillist - [EMAIL PROTECTED]

ython. Are you using Jeff Rush's binaries? I think you need to
check out his source distribution (RPM, no less!), at:
http://www.os2warp.org/%7Ejrush/python_os2/files.html
Best,
Tres.
--
===
Tres Seaver

I was just able to scratch a *really* big itch: I used my FSDump
product,
plus 'diff -r -u', to generate a diff between the versions of DemoPortal
(the "through-the-web" portion of the PTK) shipped with PTK 0.9.0 and
0.9.2:

I have just created a fishbowl proposal for hooking the creation
of new objects during HTTP/FTP PUT operations:
http://dev.zope.org/Wikis/DevSite/Proposals/HookablePUTCreation
Note that this proposal stems from my hack this weekend, which makes
it possible to create portal content via FTP; I

this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it
along with our marbles is another problem :)
Tres.
--
===
T

On Wed, 24 Jan 2001 [EMAIL PROTECTED] wrote:
Tres Seaver wrote:
Please post this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it
along with our marbles is another problem :)

e storages
(logically impossible); some "packless" storages are already in
play (maybe even near release), so the semantics you want may be
(soon) readily available by mounting a separate storage.
Tres.
--
===

On 12 Feb 2001, Erik Enge wrote:
[Tres Seaver]
| Please see:
|
| http://dev.zope.org/Projects/PTK
|
| for our work-in-progress.
Hey, looks like what I'm after. I can see that it's a work in
progress, so if you need any help, give me a shout. It didn't
say too much about

On Wed, 14 Feb 2001, Steve Alexander wrote:
Tres Seaver wrote:
...it is quite feasible to have one or more storages
inside your Zope ... often at a non-trivial time cost.
Where does the time cost come in? I've noticed a delay on first
mounting another storage, but I haven't looked

sible to create an additional ZEO client, which used the main
site's "sub-storage" as its own main storage; one would then be
able to pack it (I think), while leaving the main site running
(but more slowly during the pack).
Tres.
--
=====

technoligies for the
content owners; we spent a good deal of effoert on cleaning up FTP/WebDAV
for yesterday's CMF release, for instance.
Tres.
--
===
Tres Seaver[EMAIL PROTECTED]
Digital Creations Zope

in Zope3!), the library can just contain
'from realmodule import usefulFunction', and the template won't need
to change.
I would vote for having the bound library's names inserted into the
'template' TALES namespace, BTW.
Tres.
--
===
Tres

On Wed, 2003-09-10 at 23:46, Evan Simpson wrote:
Tres Seaver wrote:
Actually, the restricted case is the one which has the real win; the
free-floating library is pretty, but not semanticaally needed. An
added argument: a ZPT with its own private library becomes, in effect,
a Zope3 view

On Wed, 2003-09-17 at 19:10, Fred Yankowski wrote:
On Wed, Sep 17, 2003 at 06:25:47PM -0400, Tres Seaver wrote:
I have wanted to add a binding to the TALES namespace to allow access to
the skin object for some time: the current values in the namespace
are:
'content' -- the skin

On Thu, 2003-09-25 at 06:41, Chris Withers wrote:
Tres Seaver wrote:
I have wanted to add a binding to the TALES namespace to allow access to
the skin object for some time: the current values in the namespace
are:
'content' -- the skin object's aq_parent
'view

deployed Zope 2.6.2 with Python 2.2.3 in production for clients
already; the garbage collection improvements in Python 2.2.3 were so
compelling that we couldn't reasonably roll them back to Python 2.1.3
after testing.
Tres.
--
===
Tres

) and then refreshes its parent window;
if the commit takes long enough (e.g., it hits a conflict), the parent
can end up showing the old data after the refresh.
Tres.
--
===
Tres Seaver[EMAIL PROTECTED]
Zope

class for all filesystem based look-alikes.
Subclasses of this class mimic ZODB based objects like Image and
I imagine making similar small changes to Archetypes won't be hard.
Tres.
--
===
Tres Seaver

'
and into a better top-level pacakge. People are beginning to use PTF
for ZMI, which shouldn't break in the absence of a product.
Tres.
--
===
Tres Seaver[EMAIL PROTECTED]
Zope Corporation Zope Dealers http

by adding 'global context' at the top.
Did you have a deeper reason behind the change than the collector issue?
If not, would you mind if we reverted, and updated the issue?
Tres.
--
===
Tres Seaver[EMAIL

;
- Bringing up several of our large customer-specific applications.
This testing *did* find several brown-bag issues, before the release,
which hadn't been caught be the unit tests.
Tres.
--
===
Tres Seaver

Jim Fulton wrote:
Tres Seaver wrote:
I will let Jim comment on your use case.
What use case? I missed it. Where is it?
Here is Stuart's original post:
This has the side effect of not passing the name attribute to
my security assertion methods registered via
ClassSecurityInfo.setDefaultAccess

one of the following roles:
['Manager']. Your roles in this context are ['Authenticated', 'Mitarbeiter'].
You need to update or remove VerboseSecurity (I don't think Shane has
released a 2.7 compatible version yet).
Tres.
--
===
Tres

Dieter Maurer wrote:
Tres Seaver wrote at 2004-1-23 17:04 -0500:
The script being called is invoked during a workflow transition, which
calls the script, passing a StateChangeInfo instance; the new code
tries to validate access to the SCI and pukes, badly, because the script
has proxy roles

you please re-tests with the head of the 2.6
branch? If your workflow scripts are still broken, would you please
open a collector issue?
Thanks!
Tres.
--
===
Tres Seaver[EMAIL PROTECTED]
Zope Corporation

portal_catalog;
set its start attribute to 'effective' and its stop attribute to
'expires'.
- Patch CMFCore/CatalogTool.py using the attached patch file (made
against the released 1.3 version).
Tres.
--
===
Tres Seaver

DateIndexes will ease most of your pain; using a DateRange index will
blow your socks off), it would be good to confirm that I'm right (or
not :) in public.
Tres.
--
===
Tres Seaver[EMAIL PROTECTED]
Zope

in advance,
Jason Spisak
Tres Seaver wrote:
Jason Spisak wrote:
Tres and Seb,
Got rid of all the date FieldIndexes and am reindexing the new
DateIndexes one at a time from the indexes tab, but I've hit a snag.
when I go to reindex 'expires' I get this error immediately:
Site error
This site