> I think its a good idea. Howver the outer tag should probably be
<propertygroup> or somthing like that. I think the . seperator is fine.
Do others feel strongly about this? I have it working with <property
prefix="....">. I like it being all in one task so that when the user reads
the docs for <property> they understand everything about it.
Note that they can be nested as well. Ie,
<property prefix="win">
<property prefix="vc7">
<property name="cc" value="cl.exe"/>
</property>
</property>
Would give: win.vc7.cc = "cl.exe"
> I don't see a need for allowing custom seperators - it just seems to me
that it would add unnecessary confusion. '.' is already a pseudo
standard by its use for 'nant'. properties.
I agree for most cases but it doesn't really hurt to add it and it adds the
ability to use it in ways we haven't thought of.
> On a slightly different not it would be nice if we extended -projecthelp
to show all global properties ( or maybe a different option ). There was
a question on Nant-Users about how to reference environment variables.
If you could get a dump of all env, nant and custom global props it
would help the learning process.
I'm thinking of having a special type of property called an option that
build files have that are designed to be set by the user. So --projecthelp
would display a list of the targets and build options. Ideally a gui tool
would be able to show a nice dialog of the build options. When you save a
group of build options you save a build configuration.
So people send in your votes on these topics:
1. <propertygroup name="win"> or <property prefix="win">
2. separator attribute or no separator attribute
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
