> From: Peter Reilly [mailto:[EMAIL PROTECTED]
> >attributes like 'trim', 'optional', or why not 'normalize', etc... --DD
> >
> Ok done "trim" and "optional". What would "normalize" do ?
Thanks Peter. I was just throwing 'normalize' out there. I'm no XML guru,
but I thought there was special optio
Dominique Devienne wrote:
How about:
...
???
Makes it an nested element of , which allows to have interesting
attributes like 'trim', 'optional', or why not 'normalize', etc... --DD
Ok done "trim" and "optional". What would "normalize" do ?
Peter
--
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>...
> >>>
> >>>
> Ok, done.
> Should this be part of ant 1.6.1 ?
> Peter
I think so. Should be a minor, but useful modification. And it´s missed by
some persons :-)
Jan
[EMAIL PROTECTED] wrote:
How about:
...
+1
Stefan
Ok, done.
Should this be part of ant 1.6.1 ?
Peter
+1.
On first I thought an attribute would be easier, because shorter.
But you can much more things here and the use is the same as for
nested elements and attributes.
Jan
-
> > How about:
> >
> >
> >
> >
> >
> >
> > ...
> >
> >
>
> +1
>
> Stefan
+1.
On first I thought an attribute would be easier, because shorter.
But you can much more things here and the use is the same as for
nested elements and attributes.
Jan
On Fri, 23 Jan 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> How about:
>
>
>
>
>
>
> ...
>
>
+1
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Makes it an nested element of , which
> allows to have interesting
> attributes like 'trim', 'optional', or why not
> 'normalize', etc... --DD
I agree that this is attractive.
-Matt
__
Do you Yahoo!?
Yahoo! SiteB
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>
> On Fri, 23 Jan 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
>
> >> ?
> >>
> > This sounds good.
>
> Not sure either, sorry 8-(
How about:
...
???
Makes it an nested element of , which allows to have interesting
attri
> >> ?
> >>
> > This sounds good.
>
> Not sure either, sorry 8-(
>
> It is nested text, not necessarily CDATA and you assign the name of
> the macrodef pseudo-property holding the text, not the text itself
> with this attribute. Thinking about it again, textname isn't that
> bad.
>
> Stefan
On Fri, 23 Jan 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
>> ?
>>
> This sounds good.
Not sure either, sorry 8-(
It is nested text, not necessarily CDATA and you assign the name of
the macrodef pseudo-property holding the text, not the text itself
with this attribute. Thinking about it agai
[EMAIL PROTECTED] wrote:
but I'm not sure about the name "textname" for the attribute. I don't
have a better one right now and am not into bikeshedding, so go ahead
and commit in HEAD.
?
This sounds good.
Peter
-
To uns
> but I'm not sure about the name "textname" for the attribute. I don't
> have a better one right now and am not into bikeshedding, so go ahead
> and commit in HEAD.
?
Jan
On Thu, 22 Jan 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
> I would like to add support to to allow the text content
> of macros to be placed in the macro instance:
+1
but I'm not sure about the name "textname" for the attribute. I don't
have a better one right now and am not into bikesheddi
+1
Jan
> -Original Message-
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 22, 2004 4:24 PM
> To: Ant Developers List
> Subject: Re: text support for macrodef
>
>
> +1
>
> On Jan 22, 2004, at 10:03 AM, Peter Reilly wrote:
>
&
+1
On Jan 22, 2004, at 10:03 AM, Peter Reilly wrote:
I would like to add support to to allow the text content
of macros to be placed in the macro instance:
use is like this:
@{text}
Hello world
The textname attribute value becomes a macrodef attribute that
g
--- Peter Reilly <[EMAIL PROTECTED]> wrote:
> I would like to add support to to allow
> the text content
> of macros to be placed in the macro instance:
Non-committing +1... I like it.
-Matt
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try
16 matches
Mail list logo
