On Wednesday, June 6, 2001, at 06:18 PM, Ian Bicking wrote:
> Yeah, but it won't always work, even if you are clever. Like if you
> want to highlight the background of rows that match some condition.
>
>
>
> Though I'm not entirely sure how you would do this in ZPT either --
> tal:conditio
Hello, webware-devel,
My name is Donovan Preston. I have been lurking on the list for a while
and have posted occasionally, but I feel now a formal introduction is
required. A few months ago I got a job at InterSight working for Paul
McGavin, whom some of you may know since he spent quite a bi
Donovan Preston <[EMAIL PROTECTED]> wrote:
> - You can access methods or data members of this page from your TAL like
> this:
> Dummydata
> Where getContent is a function on your page object.
Now, tal has some sort of path syntax, based more closely on Zope
internals, right? So are you ju
On Thursday 07 June 2001 12:37, Chuck Esterbrook wrote:
> At 12:41 PM 6/7/2001 -0700, Tavis Rudd wrote:
> >I've just uploaded a new version that
> >implements all the changes we talked about this morning.
> >All the tests pass on Python 2.1 and 2.0
>
> Thanks.
back to my thesis now... I've recr
I've just uploaded a new version that
implements all the changes we talked about this morning.
All the tests pass on Python 2.1 and 2.0
___
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
I've kept the quotes. No, TS doesn't expand values.
On Thursday 07 June 2001 12:02, Ian Bicking wrote:
> Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> > But, yes, we can do without quotes. After all, $foo
> > doesn't even expand with quotes unless $foo really
> > contains them.
>
> TS doesn't --
Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> But, yes, we can do without quotes. After all, $foo doesn't even expand
> with quotes unless $foo really contains them.
TS doesn't -- I don't think, at least shouldn't -- "expand" values.
That way lies sh and m4, and those are scary.
$foo *evaluates
At 11:38 AM 6/7/2001 -0700, Tavis Rudd wrote:
>one other minor point:
>should we require the quotation marks on files?
>
> > #include raw $userHTProfile
> > #include "footer.html"
> becomes
> > #include raw $userHTProfile
> > #include footer.html
I could easily live without them. That means "raw
raw it is then. I've started changing the docs and but it'll take
a while to swap the code over.
On Thursday 07 June 2001 10:58, Chuck Esterbrook wrote:
> At 11:02 AM 6/7/2001 -0700, Tavis Rudd wrote:
> >'raw' is excellent! Same mean, but simpler.
> >
> >How about this then?
>
> I concur.
___
I'm resending this because I got the address wrong the first time.
- Forwarded message from -
Date: Thu, 7 Jun 2001 11:02:34 -0700
To: webware-devel
Subject: Re: [Webware-devel] Re: more on TS #parse
On Thu, Jun 07, 2001 at 10:47:48AM -0700, Tavis Rudd wrote:
> #include $var
> or
> #
BTW, didja all notice that Sourceforge lists are back up to their
normal speed?
--
-Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED])
http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol
___
Webware-devel m
one other minor point:
should we require the quotation marks on files?
> #include raw $userHTProfile
> #include "footer.html"
becomes
> #include raw $userHTProfile
> #include footer.html
___
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.s
How does this read for the user's guide? Chuck, note the last paragraph.
\subsection{\#include directives}
\code{\#include} directives are used to include text from outside the template
definition. The text can come from \code{\$placeholder} variables or from
external files. The example below
At 11:19 AM 6/7/2001 -0700, Tavis Rudd wrote:
>TemplateServer uses its .getFileContents(fileName) method to locate the
>file to be included. This method can be overriden in subclasses if you
>want to modify or extend its behaviour. It is possible to implement the
>logic for getting remote fil
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> one other minor point:
> should we require the quotation marks on files?
Yes!
Ian
___
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
At 12:54 PM 6/7/2001 -0500, Ian Bicking wrote:
>unparsed
Don't forget unlexed, uncompiled and unbound.
>plain text
>text/plain (from MIME)
If you're template and include are both something like XML or HTML, then
the text/plain could be somewhat confusing. A user might be tempted to say
"text
On Thursday 07 June 2001 10:54, Ian Bicking wrote:
> unparsed
> plain text
> text/plain (from MIME)
> raw
> raw text
>
> I think raw text makes the most sense to me. Plain text
> also seems like a good description.
'raw' is excellent! Same mean, but simpler.
How about this then?
#raw
some ve
At 10:52 AM 6/7/2001 -0700, Tavis Rudd wrote:
>I think people would learn it's meaning fairly fast as it's
>also used in the #verbatim directive There's good
>symmetry in that. Can you think of any easier words
>that mean the same thing?
I can live with verbatim and find it preferable to the al
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> On Thursday 07 June 2001 10:39, Ian Bicking wrote:
>
> > Verbatim is a hard word, and I'm not *really* clear what
> > it means. Copy confuses me, because I think of that word
> > with computers as a very active verb -- like, it does
> > something external.
At 10:47 AM 6/7/2001 -0700, Tavis Rudd wrote:
>Agreed. So it would be
>
>#include $var
>or
>#include "file.txt"
>
>or
>
>#include verbatim $var
>or
>#include verbatim "file.txt"
Looks great. Also need a setting, API or hook to provide a custom list of
paths that the file can exist in.
-Chuck
On Thursday 07 June 2001 10:39, Ian Bicking wrote:
> Verbatim is a hard word, and I'm not *really* clear what
> it means. Copy confuses me, because I think of that word
> with computers as a very active verb -- like, it does
> something external. Copyfile, perhaps, or insertfile.
I think people
On Thursday 07 June 2001 10:34, Chuck Esterbrook wrote:
> Also, can we change:
> #parse file="foo.text"
>
> to:
> #parse "foo.text"
>
> The "file=" gets redundant by the second time you use
> #parse.
Agreed. So it would be
#include $var
or
#include "file.txt"
or
#include verbat
Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> Or insert:
> #insert "foo.text"
> All though that is a little vague and starting with "in" like "include"
> might create brainspace competition. Forget "insert".
#insert was the first thing I thought of, before reading your post. I
think it's a
Also, can we change:
#parse file="foo.text"
to:
#parse "foo.text"
The "file=" gets redundant by the second time you use #parse.
-Chuck
___
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webw
FYI, here is how the Quixote folks do templating. I personally don't find
it very attractive. I'd rather write servlets, PSP or Velocity-like
templates. Maybe I'm just biased.
>To: [EMAIL PROTECTED]
>Subject: Re: [Quixote-users] PTL docs
>Mail-Followup-To: [EMAIL PROTECTED]
>From: Andrew Kuchl
On Thursday 07 June 2001 10:21, Chuck Esterbrook wrote:
> BTW your examples bring up the interesting point of
> compound word directives. I don't see any reason why we
> can't allow a space like we do with "#end if". For
> example:
> #include verbatim "foo.text"
I like this one! It makes th
At 10:18 AM 6/7/2001 -0700, Tavis Rudd wrote:
>Chuck,
>I agree with all this, but don't like the name #copy
>
>#verbatimInclude
>or
>#verbatim-include
>or
>#plainInclude
>or
>#plain-include
>
>would be better. Your thoughts?
I prefer #copy to the above.
Another choice is to have an optional argu
At 10:09 AM 6/7/2001 -0700, Tavis Rudd wrote:
>Would you mind sending me a copy that I can put in the
>package.
That was my plan.
-Chuck
___
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
Chuck,
I agree with all this, but don't like the name #copy
#verbatimInclude
or
#verbatim-include
or
#plainInclude
or
#plain-include
would be better. Your thoughts?
On Thursday 07 June 2001 10:00, Chuck Esterbrook wrote:
> TS currently uses #parse and #include. The first groks
> the file, t
TS currently uses #parse and #include. The first groks the file, the second
just copies the contents with no interpretation.
I think the functionalities are good, but not the names.
Consider the terms used by other languages:
- SSI: include
- IE/HTML: @import
- Python:
On Thursday 07 June 2001 09:51, Chuck Esterbrook wrote:
> Thanks for getting the "#end if" change in so fast.
> The first time I run the test suite, I get 8 failures all
> related to #parse and #include. However, every time after
> that the suite passes.
>
> The difference seems to be that the f
Tavis,
Thanks for getting the "#end if" change in so fast.
The first time I run the test suite, I get 8 failures all related to #parse
and #include. However, every time after that the suite passes.
The difference seems to be that the first run creates a parseTest.txt file.
There is probably a
32 matches
Mail list logo
