On Sun, 22 Apr 2007 10:02:25 -0400, Rocky <[EMAIL PROTECTED]> wrote:
On Apr 22, 11:45 am, Martin Aspeli <[EMAIL PROTECTED]> wrote:
So are we saying we need a bugfix/monkey patch to Five?
No.
By "not using five.lsm" I meant "don't do the automatic acquisition
wrapping".
Great. And I agre
On Thu, 19 Apr 2007 07:50:42 -0400, Wichert Akkerman <[EMAIL PROTECTED]>
wrote:
The tools/utilities/getToolByName debate seems to have petered out
without reaching a real consensus. Since I'm trying to get a next Plone
3 beta out this is becoming somewhat problematic for me, so I'm trying
to g
On Thu, 12 Apr 2007 06:16:23 -0400, yuppie <[EMAIL PROTECTED]>
wrote:
Hi!
Philipp von Weitershausen wrote:
yuppie wrote:
Kapil's also right when he says that utilities by principle are
context-less components.
By principle all Zope 3 code might depend on setSite to work as
expected. W
On Tue, 10 Apr 2007 09:09:27 -0400, Jens Vagelpohl <[EMAIL PROTECTED]>
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10 Apr 2007, at 10:30, yuppie wrote:
Currently non-five.lsm site managers don't work in CMF, see this thread:
http://mail.zope.org/pipermail/zope-cmf/2007-March/02
A few of us (Alec Mitchell, Godefroid Chapelle, Balazs Ree, Rocky Burt,
Daniel Nouri, Rob Miller, Vincenzo Di Somma, and myself) have been
discussing this in depth at the Sorrento Sprint. We've reached consensus
on how we hope to resolve the issues arising from the recent introduction
of five.loca
A few of us (Alec Mitchell, Godefroid Chapelle, Balazs Ree, Rocky Burt,
Daniel Nouri, Rob Miller, Vincenzo Di Somma, and myself) have been
discussing this in depth at the Sorrento Sprint. We've reached consensus
on how we hope to resolve the issues arising from the recent introduction
of fi
the gs representation can be whatever you want, registering an adapter
allows you to serialize content in whatever form is best for it.
contentsetup in plone svn uses marshall for example on at content, with
separate data file serialization for any file/image fields. for gs
default, dav was
hi folks,
in support of more advanced uses of workflow, such as instance specified
workflows, and non portal global policy settings, i was interested in
modifying the workflow tool to support delegation of interaction with
content objects to adapters for workflow chain lookup and workflow s
/note this is a resend original send failed because of attached script
which is now inlined.
the plone.org and collective cvs->svn migrations basically use cvs2svn
on a particular project subdirectory and then move the generated
branches/trunk/tags of the svn repo into an svn project subdirector