(Tested with
)
There are an awful lot of colons in there :-)
Indeed ...
Here's an off-the-wall idea:
This looks better as a tal:tag
Or, if you only use this kind of thing with tal:replace, tal:content and
tal:define.
Of course, none of this helps for tal:attributes.
If I understood
On Fri, Mar 07, 2003 at 08:56:59AM +1100, Adrian van den Dries wrote:
> (/me revisits LDAPUserFolder)
>
> Looks like the work is already done for you anyway: allowed() and
> friends check if the context has an attribute acl_satellite, and
> queries it for any additional roles, and it even keeps a
On March 5, Paul Winkler wrote:
> * more coupling
Yes.
> * performance hit
Yes.
> * one more detail to pay attention to
Yes.
> OTOH, doing the magic in user.allowed() would mean
> I'd only need one "special" UserFolder instance at the top of the
> hierarchy, and then everything else Just Wo
I'm trying to compare two number, or at least I think they're numbers.
If I do:
Equal block
I and J print out the same, but do not compare to be equal since "Equal
block" string doesn't print.
I must be doing something wrong.
Please, suggestions before I pull out all my ha
(Tested with
)
There are an awful lot of colons in there :-)
Here's an off-the-wall idea:
This looks better as a tal:tag
Or, if you only use this kind of thing with tal:replace, tal:content and
tal:define.
Of course, none of this helps for tal:attributes.
--
Steve Alexander
Evan Simpson wrote:
Guido van Rossum wrote:
IMO TALES should solve this for itself by introducing an if/then/else
expression form rather than depending on Python. If you can have a
"not:.." expression, surely you can have an "if:..:then:..:else:.."
expression.
Now that you point it out, it's no
Caveat:
a) I haven't followed the discussion closely and I haven't used this in
Zopes
better than 2.4.x and (I think) 2.5.0, so I am not aware of any API
Changes
in 2.6x
b) The way I did it is more or less crude. You may want to add to Zope's
own
local Roles rather tha
