Hi!
Charlie Clark wrote:
> Am 09.12.2009, 19:22 Uhr, schrieb yuppie :
>> -1
>> I don't think a write-on-read solution is acceptable.
>
> Okay. How about on creation?
There are different ways to create type infos. I don't think the class
constructor should contain any magic that sets computed d
Am 09.12.2009, 19:22 Uhr, schrieb yuppie :
Hiya yuppie,
> -1
> I don't think a write-on-read solution is acceptable.
Okay. How about on creation?
>> 2) Uneditable TypeInfo method
>>
>> Apart from transparency I can't see any reason for making this value
>> editable so it could be implemented as
Hi!
Charlie Clark wrote:
> Am 02.12.2009, 21:04 Uhr, schrieb Charlie Clark :
>
>> I think that we could work with a sensible default which might be
>> overwritable in the aliases?
>
> I can think of two solutions here.
>
> 1) Sensible default:
>
> replace
>
> if self.add_view_expr:
Am 02.12.2009, 21:04 Uhr, schrieb Charlie Clark :
> I think that we could work with a sensible default which might be
> overwritable in the aliases?
I can think of two solutions here.
1) Sensible default:
replace
if self.add_view_expr:
lazy_map['url'] = self.add_view_expr
Am 09.12.2009, 15:10 Uhr, schrieb Jens Vagelpohl :
> For the "extends = src/Zope2/versions.cfg" line to work you must have a
> Zope 2 checkout in src/Zope2 *before* you attempt run the buildout.
> CMF.buildout does this using svn:externals, so you may not have those in
> your own buildout.
Hi Charlie,
> Is there an easy to way to setup a project buildout based
> on CMF? I've tried various combinations of the following:
>
> [buildout]
> extends =
> http://svn.zope.org/*checkout*/CMF.buildout/branches/zope212-cmf22/buildout.cfg
> versions = versions
> parts = parts
> eggs = eggs
Am 06.12.2009, 18:39 Uhr, schrieb Jens Vagelpohl :
> All done now:
> - release branches for the 2.2 release series are cut
> - the 2.2.0 beta release is tagged and published on PyPI
> - the convenience buildout branch[1] now uses the new CMF 2.2 branch
> The trunk (-> CMF 2.3) is free for new feat
On Dec 1, 2009, at 07:52 , Jens Vagelpohl wrote:
> Reminder: After this week (probably this coming Sunday) I plan on doing the
> first CMF 2.2 beta, and creating the 2.2 release branch.
All done now:
- release branches for the 2.2 release series are cut
- the 2.2.0 beta release is tagged an
Hi Charlie!
yuppie wrote:
> Charlie Clark wrote:
>> Am 02.12.2009, 20:51 Uhr, schrieb yuppie
>> :
>>> Using the class directive instead is just a workaround for a generic
>>> problem that needs a generic solution, not a new addView directive.
>> I have to agree with you on that. But the current
Hi Charlie!
Charlie Clark wrote:
> Am 02.12.2009, 20:51 Uhr, schrieb yuppie :
>
>> -1
>> The real issue here is the fact that the permission argument of the
>> adapter directive is not supported in Zope 2. Otherwise we could simply
>> use this:
>> > name="myproduct.content_type_fa
Am 02.12.2009, 20:51 Uhr, schrieb yuppie :
> -1
> The real issue here is the fact that the permission argument of the
> adapter directive is not supported in Zope 2. Otherwise we could simply
> use this:
> name="myproduct.content_type_factory"
> factory=".myproduct.MyAddV
Hi Charlie!
Charlie Clark wrote:
> Hooking everything together is, however, a bit clunky:
>
>name="myproduct.content_type_factory"
> factory=".myproduct.MyAddView"
> />
>
>
>permission="cmf.AddPortalContent"
>interface="zop
Am 01.12.2009, 07:52 Uhr, schrieb Jens Vagelpohl :
> Reminder: After this week (probably this coming Sunday) I plan on doing
> the first CMF 2.2 beta, and creating the 2.2 release branch.
My CSS stuff won't make it into the beta. I would like to contribute some
documentation on Yuppie's new a
Reminder: After this week (probably this coming Sunday) I plan on doing the
first CMF 2.2 beta, and creating the 2.2 release branch.
jens
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.lau
14 matches
Mail list logo
