On Wed, 30 Jul 2003 06:16 am, Evan Simpson wrote:
> OK, I've checked in a sample implementation on "evan-pathprefix-branch".
> It allows for registering prefixes with:
This seems very nice. I'm not likely to actually have a chance to play with it
any time soon though, so I can't really comment
On Tue, 29 Jul 2003 17:51:56 -0400
Shane Hathaway <[EMAIL PROTECTED]> wrote:
> Jim Penny wrote:
> > Frankly, would not even have occurred to me - I would probably
> > create a tiny Script (Python) en passant, and called it directly,
> > as:. I
> > did not realize that this is deprecated in Zope3.
On Tue, 29 Jul 2003 17:04:46 -0500
Evan Simpson <[EMAIL PROTECTED]> wrote:
> Jim Penny wrote:
> > But, what does all of this have to do with index:, key:, int:, etc.?
> > index: and key: are particularly interesting, in that they use
> > different syntax for something that python conflates syntact
Just to throw my 2c into the fray.
ZPT is an HTML/XML template language. But what does that mean, really?
IMHO. Template languages are data structure navigation languages, or
model navigating languages (EEEK, templates having direct access to the
model!). And the should avoid being turing-complet
On Tue, Jul 29, 2003 at 04:43:21PM -0400, Shane Hathaway wrote:
> Python expressions won't be banned. I will never consider them
> discouraged for all cases, either. There will always be a need for
> constructs like:
>
> ...
> ...
ok.
> However, the following is quite bad:
And quite common
Jim Penny wrote:
But, what does all of this have to do with index:, key:, int:, etc.?
index: and key: are particularly interesting, in that they use
different syntax for something that python conflates syntactically.
That is, an integer indexed reference looks exactly like a string
indexed referen
Shane Hathaway writes:
> I'm not quite sure what you're saying. The following fails compilation:
>
>
That's because you've broken the syntax. It should have been:
or, more legibly,
I think the problem is that it's easy to think of TAL as little bits
of different syntaxes, but
Jim Penny wrote:
Frankly, would not even have occurred to me - I would probably create a
tiny Script (Python) en passant, and called it directly, as:
. I did not
realize that this is deprecated in Zope3.
Your example relies on implicit acquisition. Your example is not
deprecated, it just won't w
On Tue, Jul 29, 2003 at 09:26:07PM +0100, Christopher Boomer wrote:
> The only problem I ever have in this area is knowing when something
> is too complicated for TAL, and moving that boundary will not help.
In particular, expanding the size of the overlapping gray area will not help.
> Often I s
Fred L. Drake, Jr. wrote:
Shane Hathaway writes:
> - You have to be careful not to use double quotes in expressions.
> (Ampersands and less-than/greater-than signs are tricky too. Watch out
> for pairs of hyphens!)
This is FUD. TAL can handle these things quite well; the "problem" is
that m
On Tue, 29 Jul 2003 16:43:21 -0400
Shane Hathaway <[EMAIL PROTECTED]> wrote:
> [Paul Winkler]
> >>>I guess I don't understand the goal. Are we trying to make it
> >>>so that zpt authors don't have to know any python?
>
> [Chris Withers]
> >>For me, that would be ideal...
>
> [Paul Winkler]
> >>>
If DTML used TALES expressions, it would be just as clean as ZPT.
With the one caveat that ZPTs are valid XHTML, while DTML methods needn't
balance tags and needn't mark empty tags as such (i.e. "",
instead of ""). DTML tags can straddle HTML tags in
completely non-XML ways: ""; limiting the
tools
Shane Hathaway writes:
> - You have to be careful not to use double quotes in expressions.
> (Ampersands and less-than/greater-than signs are tricky too. Watch out
> for pairs of hyphens!)
This is FUD. TAL can handle these things quite well; the "problem" is
that many web developers don't
Chris Withers wrote:
http://dev.zope.org/Wikis/DevSite/Proposals/MacroParameters
I'm swinging round to the ideas behind this proposal having initially
been against it.
What's the status of implementation?
Somewhere in the clouds. :-)
Seriously, people seem to be in favor of it, but it's not a pre
[Paul Winkler]
I guess I don't understand the goal. Are we trying to make it
so that zpt authors don't have to know any python?
[Chris Withers]
For me, that would be ideal...
[Paul Winkler]
I really think that's a mistake.
Guys, that line of thinking is a distraction. ZPT authors ought to
learn P
I have been watching this thread silently for what seems like weeks, and I
think it is time for a newcomer's opinion. I like to read above my station
;-)
>> "options/a_mapping/key:items/index:0" rather than
>> "python:options['a_mapping']['items'][0]".
They look very similar to me. There is lit
OK, I've checked in a sample implementation on "evan-pathprefix-branch".
It allows for registering prefixes with:
from Products.PageTemplates.PathPrefixes import registerSubPathPrefix
registerSubPathPrefix('call', call_compiler, call_handler)
It includes an implementation of 'var:', 'call:', 'k
On Tue, 29 Jul 2003 14:27:34 -0400
Paul Winkler <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 29, 2003 at 06:22:38PM +0100, Chris Withers wrote:
> > Paul Winkler wrote:
> >
> > >On Wed, Jul 23, 2003 at 11:07:20AM -0500, Evan Simpson wrote:
> > >
> > >>... This would allow
> > >>"options/a_mapping/ke
On Mon, Jul 28, 2003 at 02:49:33PM -0400, Casey Duncan wrote:
> You can usually commit a subtransaction to get a _p_jar and oid (I think) set.
> You can still abort this at the end of the test to clean up.
yep, this seems to work very nicely! Thanks Casey!
def setUp(self):
...
get_transact
On Tue, Jul 29, 2003 at 06:22:38PM +0100, Chris Withers wrote:
> Paul Winkler wrote:
>
> >On Wed, Jul 23, 2003 at 11:07:20AM -0500, Evan Simpson wrote:
> >
> >>... This would allow
> >>"options/a_mapping/key:items/index:0" rather than
> >>"python:options['a_mapping']['items'][0]".
> >
> >Why is
Am Dienstag, 29. Juli 2003 19:22 schrieb Chris Withers:
> Paul Winkler wrote:
> > On Wed, Jul 23, 2003 at 11:07:20AM -0500, Evan Simpson wrote:
> >>... This would allow
> >>"options/a_mapping/key:items/index:0" rather than
> >>"python:options['a_mapping']['items'][0]".
> >
> > Why is that an impro
Shane Hathaway wrote:
We recently had a discussion about this:
http://dev.zope.org/Wikis/DevSite/Proposals/MacroParameters
The conclusion we came to is that we need a new kind of construct,
tentatively called a "subtemplate". Subtemplates accept parameters and
have full control over the varia
Paul Winkler wrote:
On Wed, Jul 23, 2003 at 11:07:20AM -0500, Evan Simpson wrote:
... This would allow
"options/a_mapping/key:items/index:0" rather than
"python:options['a_mapping']['items'][0]".
Why is that an improvement?
Personally, I find it much easier to read...
I wonder what non-pytho
Evan Simpson wrote:
'key:' -- use item access with the prefixed string.
'index:' -- use item access with the prefixed integer.
'attr:' -- use attribute access with the prefixed string.
In each case, the path traversal fails if the specified access method
fails, rather than trying other access met
Philipp von Weitershausen wrote:
AFAIK, Jim wants this for Zope3 for some time now. The idea is to
implement this with named adapters.
The framework is implemented, as are one or two examples, IIRC...
The question remains how to implement this in Zope2 as we don't have
adapters there.
The implem
Shane Hathaway wrote:
Literally, "user_files/int:0" says "get item 0 of user_files,
interpreting '0' as an integer". Technically, this could be interpreted
as "get the attribute named 0 or item 0", but an attribute name must be
a string, so implicitly it really just says "get item 0".
We've co
Christopher N. Deckard wrote:
Can you put us to the underlying code and I'll take a look at what
needs to be done? This is something that is going to be very useful
to us.
Have a trawl through the list archives, I'm afraid I can't remember where the
code is...
cheers,
Chris
___
Dieter Maurer wrote:
But overall, unless you have special (non DC derived) indexes,
That can well be the case...
Anyway, what are we going to do about this crawling tab?
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/l
28 matches
Mail list logo