On 6/19/07, Stephan Richter [EMAIL PROTECTED] wrote:
On Tuesday 19 June 2007 09:53, Jan-Wijbrand Kolman wrote:
Is there a way to overcome this? (or to put it differently, why is
my utility created when the action object is created and not just
before the actual registration?)
Unfortunately,
On Wednesday 14 March 2007 05:43, Daniel Nouri wrote:
Currently, when you have a condition on an action, and it is satisfied on
render time, you'll get a button. However, if you click that button and
the condition happens to be false in the subsequent request, the action
will not be executed,
On Wednesday 20 June 2007 04:14, Jan-Wijbrand Kolman wrote:
I had a quick look into this yesterdag. My (proably naive) idea was to
add an keyword argument to registerUtility telling that the component
is a factory and needs to be instantiated before actual registration.
No, that would be the
Am Montag, 18. Juni 2007 13:36 schrieb Brian Sutherland:
On Mon, Jun 18, 2007 at 07:57:10PM +1000, John Maddison wrote:
Hi all,
I've just started playing around with using z3c.layer to create
applications that don't use the ZMI at all. Everything is pretty
simple so far, except for one
Hi,
Is there a way to assign a skin/layer to a specific site? In my case I'd like
to have the rotterdam skin for the root folder, for root['mysite1'], I'd like
to have MySkin1, and for root['mysite2'] MySkin2.
Moreover I do not want to have the ++skin++ directive in the URL.
The only way I
On Wednesday 20 June 2007 13:55, Daniel Nouri wrote:
May I suggest that the fact that you wouldn't expect anything else is
because you know the implementation?
No, I just have written z3c.form and I implemented the same semantics there.
Simply because it makes sense to me.
I've been using my
Stephan Richter wrote:
On Wednesday 20 June 2007 13:55, Daniel Nouri wrote:
Isn't it reasonable to expect an action to
execute although it's not visible when the form is rendered again?
Nope. For me the condition is a condition of availability and not visibility.
That's exactly where I
