On Tue, 9 Apr 2002 10:57:04 -0400, "Brian Lloyd" <[EMAIL PROTECTED]>
wrote:
>> IMO, this comes at this at the wrong direction.
>>
>> Objects should not decide whether they can be added to a given folder,
>> the folder should be the one that makes that decision.
Zope can already do that. Check
Brian Lloyd wrote:
>
> I think (correct me though, if I'm wrong!) that Toby
> actually implemented the suggestion that Jim made on
> the comments page of the proposal (add a filter to the
> meta type info, allowing products to do this without
> killing performance).
...but hasn't this problem al
After reading the discussion page I feel a bit more comfortable with it.
I do see an undesireable increase in the entropy of the ui, however.
This could be offset by careful use of this feature, of course. In fact
good use of it could reduce some of the clutter in the add list. For
instance, s
Toby Dickenson wrote:
> (Ive CCed everyone who has commented on the proposal; I hope thats OK)
Could everyone stick to zope-dev only? One copy of each email is enough ;)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listi
> IMO, this comes at this at the wrong direction.
>
> Objects should not decide whether they can be added to a given folder,
> the folder should be the one that makes that decision.
>
> It gives me the heebie geebies to think that every time the add list is
> rendered, a whole slew of class me
IMO, this comes at this at the wrong direction.
Objects should not decide whether they can be added to a given folder,
the folder should be the one that makes that decision.
It gives me the heebie geebies to think that every time the add list is
rendered, a whole slew of class methods are pote
Re: http://dev.zope.org/Wikis/DevSite/Proposals/RestrictedCreation
This proposal from Itamar has been up on dev.zope.org for a while, proposing
a way for a registered type to control whether or not it can be added to a
container, or a per-container basis.
I now have an implementation of this i
