On Monday 02 April 2007 18:58, Maciej Wisniowski wrote:
> > I was thinking of that...
> > How would you do that? Do you know formulator enough to say?
>
> I don't know your use case good enough. Is this just changing
> attributes of formulator fields?
Just asking :)
> > Put the whole thing in th
> EM gives you no security restrictions in comparision to Script Python.
I should rather say that it gives you less restrictions: access to
all python modules etc.
--
Maciej Wisniowski
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/lis
> I was thinking of that...
> How would you do that? Do you know formulator enough to say?
I don't know your use case good enough. Is this just changing
attributes of formulator fields?
> Put the whole thing in the EM, or something simpler?
> An EM I could just hand off the field object to, to get
On Monday 02 April 2007 17:51, Maciej Wisniowski wrote:
> > What to do?
> >
> > I guess some developer has worked hard to prevent me from doing just this
> > at some point, but why? Do I need to write a product to do it?
> > Is anyone at all using this crazy development model where "semi trusted
>
> What to do?
>
> I guess some developer has worked hard to prevent me from doing just this at
> some point, but why? Do I need to write a product to do it?
> Is anyone at all using this crazy development model where "semi trusted
> users"
> do stuff in the ZMI???
> But I digress..
>
> If an
Hi.
Trying to change various properties of a few hundred formulator fields
programmatically.
For example assigning to field.values['required'] = False.
This seemed to work, but of course was not persisted, and disappeared
gradualy. Quite magical to see :)
Tried to take a copy of values and "ov
