On Wednesday 30 May 2001 07:50, Tom Schwaller wrote:
> Are filters already working?
> #filter filterName(filterArgs)
> ..
> #/filter filterName(filterArgs)
You can do static once-off filtering with
custom macros, but I haven't gotten around to
implementing a run-time #filter directive yet.
> I
Tavis Rudd wrote:
> > I was mainly thinking of cases where the template
> > includes program listing fragments. In that case,
> > distinguishing comment #s from macro/command #s can be
> > more difficult.
>
> In that case you could use
> #verbatim
> a Python code example:
> if 1: #a comment
>
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> I have no qualms about using the parser
> for that stuff (... I wish I had the time). However, I still think
> it's not worth the effort for the directives and I actually
> prefer /# to ; for a closure. It's more visible. I might reconsider
> at a future
On Wednesday 30 May 2001 06:41, Chuck Esterbrook wrote:
> (starting to chant)
> Parse! Parse! Parse! Parse! Parse! Parse!
> :-)
>
> Actually, I'm curious: What are the other syndromes? I
> forget.
The only one that I can remember was
the $placeholder(arg=$placeholder(arg2=1234))
nesting. What
(starting to chant)
Parse! Parse! Parse! Parse! Parse! Parse!
:-)
Actually, I'm curious: What are the other syndromes? I forget.
At 02:00 AM 5/30/2001 -0500, Ian Bicking wrote:
>Just bite the bullet already and use the parser! It won't be 1.0
>until you use a parser, no matter what, becaus
Just bite the bullet already and use the parser! It won't be 1.0
until you use a parser, no matter what, because this is only one
syndrome of the lack of a parser among many syndromes.
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> On Tuesday 29 May 2001 23:34, Ian Bicking wrote:
> > To be safe, any us
On Tuesday 29 May 2001 23:34, Ian Bicking wrote:
> To be safe, any use of this syntax in a WYSIWYG editor
> should use explicit closures -- newlines are meaningless
> in HTML, and you never can be sure how the editor will
> treat them, or preserve them.
Good point. You raised this before, but I'd
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> On Tuesday 29 May 2001 23:11, Chuck Esterbrook wrote:
>
> > Well, for what it's worth, I prefer ;
> > I think ;# looks awkward at best and confusing at worst.
>
> I agree with you about that. It's just a pain in the ass to
> switch to a single char closur
At 11:31 PM 5/29/2001 -0700, Tavis Rudd wrote:
>I agree with you about that. It's just a pain in the ass to
>switch to a single char closure - i.e. create
>a parser that would be able to handle all the different types of
>directives in addition to $placeholders. Adding a new directive
>is current
On Tuesday 29 May 2001 23:11, Chuck Esterbrook wrote:
> Well, for what it's worth, I prefer ;
> I think ;# looks awkward at best and confusing at worst.
I agree with you about that. It's just a pain in the ass to
switch to a single char closure - i.e. create
a parser that would be able to handl
At 01:11 AM 5/30/2001 -0500, Ian Bicking wrote:
>Yeah. *I* just *think* it should be #. I don't actually remember
>quite what it is either.
Well, for what it's worth, I prefer ;
I think ;# looks awkward at best and confusing at worst.
___
Webware-d
Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> Isn't the terminator for TS #; ?
> Or was it ;# ? I forget...
Yeah. *I* just *think* it should be #. I don't actually remember
quite what it is either.
Ian
___
Webware-devel mailing list
[EMAIL PROT
On Tuesday 29 May 2001 22:56, Chuck Esterbrook wrote:
> Isn't the terminator for TS #; ?
> Or was it ;# ? I forget...
Directive closures are the end of the line or ;# if you need
to close it explicitly. I don't think many people will ever use
the explicit ;# closure unless they're doing some
On Tuesday 29 May 2001 22:57, Mike Orr wrote:
> > On Tuesday 29 May 2001 22:07, Ian Bicking wrote:
> > I meant the ## comments in TemplateServer rather than
> > those Python. Anyway, I think I also prefer sticking
> > with # for everything except for $placeholders. It's
> > consistent and it def
On Tuesday 29 May 2001 22:59, Ian Bicking wrote:
> #comment is readable, and I know non-programmers really
> like things they can read aloud, as opposed to lots of
> punctuation. I suggest it for their benefit.
Fair enough. I don't see any harm in allowing both
#comment and ##. It's dead simple
At 12:49 AM 5/30/2001 -0500, Ian Bicking wrote:
>Well, if ## comments seem odd, how about:
>
>#comment
>
>That's easy, easy to read, and doesn't propogate funny symbols. I
>think I considerably prefer it to ##, especially since I prefer # as a
>terminator too, since that feels balanced to me.
I
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> ## comes from Velocity as well. #comment is symmetrical
> with the other directives, however. But as # is a comment
> in Python you could say that ## is a synonym for #comment ;)
#comment is readable, and I know non-programmers really like things
they can
On Tue, May 29, 2001 at 10:36:11PM -0700, Tavis Rudd wrote:
> On Tuesday 29 May 2001 22:07, Ian Bicking wrote:
> > I think # works well. It's big, even in a proportional
> > font. It's not used much, #1 isn't that common, and the
> > only HTML place is anchors. You aren't like Python
> > anyway
On Tuesday 29 May 2001 22:49, Ian Bicking wrote:
> Tavis Rudd <[EMAIL PROTECTED]> wrote:
> Well, if ## comments seem odd, how about:
> #comment
too much to type. I like ## because it makes escaping
#directives dead simple and it allows you to use decorative
comments like
##
or
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> On Tuesday 29 May 2001 22:07, Ian Bicking wrote:
> > I think # works well. It's big, even in a proportional
> > font. It's not used much, #1 isn't that common, and the
> > only HTML place is anchors. You aren't like Python
> > anyway, since $ isn't meanin
On Tuesday 29 May 2001 22:07, Ian Bicking wrote:
> I think # works well. It's big, even in a proportional
> font. It's not used much, #1 isn't that common, and the
> only HTML place is anchors. You aren't like Python
> anyway, since $ isn't meaningful in Python.
I meant the ## comments in Temp
Tavis Rudd <[EMAIL PROTECTED]> wrote:
> There is one point about "What should it look like?" that might
> be worthwhile looking at again. In Velocity, WebMacro, and
> thus TemplateServer, all directives begin with # and macro
> calls are in the form #macroName(). Last night, Mike asked
> if t
On Tuesday 29 May 2001 06:40, Chuck Esterbrook wrote:
> BTW I CCed webware-devel where these discussions on
> templating design are taking place. Although recently
> they have quieted down as we have phased out of "What
> should it look like?" to "Who's implementation is doing
> what?".
There is
23 matches
Mail list logo
