Jeffrey P Shell writes:
You would at the very least need something like:
condition
if.../if
elif.../elif
else.../else
/condition
Which would ensure / cut back on needless growth of stacks and/or global
variables.
Personally, I think the way Page Templates can do it (via a 'not'
I feel compelled to take the XML hard line, and point out that depending on
the ordering of XML attributes is not compliant:
http://www.w3.org/TR/xml-infoset/
XML Information Set
W3C Recommendation 24 October 2001
2. Information Items
2.2. Element Information Items
An element information item
Tim Hoffman wrote:
In addition event handlers in html ie onClick onBlur etc
are all order independant.
now adding tal: attributes that where order dependant would seem
to fly in the face of that convention. (Admittedely there are probably
no strange dependancies that could be introduced
At 06:13 10/05/2002, [EMAIL PROTECTED] wrote:
'else' is tricky within the block oriented structure of anything XML-ish,
because of the concept of 'well-formedness'. The 'if' statement would have
to be singly wrapped, and the else block wrapped separately, looking at
least somewhat awkward any
Tim Hoffman wrote:
snip
This I would imagine could introduce all sorts of nasty bugs.
Good points! On that basis, I retract my feature request ;-)
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
Jim Penny wrote:
on the surface, to be pretty ugly. I have said that there are three
specific things I dislike about ZPT -- 0) lots of things have changed
spelling again -- request v. REQUEST, here v. context v. container v.
this v. ?
Yeah, there was absolutely no need for this and I
Tim Hoffman wrote:
The big problem with the whole 'else' issue as I see
it, is that non coders, using dreamweaver etc.. would no doubt end
up with both bit's of html in their template.
But that's exactly what you want! hey can then see what would happen in either case and
will probabyl
I'm not using it, and will never use it, so why does Zope 2.5.1 always
create one for me?
Grrr. Highly annoying. :-[
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding!
On Thursday 09 May 2002 09:47, Chris Withers wrote:
Thomas Olsen wrote:
DTML is great for style sheets, javascript and such where you cannot use
ZPT and python scripts would be too ugly to use ;-)
There's no reason to use DTML for these, as I've explained before ;-)
Must have missed that
On Friday 10 May 2002 01:19, Adrian Hungate wrote:
Yeah, for CSS I'd use ZStyleSheets, and for javascript I'd use a very large
magnet... but that is another argument.
GRIN
--
Regards,
Thomas Olsen
___
Zope-Dev maillist - [EMAIL
Thomas Olsen wrote:
Must have missed that mail..?
http://zope.nipltd.com/public/lists/dev-archive.nsf/$$Search?OpenForm
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts
Quoting Jeffrey P Shell:
The 'not' TALES namespace is valuable. The downside is that you
evaluate the expression twice. A good way to work within this is
something that I did earlier today, outside of this conversation,
where I evaluate an expression earlier and assign it to a
Lennart Regebro wrote:
I'm not using it, and will never use it, so why does Zope 2.5.1 always
create one for me?
Grrr. Highly annoying. :-[
From Zope 2.1.3 (when I started Zopeing), I could write a Python
Product that expected standard_html_header and standard_html_footer to
exist.
From
From: Steve Alexander [EMAIL PROTECTED]
From Zope 2.5.1, I can write a Python Product that expects
standard_template.pt to exist.
I dont see the purpose of that. Checking that is exists is trivial if you
need it.
I don't. I want to get rid of it, thankyouverymuch.
Guess I'll just have to
If its the same as earlier zopes its line 174 of OFS\Application.py remove
the offending reserved names. Except maybe for Control_Panel, it seems
pointless. If the item's not there, an error is raised. Simple. To me there
should just be a warning message, Removing this item may cause some
On Fri, May 10, 2002 at 11:53:47AM +0100, Chris Withers wrote:
Jim Penny wrote:
on the surface, to be pretty ugly. I have said that there are three
specific things I dislike about ZPT -- 0) lots of things have changed
spelling again -- request v. REQUEST, here v. context v. container
I looked at 2.5 on surprised to see that apart from Control Panel only
'browser_id_manager' and 'temp_folder' are protected meaning you can delete
all the others. I threw a monkeypatch up that allows you to delete them
anyway, and it will work for pre 2.4 systems
on 5/10/02 12:47 AM, Jeffrey P Shell at [EMAIL PROTECTED] scrivened:
You would need something to close off the 'if' statement, otherwise, a
document full of 'if' statements and no 'else' ones could fill up a stack
needlessly.
What's so bad about that? The stack wouldn't carry over after
on 5/9/02 11:58 PM, Tim Hoffman at [EMAIL PROTECTED] scrivened:
The big problem with the whole 'else' issue as I see
it, is that non coders, using dreamweaver etc.. would no doubt end
up with both bit's of html in their template.
Don't you have that now with the kludgey 'not' construct?
Jim Penny wrote:
...can also be written as:
tal:x repeat=x xes
tr
tdtal:x replace=x/id//td
/tr
/tal:x
Interesting. I seem to remember this from the Wiki's, is it documented
anywhere else? This really seems like Chapter 5 material.
No idea, but it definitely should be...
Marc Lindahl wrote:
Don't you have that now with the kludgey 'not' construct?
What is kludgey about the 'not:' construct?!
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross
On 5/10/02 4:53 AM, Chris Withers [EMAIL PROTECTED] wrote:
Jim Penny wrote:
on the surface, to be pretty ugly. I have said that there are three
specific things I dislike about ZPT -- 0) lots of things have changed
spelling again -- request v. REQUEST, here v. context v. container v.
Jim Penny wrote:
I have also said that, while ZPT is not as warty as DTML, ZPT looks,
on the surface, to be pretty ugly. I have said that there are three
specific things I dislike about ZPT -- 0) lots of things have changed
spelling again -- request v. REQUEST, here v. context v. container
On 5/10/02 9:25 AM, Marc Lindahl [EMAIL PROTECTED] wrote:
on 5/10/02 12:47 AM, Jeffrey P Shell at [EMAIL PROTECTED] scrivened:
You would need something to close off the 'if' statement, otherwise, a
document full of 'if' statements and no 'else' ones could fill up a stack
needlessly.
From: Marc Lindahl [EMAIL PROTECTED]
You would need something to close off the 'if' statement, otherwise, a
document full of 'if' statements and no 'else' ones could fill up a
stack
needlessly.
What's so bad about that? The stack wouldn't carry over after
html/html
or body/body -
Don Hopkins wrote:
From: Marc Lindahl [EMAIL PROTECTED]
You would need something to close off the 'if' statement, otherwise, a
document full of 'if' statements and no 'else' ones could fill up a
stack
needlessly.
What's so bad about that? The stack wouldn't carry over after
html/html
Hello,
I would like to setup the security on a Zope server such that a user can
edit permissions on something they own, but not grant more permissions
than what they have acquired from the parent.
If a user owns a folder they could grant Owner any permissions
they want inside of that folder
On Fri, 2002-05-10 at 12:21, Jim Penny wrote:
On Fri, May 10, 2002 at 11:53:47AM +0100, Chris Withers wrote:
[...]
Actually, the first time I got bit was on repeat v. condition. I wanted
the condition to test each row, not to guard the entire iteration
process.
You shouldn't want that.
28 matches
Mail list logo
