RE: [nant-dev] Addition documentation (+/-)?
Just through some of the stuff into the Wiki just now :) - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED] Sent: Saturday, 21 February 2004 4:52 AM To: Mitch Denny Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Addition documentation (+/-)? Also, the Wiki is a great place for this type of info; it can be updated by users directly. :) http://nant.sf.net/wiki - Original Message - From: Gert Driesen [EMAIL PROTECTED] Perhaps first post it to the list for review, is that ok for you ? - Original Message - From: Mitch Denny [EMAIL PROTECTED] Gert suggested that we start to add references to third party tasks/resources. I've got some doco to commit which is a start. Can I get a green light to commit that (+/-)? --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Experimental branches . . .
Hi Scott, Good idea about the zip. Does the nightly snapshot just take the HEAD? Follow-up Questions: 1. Who can do the branch for me? 2. When I finish patches, who do I send them to? Cheers. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Hernandez Sent: Tuesday, 27 January 2004 3:39 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] Experimental branches . . . +1 As far as I understand it, branching is done from the head (or any tag I guess). As for blogging, go for it. Posting to the dev list is probably also a good idea. Anon CVS access is rather behind, and less reliable. It may make sense to post on your website a zip of the tree/dist when you want people to try it out. - Original Message - From: Mitch Denny [EMAIL PROTECTED] Hi folks, We'll I think we have had the discussion, so I thought it would be an appropraite time to tag and branch for some of the experimental stuff that we have been talking about. I'd like to start experimenting more publically with the taskdef / element first. If possible I'd like the branch done from the head and not the previous tag since there have been a number of fixes since then that specifically affect the ability to do a successful build. Once I had something working and a patch applied I was hoping to do a blog post and get a bit of end-user feedback on the idea. I know a lot of Nant users are into blogs so I thought it would be a good outlet. They would be able to anon cvs download from that branch and try it out. --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Experimental branches . . .
Hi guys, I'm happy to do it that way. Has anyone present done a branch of this particular module before? Any wisdom you want to share? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Hernandez Sent: Tuesday, 27 January 2004 11:03 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] Experimental branches . . . The nightly snapshot is now a nightly build; it just builds from the head. We used to have a nightly tarball but replaced it when we started using a build server. For the purpose of your branch I think it might be best if you get cvs access so you can manage it. Mitch, is that something you are up for? Gert, Ian, Gerry, does that sound reasonable? I'd rather take the enabling approach than to put more levels of indirection in... :) - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: Scott Hernandez [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, January 26, 2004 6:19 AM Subject: RE: [nant-dev] Experimental branches . . . Hi Scott, Good idea about the zip. Does the nightly snapshot just take the HEAD? Follow-up Questions: 1. Who can do the branch for me? 2. When I finish patches, who do I send them to? --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Property Scoping
What about scoped properties? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, 23 January 2004 7:07 AM To: Jaroslaw Kowalski Cc: Mitch Denny; Scott Hernandez; [EMAIL PROTECTED] Subject: Re: [nant-dev] Property Scoping To be honest I'd like to see us release a 1.0 with the current feature set before implementing somthing like typed properties. it would be kinda nice to unify properties and type references which are both essentially different types of variables. However I do feel that this is peripheral to what the majority of users want to do with nant. ie its quite a big change which doesn't actually make that much of a user-visible difference in many cases. Not that its not worth investigating just that it might be sensible to set this out past a 1.0 release. Ian Jaroslaw Kowalski wrote: Yeah, I was considering the same thing. I also wondered whether this could mean that there could be a unified type system. Filesets, string properties etc. You mean storing a fileset inside a property? Interesting idea. Gert, Ian, Scott - what do you think about typed properties? Jarek --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Property Scoping
Hiya Jarek,
Yeah I wasn't sure about the nested if approach either, its easy enough
to change the behavior (I think). By default its Global anyway, and flow
fits the bill. Maybe Local should behave like Flow, and have one called
Private or something. Shrug :)
Come to think of it, there are very few cases where you wouldn't want to
use either Global or Flow instead of Local. Need to think about where we
want Flow properties to fall out of scope and cross breed it with
Local.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 6:37 AM
To: Mitch Denny; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
Hi Mitch!
property name=x value=y accessibility=Global /
Global is actually the default. If I had this:
property name=x value=y accessibility=Local /
It would mean that the property is accessible to all things in the
current scope where a scope is defined by the current target (project
for root level tasks) or TaskContainer. So this would cause an error
in the expression evaluator:
if test=true
property name=x value=y accessibility=Local / /if
echo message=${x} /
That's intuitive. You usually expect variable to be inaccessible when it
leaves the scope.
Because x is not accessible outside of the scope defined by the if
task container. This works with my earlier taskdef work too!
Interestingly the following won't work.
if test=true
property name=x value=y accessibility=Local / if test=true
echo message=${x} / /if /if
This one is counter-intuitive. Most languages use local for what
you've called flow. What is the use for local scoping anyway?
Because local is local to the current task container. I introduced a
third accessibility level called Flow which allows this to work.
Remember that the default is Global when you are using the property
/ task, so it won't break anything. The way it works is that I have
lots of PropertyDictionary objects attached to a hierarchy of Scope
objects.
The scope is updated when ever a build/target/task container starts or
finishes.
I haven't noticed a patch attached, but I don't know why do you want to
store multiple dictionaries? Usually the this kind of processing can be
done entirely on the evaluation stack.
I also modified quite a bit of the implementation of
PropertyDictionary so that it now stores a Property object as its
value although the external interface is unaffected (cross fingers I
didn't break anything).
Now that I have done this, and if there is enough interest I'd like to
propose that we do something like has been done for expression
evaluation, take a branch and do some exploritory work on this where
this = taskdef / and property scoping.
This definitely needs some thought. +1 for the branch idea.
Can I get a +1 or -1?
+2/3
Jarek
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Property Scoping
Scott,
I'd really prefer to branch on this - it has the ability to really break
things. One of the first changes is changing the PropertyDictionary to
to store Property objects instead of string values. The property object
is where the accessibility level is stored.
While I am really keen to put this in, I realise that this may not be
stable before the next release. One of the key drivers for the scoped
properties (for me anyway) is the inline task definitions. That's why I
wanted to see them together. Scoped properties would need to be
implemented first mind.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Hernandez
Sent: Thursday, 22 January 2004 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
Seems like the flow scope should be called local in C#/programming
terms, and local would be private/container-only scoping. Having
global be the default is a good call, but only in come case, as you
have identified in if//foreach//etc.
I'm sure we will be able to say more with a patch; so we can test things
out. If the changes are small enough, and defaults don't change existing
functionality, I'm happy to put them in the head since we are still a
little while from testing/beta'n this version.
I'd be inclined to separate the two patches, one for scoped properties
(which are core changes) and one for the new task def stuff.
- Original Message -
From: Mitch Denny [EMAIL PROTECTED]
Hi folks,
OK, I've got a bit of a prototype working for property scoping which
so
far appears to be non-breaking to existing scripts. It works like
this:
property name=x value=y accessibility=Global /
Global is actually the default. If I had this:
property name=x value=y accessibility=Local /
It would mean that the property is accessible to all things in the
current scope where a scope is defined by the current target (project
for root level tasks) or TaskContainer. So this would cause an error
in
the expression evaluator:
if test=true
property name=x value=y accessibility=Local /
/if
echo message=${x} /
Because x is not accessible outside of the scope defined by the if
task
container. This works with my earlier taskdef work too! Interestingly
the following won't work.
if test=true
property name=x value=y accessibility=Local /
if test=true
echo message=${x} /
/if
/if
Because local is local to the current task container. I introduced a
third accessibility level called Flow which allows this to work.
Remember that the default is Global when you are using the property
/
task, so it won't break anything. The way it works is that I have lots
of PropertyDictionary objects attached to a hierarchy of Scope
objects.
The scope is updated when ever a build/target/task container starts or
finishes.
I also modified quite a bit of the implementation of
PropertyDictionary
so that it now stores a Property object as its value although the
external interface is unaffected (cross fingers I didn't break
anything).
Now that I have done this, and if there is enough interest I'd like to
propose that we do something like has been done for expression
evaluation, take a branch and do some exploritory work on this where
this = taskdef / and property scoping.
Can I get a +1 or -1?
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Property Scoping
Hiya,
Yeah, I was considering the same thing. I also wondered whether this
could mean that there could be a unified type system. Filesets, string
properties etc.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 7:50 AM
To: Mitch Denny; Scott Hernandez; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
Scott,
I'd really prefer to branch on this - it has the ability to really
break things. One of the first changes is changing the
PropertyDictionary to to store Property objects instead of string
values. The property object is where the accessibility level is
stored.
The branch is a good idea. I'd like to evaluate another issue: can we
have TYPED properties? Like this:
property name=counter type=integer value=0 /
This way you can write:
if test=${counter + 1 = 100}
/if
instead of:
if test=${convert::to-int(counter) + 1 = 100} /if
Once a property has its type set, it cannot be re-typed. Every time you
store a value in such a property, it is checked for type compatibility.
Storing data type (optional - would default to string) in a
PropertyDictionary would help here a lot.
Jarek
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Idea: Inline task definitions (task orchestration/macros).
Thanks for the perspective. quote source=Stefan It turns out that in a lot of our users' build files a single task or a combination of tasks has to be invoked repeatedly with different combinations of parameters. As I'm just feeling my way into C# right now (don't ask) I think that this will become even more true in a .NET environment where I'll need one csc task per assembly I want to create as opposed to a single javac task in Java land with its 1:1 mapping of public classes and files. /quote I'm seeing this already in my build scripts, and I suspect that build scripts could be simplified significantly by doing something similar to Nant. In our case we can do the taskdef / element and simply do the include / to suck in the definitions, it works like a charm on the modified build I have. I am currently working on the property scoping mechanism. Believe it or not this is actually a harder change because I need to create a property dictionary (in my current implementation approach) for every scope. Then have a front end lookup (so its transparent) to search all the dictionaries in a tree. Interesting stuff actually. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Wednesday, 21 January 2004 9:06 AM To: Mitch Denny Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Idea: Inline task definitions (task orchestration/macros). On Tue, 20 Jan 2004, Mitch Denny [EMAIL PROTECTED] wrote: It is, in fact I spoke to Ian about it last week and he pointed me at your blog entries on the subject. Which are certainly not the full story. Can you recall the justifications made for the element? The Ant and NAnt communities have different takes on some issues, in particular Anters don't like anything scripty in their build files while scripty stuff is a first class citizen in NAnt, so not all reasons for macrodef in Ant may apply to Ant. When Peter Reilly suggested macrodef and it cousin presetdef I didn't understand its potential imediately, I thought it was just syntactic sugar - but I've been utterly wrong. It turns out that in a lot of our users' build files a single task or a combination of tasks has to be invoked repeatedly with different combinations of parameters. As I'm just feeling my way into C# right now (don't ask) I think that this will become even more true in a .NET environment where I'll need one csc task per assembly I want to create as opposed to a single javac task in Java land with its 1:1 mapping of public classes and files. So what do you do in NAnt if you want to execute the same csc task for ten assemblies - the exactly same configuration of the task itself but only the assembly name and the set of source files changes? In Ant 1.5.x you could (1) Copy'n'Paste, (2) use script and be called a herectic or (3) use antcall which is an incredibly heavy operation in Ant - NAnt may or may not be different. Ant 1.6 also added import. You can now write a library build file that defines macros for complex combinations of tasks. This means that macrodef can be used to improve build file snippet reuse by encapsulating and even hiding parts of the build logic. There may be other pros for the tasks, but the above has convinced me to view this task together with import as the most important feature of Ant 1.6. Cheers Stefan -- http://stefanbodewig.blogger.de/ --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Idea: Inline task definitions (task orchestration/macros).
I still haven't got any firm ideas on now to handle Nant data types like filesets etc. I'd really like to be able to use them. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Monday, 19 January 2004 11:59 PM To: Mitch Denny Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Idea: Inline task definitions (task orchestration/macros). Sorry for coming late tgo the discussion, but the original request sounds a lot like Ant's new macrodef[1] task. Stefan Footnotes: [1] http://ant.apache.org/manual/CoreTasks/macrodef.html -- http://stefanbodewig.blogger.de/ --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Idea: Inline task definitions (task orchestration/macros).
Hi folks, I had a chance to do some tinkering last night on a feature that I have desperately wanted in Nant for quite some time. The ability to do inline task definitions in XML that orchestrate a number of other tasks. It works like this: project name=test taskdef name=foobar echo message=Hello / echo message=World / /taskdef target name=build foobar / /target /project I've managed to get an implementation of this working by making a number of minor modifications to the source. The list of source files affected is: 1. Project.cs Added a loop to the InitializeProjectDocument method which reads the taskdef elements and creates a task builder for them. Also modified the loop that executes the global tasks so that it ignores the taskdef elements and doesn't treat them as tasks. 2. TaskBuilder.cs Added a new constructor which takes an XmlNode so the task builder can pass that onto the InlineTask instance when it is created. Also added a property IsInline as a flag to the task builder's CreateTask (modified) method to know to handle them in a special way. 3. InlineTask.cs This is a new class. This class takes the XmlNode that was stored with the TaskBuilder when the project file was read in. It's a TaskContainer so it just calls ExecuteChildTasks (modified). 4. TaskContainer.cs Added an overload for ExecuteChildTasks which allows the InlineTask class to override which XmlNode it users to parse over. I think that is pretty much it, although if I went through and did it again I'd be tempted to refactor things a little bit. Anyway, where I see this being useful is helping lower the barrier to entry for task developers by allowing them to just have .build files that they can include in without having to cut real code (and therefore have a build system for that code). I've tested that this works with include files and it does (so far). You might be wondering how this differs from target elements, and I think there is little difference to be honest, other than it feels more consistent when all you are doing is orchestrating the functionality of a number of tasks for reuse. It could also drive a few other tweaks such as the ability to have private properties. On the taskdef element, somehow I'd like to be able to specify attributes which can be used just like properties for the tasks contained within the taskdef, but have their scope limited just for that run. I think there is enough to bite off there! - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] SUMMARY: Expression Syntax
I really need it too. +1
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Martin Aliger [mailto:[EMAIL PROTECTED]
Sent: Monday, 8 December 2003 11:17 PM
To: Scott Hernandez; [EMAIL PROTECTED]
Subject: Re: [nant-dev] SUMMARY: Expression Syntax
Now for the larger question, Does everyone want expression
support in
NAnt?
I definitely want it! I need it really badly. Currently I'm
unable to check some things correctly without expressions
(without script or external utility). Expression will be very
easy in mine case.
It is:
foreach item=String in=${changes} delim=
property=folder
property name=name value=${folder}.dll/
ifnot test=endswith('${name}','.Test.dll')
...
/ifnot
/foreach
very readable (=maintainable), no need to learn script syntax
or write any external code.
summary: I think expression are really needed in Nant.
Just mine 2 cents...
Martin
btw: expression syntax is maybe incorrect here - but it's not
important.
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us
help YOU! Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] SUMMARY: Expression Syntax
Give them choice ... do both! Just share the code-base :)
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, 8 December 2003 3:28 PM
To: Mitch Denny
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] SUMMARY: Expression Syntax
I don't think it is - is it ? Maybe the suggestion was that
xmlpeek could be implemented as a function rather than a task ie :
property name=foo value=${xmlpeek( 'somefile.xml',
'\\somexpathexpr'} /
I think there will probably be a number of borderline cases where its
uncertain whether a given piece of functionality should be a
task or a
function.
Ian
I didn't realise xmlpeek was on the chopping block. Any particular
reason?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Monday, 8 December 2003 8:47 AM
To: Scott Hernandez; [EMAIL PROTECTED]
Subject: Re: [nant-dev] SUMMARY: Expression Syntax
Good point about side-effects. This does paint a clear
distinction.
But
then
you get tasks like xmlpoke, with no corresponding xmlpeek;
this might
make the user search around for the expression/function to use, or
even assume that this functionality does not exist.
You're right. Perhaps xmlpeek should stay.
I'm inclined to give this a day or two to stew, commit the
changes to
the head, if there are no serious issues. We doc, write
unit tests,
and do a release with expression support in a week or less.
That would be great!
We can also put a switch in our config section, and a command line
option, to turn it off, as you have suggested.
I'll implement this in EE-patches + I'll write some html docs
and make test2 release for developers when I'm ready. When
it's ok we'll move the patches to the main trunk. Ok?
Jarek
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us
help YOU! Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
--
Ian MacLean, Developer,
ActiveState, a division of Sophos
http://www.ActiveState.com
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Expression Support
Hi folks, I'm wondering if anyone has looked into building expression support into NAnt. For example, it would be cool to be able to do this: echo message=Hello World! unless=mood == 'bad' / I've been doing some digging and it looks like the path of least resistance for implementing something like this would be around the ExpandProperties method of the PropertyDictionary - so before the validators kick in, because they would reject an expression like this, so it needs to be evaluated before then. All I need now is a good pattern for expression parsing and evaluation :) - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Licensing
Hi Brant, Good scenarios. In the first one, you have to really ask why someone might want to do this, you might consider it if you were building a commercial product to support application development (say a new SCC system) and you wanted to offer NAnt users very good integration by shipping a bunch of tasks for this purpose. I'm not sure where I stand on the other two scenarios - so I'll refrain from making a generalised judgement. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Brant Carter [mailto:[EMAIL PROTECTED] Sent: Saturday, October 11, 2003 3:03 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] Licensing I think we should ask ourselves what types of uses we would want NAnt to be available to. Here are two scenarios. [1] A commerical company wants to release a custom task and charge money for it. Do we want to allow this? [2] A commerical company wants to distribute a customized version of NAnt as part of its software package (ie: A compiler company, IDE developer) and charge money for the entire package. Do we want to allow this? [3] A company creates a large software package that requires it to be built by the end customer. Are they allowed to distribute NAnt to do this? What if they modified NAnt in some way? brant ... _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Licensing
+1 for BSD. But lets post it up here for everyones reference: license Copyright (c) 2003, NAnt Project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the NAnt project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. /license I have one question about the wording though. The section Redistribution and USE (my emphasis) in source and binary forms. Does this mean that if I build a set of tasks and compile them into a separate assembly, but don't ship the NAnt libraries along with them (I assume the people I am sending to already have them) I still have to ship this license? Its not a major issue because I don't intend to profit from the libraries - but its just one more thing I have to put in the bundle (I want to be legally covered). - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2003 2:18 AM To: Ian MacLean; Stefan Bodewig Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Licensing - Original Message - From: Ian MacLean [EMAIL PROTECTED] To: Stefan Bodewig [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 5:54 PM Subject: Re: [nant-dev] Licensing Thanks for the info Stefan, I tend to agree with you re FSF and associated philosophy. There sould be no reason we can't get the licencing change in for the next release - assuming we can deal with any copyright holder issues. So now we need to make the official dicision as to which licence. I'm leaning towards BSD - what are everyone elses thoughts ? I would also prefer BSD, unless there's a slight chance that Apache is going to accept .NET projects :-) Gert --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAnt and Ant (was: Ready to tackle next release)
I'm not sure how copyright is determined, is it just code contribution? I really like the BSD-style licenses, they don't seem to raise as many alarm bells with organisations and from what I gather Microsoft's shared source license is similar - but I am no lawyer. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:02 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release) I would say that we should just leave the old code licensed under the old license (not change any prev. distribution that is). Then we will go forward with the new releases under the new license (since we are still pre-1.0). At this point the copyright holders number just a few. I feel like we should probably keep this number down, but above 1; we really need to keep good track of who these people are, and how to contact them just for these types of reasons. As for libs that are gpl'd, I think we can get around this. It just means we need to remove it from the dist and require a sep download from the real source. There are a few other small changes so we don't step over our license boundaries, but I think it manageable. - Original Message - From: Philip Nelson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 10:50 AM Subject: Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release) Well, to be honest : I don't have a clue ... That's perhaps why we're still stuck with the GPL license :-) I am pretty sure the copyright holder can do whatever they want, so long as they aren't bound to the gpl by other source code or libraries in the application. NAnt may be bound to the gpl because of things like the sharpcvslib. There's also the issue of source code that may have been copied. Does anybody know where all the source comes from? I did have a quick look at the licensing stuff, and to me it seems like a BSD-style license is the most open license ... I would summarize it as do want you want with this code, and you can't sue me with an unwritten correlary of I don't want your crummy enhancements to my code. It is definately my preference to use BSD or Apache licenses. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAnt Designer Support
Hi Nick, That's far enough. Good documentation is essential and would probably be required as a design step of this kind of stuff anyway - gotta have good practices before you can wrap them up in an IDE! - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Nick Varacalli [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 07, 2003 1:05 PM To: [EMAIL PROTECTED] Subject: RE: [nant-dev] NAnt Designer Support I would love designer support in Nant. I'm not big on XML, it's lots of angle brackets to me. I'm really into using and writing rich UIs. However, as the person managing the nightly build, and the person evangelizing Nant to my co-workers, I think that documentation is more important. Besides being an introduction to Nant, the documentation is also many developers' introduction to automated builds. Specifically: * Full, verbose documentation for each task. As a build writer, I want/need to know about every corner case, limitation, and feature of every task. I need to know why the build behaves the way it does. * Numerous task based examples within the documentation. Include answers to FAQs from the dev and user list. * XML schema, including sub-elements. Instructions on how to get intellisense working with .build files. * More example build files. Every task and attribute should have at least one example if at all possible. * Best practices documentation on how to manage large / complex build files. Building diverse projects across multiple departments with shared code, 3rd party open source code, 3rd party binaries, build notifications, logging is difficult. (If anyone has any suggestions on this, I'm all ears. We have about 200K worth of build files so far, and have only about 1/10th of our projects in the daily build.) * Documentation on how to separate developer build and automated build. * Documentation on how to integrate with Visual Studio.Net tools menu, and other little tips and tricks. Just my $0.02. Nick Varacalli -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Hernandez Sent: Sunday, October 05, 2003 14:23 To: [EMAIL PROTECTED] Subject: Re: [nant-dev] NAnt Designer Support Mitch, Yeah, it would be nice to put together a real-time chat with a whiteboard. Instead though we could post images and storyboards about the user stories for this idea. I think I understand what is driving this but part of my ambiguity is not knowing the user base. It would be great to support all types of users, but really this tool, along with Ant, requires someone who has a good grasp of xml and the ability to read the docs. If I had an option of where to put resources at this point I would emphasize getting the docs into a more usable and easier to read format, then make sure we had good error messages for validation and an accurate xml schema def. for all tasks. To that end I have been starting to beef up our user help (html stuff generated from ndoc) with more sub-element information and better index. I had already been working on the nantschema task and working through the information we generate for exception on validation and xml loading. I think this is a great idea, but given the resources we have available to work on NAnt, it seems unrealistic that we will have time to work on this for the next few months. On the other hand, if someone wanted to do it, we would be happy to take patches :) - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: Scott Hernandez [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, October 05, 2003 3:05 AM Subject: RE: [nant-dev] NAnt Designer Support Hi Scott, The driver for this kind of functionality would be orientated more at the end user who has been charged with setting up an automated build. With that in mind I think the solution might possibly consist of a few layers: Tools (e.g. NAntpad) NAnt Designers NAnt / NAnt DOM We already have NAnt. What I am suggesting is that as part of the NAnt distribution (or possibly a side project) we start building a series of designers - where designers are just UI bits which can provide a view of an XML element representing a NAnt task. Other tools (i.e. not part of the NAnt distribution) would use these designers to construct their own interfaces. So, for example when someone using NAntpad (I'm just using NAntpad as an example here) uses that particular interface to modify the settings on a task, the NAnt designer can be invoked to provide the interface. Tool designers could choose to override the designer if they wish
RE: [nant-dev] [Fwd: Ready to tackle next release]
So would we preload some like it does now when an assembly with tasks is dropped into the same directory as NAnt.exe? That would be useful too. For each buildable unit I tend to take a snapshot of NAnt and any custom tasks and drop it into a tools directory. That way I'm not tied to the version of NAnt (and its associated configuration) that is on the machine. It helps quite a bit when you are reusing build servers for multiple projects. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 1:19 PM To: Stefan Bodewig Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] Interesting. I think we can easily do the equivalent for NAnt by means of a loattypes task similar to the loadtasks we have already. We already discover referencable datatypes so adding attribute based detection of filters and or anything else shouldn't be a big change. Ian Stefan Bodewig wrote: On Tue, 7 Oct 2003, Gert Driesen [EMAIL PROTECTED] wrote: For third party filterreaders only the first notation is supported, ofcourse. in Ant 1.5, that is. With Ant 1.6beta things have changed dramatically. http://ant.apache.org/manual-1.6beta/CoreTypes/custom-progra mming.html for the short version of something we need to explain in more detail before the beta can become 1.6final. Stefan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [Fwd: Ready to tackle next release]
Awesome! I'll do a fetch on the CVS repository tomorrow. Does anyone
know if SourceForge has cut over to the live copy of the CVS repository
for anonymous access yet?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 5:22 PM
To: Ian MacLean; Mitch Denny
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
I don't think we should rush a task in ...
However, I agree that we shouldn't wait until support for
filterchains is added. But if we add such a task to NAnt
core, we should at least support both filtersets and filesets ...
I already ported the base classes for filtersets from Ant
(NAnt.Core.Types.FilterSet(Collection) and
NAnt.Core.Types.Filter(Collection)) ... these are available
in cvs now ...
so it shouldn't really be hard to add this to your replace
task ... I'll look into adding support for filtersets to the
copy and move tasks later (probable tomorrow or so)
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Mitch Denny [EMAIL PROTECTED]
Cc: Gert Driesen [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 4:25 AM
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
+1, mainly because I've just found a use for it in our
linux build. We
need to create a nant shell script that contains the full
path to the
just built NAnt.exe which we won't know till we build it.
So it would be
a prime candidate for a use of the replace task.
Ian
The touch / task could possibly be modified to do it. But replace
would possibly be more intuitive for new users than using a filter
chain. It could probably support filter chains anyway - it
might also be
cool to have a generic filter / task too. Next release :)
I'm thinking that we could put the replace task in now
since it would be
useful, and then modify its implementation when chaining support is
added.
What do you all think?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 2:03 AM
To: Gert Driesen
Cc: Mitch Denny; [EMAIL PROTECTED]
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
I just noticed that Ant still has both the replaceTask and
the filtersets in copy/zip etc. I'm sure you could accomplish
an in-place replace with filtersets but I can see a task
called replace being easier for new uesrs to deal with than
filterchains.
Ian
http://ant.apache.org/manual/CoreTasks/replace.html
Gert Driesen wrote:
to be honest, I'm not sure about that one ... If
necessary we could
ofcourse create a task for that, but I was just saying we don't
necessary need one ... didn't really give it much thought yet ...
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: Mitch Denny [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 1:53 PM
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
What if you want to replace strings in a file in place ? -
ie without
copying/moving the file
Ian
Gert Driesen wrote:
something like that yes :-)
but instead of having a separate task for that
purpose, filterchain
support
would be added to existing tasks (like copy, zip, ...)
Gert
- Original Message -
From: Mitch Denny [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 12:15 PM
Subject: RE: [nant-dev] [Fwd: Ready to tackle next release]
So in implementation it would work like this:
[FilterChain(filterchain)]
public FilterChain FilterChain {
...
}
Then in the execute task:
StreamReader reader = new StreamReader(...);
StreamWriter writer =
new StreamWriter(...); this.FilterChain.Filter(reader, writer);
Or something like that.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com
RE: [nant-dev] [Fwd: Ready to tackle next release]
Actually, are you guys working off some branch, because I can't see the
XmlPeek or XmlPoke tasks in there either. Is it BRANCH-083?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 5:22 PM
To: Ian MacLean; Mitch Denny
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
I don't think we should rush a task in ...
However, I agree that we shouldn't wait until support for
filterchains is added. But if we add such a task to NAnt
core, we should at least support both filtersets and filesets ...
I already ported the base classes for filtersets from Ant
(NAnt.Core.Types.FilterSet(Collection) and
NAnt.Core.Types.Filter(Collection)) ... these are available
in cvs now ...
so it shouldn't really be hard to add this to your replace
task ... I'll look into adding support for filtersets to the
copy and move tasks later (probable tomorrow or so)
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Mitch Denny [EMAIL PROTECTED]
Cc: Gert Driesen [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 4:25 AM
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
+1, mainly because I've just found a use for it in our
linux build. We
need to create a nant shell script that contains the full
path to the
just built NAnt.exe which we won't know till we build it.
So it would be
a prime candidate for a use of the replace task.
Ian
The touch / task could possibly be modified to do it. But replace
would possibly be more intuitive for new users than using a filter
chain. It could probably support filter chains anyway - it
might also be
cool to have a generic filter / task too. Next release :)
I'm thinking that we could put the replace task in now
since it would be
useful, and then modify its implementation when chaining support is
added.
What do you all think?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 2:03 AM
To: Gert Driesen
Cc: Mitch Denny; [EMAIL PROTECTED]
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
I just noticed that Ant still has both the replaceTask and
the filtersets in copy/zip etc. I'm sure you could accomplish
an in-place replace with filtersets but I can see a task
called replace being easier for new uesrs to deal with than
filterchains.
Ian
http://ant.apache.org/manual/CoreTasks/replace.html
Gert Driesen wrote:
to be honest, I'm not sure about that one ... If
necessary we could
ofcourse create a task for that, but I was just saying we don't
necessary need one ... didn't really give it much thought yet ...
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: Mitch Denny [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 1:53 PM
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
What if you want to replace strings in a file in place ? -
ie without
copying/moving the file
Ian
Gert Driesen wrote:
something like that yes :-)
but instead of having a separate task for that
purpose, filterchain
support
would be added to existing tasks (like copy, zip, ...)
Gert
- Original Message -
From: Mitch Denny [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 12:15 PM
Subject: RE: [nant-dev] [Fwd: Ready to tackle next release]
So in implementation it would work like this:
[FilterChain(filterchain)]
public FilterChain FilterChain {
...
}
Then in the execute task:
StreamReader reader = new StreamReader(...);
StreamWriter writer =
new StreamWriter(...); this.FilterChain.Filter(reader, writer);
Or something like that.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
RE: [nant-dev] [Fwd: Ready to tackle next release]
Atleast :( Are the nightly tarballs of the repository happening or are they lagging too? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 9:33 PM To: Mitch Denny; Ian MacLean Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] No we're working on the main branch, but I noticed that, at times, anoncvs is more than 5 days behind ... Gert - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, October 06, 2003 1:12 PM Subject: RE: [nant-dev] [Fwd: Ready to tackle next release] Actually, are you guys working off some branch, because I can't see the XmlPeek or XmlPoke tasks in there either. Is it BRANCH-083? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 5:22 PM To: Ian MacLean; Mitch Denny Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] I don't think we should rush a task in ... However, I agree that we shouldn't wait until support for filterchains is added. But if we add such a task to NAnt core, we should at least support both filtersets and filesets ... I already ported the base classes for filtersets from Ant (NAnt.Core.Types.FilterSet(Collection) and NAnt.Core.Types.Filter(Collection)) ... these are available in cvs now ... so it shouldn't really be hard to add this to your replace task ... I'll look into adding support for filtersets to the copy and move tasks later (probable tomorrow or so) Gert - Original Message - From: Ian MacLean [EMAIL PROTECTED] To: Mitch Denny [EMAIL PROTECTED] Cc: Gert Driesen [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, October 06, 2003 4:25 AM Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] +1, mainly because I've just found a use for it in our linux build. We need to create a nant shell script that contains the full path to the just built NAnt.exe which we won't know till we build it. So it would be a prime candidate for a use of the replace task. Ian The touch / task could possibly be modified to do it. But replace would possibly be more intuitive for new users than using a filter chain. It could probably support filter chains anyway - it might also be cool to have a generic filter / task too. Next release :) I'm thinking that we could put the replace task in now since it would be useful, and then modify its implementation when chaining support is added. What do you all think? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 2:03 AM To: Gert Driesen Cc: Mitch Denny; [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] I just noticed that Ant still has both the replaceTask and the filtersets in copy/zip etc. I'm sure you could accomplish an in-place replace with filtersets but I can see a task called replace being easier for new uesrs to deal with than filterchains. Ian http://ant.apache.org/manual/CoreTasks/replace.html Gert Driesen wrote: to be honest, I'm not sure about that one ... If necessary we could ofcourse create a task for that, but I was just saying we don't necessary need one ... didn't really give it much thought yet ... Gert - Original Message - From: Ian MacLean [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED] Cc: Mitch Denny [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, October 05, 2003 1:53 PM Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] What if you want to replace strings in a file in place ? - ie without copying/moving the file Ian Gert Driesen wrote: something like that yes :-) but instead of having a separate task for that purpose, filterchain support would be added to existing tasks (like copy, zip, ...) Gert - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, October 05, 2003 12:15 PM Subject: RE: [nant-dev] [Fwd: Ready to tackle next release] So
RE: [nant-dev] NAnt Designer Support
Hi Scott, The driver for this kind of functionality would be orientated more at the end user who has been charged with setting up an automated build. With that in mind I think the solution might possibly consist of a few layers: Tools (e.g. NAntpad) NAnt Designers NAnt / NAnt DOM We already have NAnt. What I am suggesting is that as part of the NAnt distribution (or possibly a side project) we start building a series of designers - where designers are just UI bits which can provide a view of an XML element representing a NAnt task. Other tools (i.e. not part of the NAnt distribution) would use these designers to construct their own interfaces. So, for example when someone using NAntpad (I'm just using NAntpad as an example here) uses that particular interface to modify the settings on a task, the NAnt designer can be invoked to provide the interface. Tool designers could choose to override the designer if they wish but this approach would allow task developers to put together usable UI for others to manipuate their tasks with. Tools could add additional value by providing things like wizards which allow the end user to put together solutions to common problems. For example building a VS.NET project, manipulating AssemblyVersionInfo files, updating dependencies etc. Pity we can't get a whiteboard session going :) - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 5:04 AM To: [EMAIL PROTECTED] Subject: Re: [nant-dev] NAnt Designer Support I'm not sure what user experience this would provide. What kind of designer would the nant stuff look like? Would it be like the xsd editor, or database schema editor, with something like a flow diagram of tasks? Would it be a buff'd up tree control, like the vsnet addin is now? I understand that having a designer based solution would allow for much more flexibility and extensibility in the future, but it seems a little much considering we are working on getting a 1.0 release of the core functionally out. I'm really interested in hearing how this stuff would work, and who this is targeted at, but I just don't think I see it yet. - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 29, 2003 4:31 AM Subject: RE: [nant-dev] NAnt Designer Support Hi Scott, We wouldn't need to modify the existing code base much other than decorating tasks (and sometimes their properties/attributes with attributes. The idea behind the design time attributes is not to create a tool inside the NAnt distribution itself, but rather support the development editors like NAntpad. Kinda like the way the component designer features in the .NET framework work in VS.NET and WebMatrix. The design time tool would reflect over the task class libraries looking for classes decorated with the designer attribute. When a task is selected from a build file the type pointed to by the designer attribute is created and a method is invoked which returns a UI object which can be used to build the XML node. This creation method would have some contextual information passed to it like which OS/UI toolkit it needs to support. If the designer doesn't support that environment then the tool (e.g. NAntpad would gracefully downgrade to its basic capabilities. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [Fwd: Ready to tackle next release]
Hi Ian/Gert, The current drop of the code I have doesn't work with a fileset, although I guess it could easily be modified to do so. How long do I have until the 0.8.4 feature freeze starts? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Sunday, October 05, 2003 7:07 PM To: Gert Driesen Cc: Mitch Denny; [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] Same as the Ant replace task. Replace tokens in a text file ( or fileset of text files ) Ian Gert Driesen wrote: Mitch, Can you freshen up my memory again, and tell me what this task is supposed to do ? Thanks, Gert - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 03, 2003 7:05 AM Subject: RE: [nant-dev] [Fwd: Ready to tackle next release] It would be great to see NUnit 2.1 plugged in. I'd also like to see 1.1 as the default. Ian - do you think it would be possible to get the ReplaceTask into the core if I can make it more robust? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [nant-dev] [Fwd: Ready to tackle next release] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [Fwd: Ready to tackle next release]
Hrm, yeah I can see how that would be a better solution. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Sunday, October 05, 2003 7:38 PM To: Ian MacLean Cc: Mitch Denny; [EMAIL PROTECTED] Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] I think we should have a more generic solution for this, like Ant has with its support for FilterChains ... Scott has put this on his to-do list (and I updated the NAnt to-do list in cvs with this information), but he's very busy so I'm not sure when this will be available ... Gert - Original Message - From: Ian MacLean [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED] Cc: Mitch Denny [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, October 05, 2003 11:06 AM Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] Same as the Ant replace task. Replace tokens in a text file ( or fileset of text files ) Ian Gert Driesen wrote: Mitch, Can you freshen up my memory again, and tell me what this task is supposed to do ? Thanks, Gert - Original Message - From: Mitch Denny [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 03, 2003 7:05 AM Subject: RE: [nant-dev] [Fwd: Ready to tackle next release] It would be great to see NUnit 2.1 plugged in. I'd also like to see 1.1 as the default. Ian - do you think it would be possible to get the ReplaceTask into the core if I can make it more robust? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [nant-dev] [Fwd: Ready to tackle next release] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [Fwd: Ready to tackle next release]
The touch / task could possibly be modified to do it. But replace
would possibly be more intuitive for new users than using a filter
chain. It could probably support filter chains anyway - it might also be
cool to have a generic filter / task too. Next release :)
I'm thinking that we could put the replace task in now since it would be
useful, and then modify its implementation when chaining support is
added.
What do you all think?
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 2:03 AM
To: Gert Driesen
Cc: Mitch Denny; [EMAIL PROTECTED]
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
I just noticed that Ant still has both the replaceTask and
the filtersets in copy/zip etc. I'm sure you could accomplish
an in-place replace with filtersets but I can see a task
called replace being easier for new uesrs to deal with than
filterchains.
Ian
http://ant.apache.org/manual/CoreTasks/replace.html
Gert Driesen wrote:
to be honest, I'm not sure about that one ... If necessary we could
ofcourse create a task for that, but I was just saying we don't
necessary need one ... didn't really give it much thought yet ...
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: Mitch Denny [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 1:53 PM
Subject: Re: [nant-dev] [Fwd: Ready to tackle next release]
What if you want to replace strings in a file in place ? -
ie without
copying/moving the file
Ian
Gert Driesen wrote:
something like that yes :-)
but instead of having a separate task for that purpose, filterchain
support
would be added to existing tasks (like copy, zip, ...)
Gert
- Original Message -
From: Mitch Denny [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, October 05, 2003 12:15 PM
Subject: RE: [nant-dev] [Fwd: Ready to tackle next release]
So in implementation it would work like this:
[FilterChain(filterchain)]
public FilterChain FilterChain {
...
}
Then in the execute task:
StreamReader reader = new StreamReader(...); StreamWriter writer =
new StreamWriter(...); this.FilterChain.Filter(reader, writer);
Or something like that.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] RE: RE: [Fwd: Ready to tackle next release]
Which version of the framework to run on is going to be a perennial problem. There are going to be features in the upcoming version of the .NET runtime which, if you guys choose to take advantage of them might force a fork in the code bases - I'm not sure what the Mono guys have plannned as far as supporting generics goes. I know of a number of organisations that are planning on being on 1.0 for atleast the next 12 months - in twelve months its likely that NAnt will need to be starting to build in support for upcoming versions of the framework, it might just been too hard to manage in one code base. Unfortunately I know. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Saturday, October 04, 2003 3:19 PM To: James C. Papp Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] RE: RE: [Fwd: Ready to tackle next release] I've been testing Nunit 2.1 and it seems ok - except for needing to re-compile all 2.0 version tests. We're waitning on the NUnit team for a response to a number of queries about shipping 2.1. With luck we should have it in 0.9. The problem with building against 1.1 is that a 1.1 build will not work on 1.0 whereas a 1.0 one will work fine on both. If everyone has moved to 1.1 then thats not a problem but I'm not sure thats the case. The other option is to ship two builds - one for each platform. Ian It would be great to see NUnit 2.1 plugged in. I'd also like to see 1.1 as the default. Ian - do you think it would be possible to get the ReplaceTask into the core if I can make it more robust? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [nant-dev] [Fwd: Ready to tackle next release] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] RE: RE: [Fwd: Ready to tackle next release]
Hi Ian, True, right now its not a real issue provided NUnit 2.1 will happily compile onto version 1.1 of the framework. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Sunday, October 05, 2003 1:41 AM To: Mitch Denny Cc: James C. Papp; [EMAIL PROTECTED] Subject: Re: [nant-dev] RE: RE: [Fwd: Ready to tackle next release] Totally. I'm really looking forward to using generics when whitbey ships for example. However right now the codebase isn't usihng any 1.1 specific features. So I see no reason to exclude 1.0 users until we need specific features in a higher version. I can recall reading the same types of dicussions on the mailing lists for Java projects ( Ant and JEdit to be specific ). It was even worse with java as there was a large amoutn of change between early versions. Wheras 1.1 of the framework could almost be considerd a bug fix release in terms of breaking changes. I don't think we'll need to fork the codebase - I just think that when we do force a newer framework version people on an older platform will just use an older NAnt until they upgrade. Ian Mitch Denny wrote: Which version of the framework to run on is going to be a perennial problem. There are going to be features in the upcoming version of the .NET runtime which, if you guys choose to take advantage of them might force a fork in the code bases - I'm not sure what the Mono guys have plannned as far as supporting generics goes. I know of a number of organisations that are planning on being on 1.0 for atleast the next 12 months - in twelve months its likely that NAnt will need to be starting to build in support for upcoming versions of the framework, it might just been too hard to manage in one code base. Unfortunately I know. - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Saturday, October 04, 2003 3:19 PM To: James C. Papp Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] RE: RE: [Fwd: Ready to tackle next release] I've been testing Nunit 2.1 and it seems ok - except for needing to re-compile all 2.0 version tests. We're waitning on the NUnit team for a response to a number of queries about shipping 2.1. With luck we should have it in 0.9. The problem with building against 1.1 is that a 1.1 build will not work on 1.0 whereas a 1.0 one will work fine on both. If everyone has moved to 1.1 then thats not a problem but I'm not sure thats the case. The other option is to ship two builds - one for each platform. Ian It would be great to see NUnit 2.1 plugged in. I'd also like to see 1.1 as the default. Ian - do you think it would be possible to get the ReplaceTask into the core if I can make it more robust? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [nant-dev] [Fwd: Ready to tackle next release] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] [Fwd: Ready to tackle next release]
It would be great to see NUnit 2.1 plugged in. I'd also like to see 1.1 as the default. Ian - do you think it would be possible to get the ReplaceTask into the core if I can make it more robust? - Mitch Denny - [EMAIL PROTECTED] - http://www.monash.net - +61 (414) 610141 - -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [nant-dev] [Fwd: Ready to tackle next release] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAnt Designer Support
Hi Scott,
We wouldn't need to modify the existing code base much other than
decorating tasks (and sometimes their properties/attributes with
attributes. The idea behind the design time attributes is not to create
a tool inside the NAnt distribution itself, but rather support the
development editors like NAntpad. Kinda like the way the component
designer features in the .NET framework work in VS.NET and WebMatrix.
The design time tool would reflect over the task class libraries looking
for classes decorated with the designer attribute. When a task is
selected from a build file the type pointed to by the designer attribute
is created and a method is invoked which returns a UI object which can
be used to build the XML node. This creation method would have some
contextual information passed to it like which OS/UI toolkit it needs to
support.
If the designer doesn't support that environment then the tool (e.g.
NAntpad would gracefully downgrade to its basic capabilities.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 12:33 PM
To: [EMAIL PROTECTED]
Subject: Re: [nant-dev] NAnt Designer Support
I would be interested in this if it could be included without
altering the core code (much). What do you think the
nantdesigner would look like?
What benefits would this really give? It sounds like an
interesting idea, but don't the vsnet addin, nantpad and
other tools supply this type of support already? Why go with
Designer stuff?
I'm interested in hearing more... :)
- Original Message -
From: Mitch Denny [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 28, 2003 3:50 PM
Subject: [nant-dev] NAnt Designer Support
Hi folks,
I'm sure most of you are aware of NAntpad by Anthony Brown.
Well, his
work has gotten me thinking about designer support in
NAnt and whether
it would be feasible to try to do it in NAnt.
We could define a designer factory which would spit out
the UI classes
depending on what platform NAnt was being used on (since
WinForms isn't
everywhere). You could hook up the designer factory to each task.
[NAntDesigner(typeof(NAnt.Core.Tasks.Design.XmlPokeTaskDesigner)]
public class XmlPokeTask : NAnt.Core.Task {
...
}
To get some level of reuse in the designers, the designer attributes
could also be marked against individual properties. I see this being
useful for things like a regular expression builder, XPath
expression
builder and elephant in the living room example - file/directory
browser.
Reason: One of the most common complaints I hear about NAnt
is that its
too hard to use, even though it oozes power and
flexibility. A lot of
people run with Visual Build from Kinook (another fine
product), but I
think some kind of designer support would give NAnt the edge.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAnt Designer Support
Hi folks,
I'm sure most of you are aware of NAntpad by Anthony Brown. Well, his
work has gotten me thinking about designer support in NAnt and whether
it would be feasible to try to do it in NAnt.
We could define a designer factory which would spit out the UI classes
depending on what platform NAnt was being used on (since WinForms isn't
everywhere). You could hook up the designer factory to each task.
[NAntDesigner(typeof(NAnt.Core.Tasks.Design.XmlPokeTaskDesigner)]
public class XmlPokeTask : NAnt.Core.Task {
...
}
To get some level of reuse in the designers, the designer attributes
could also be marked against individual properties. I see this being
useful for things like a regular expression builder, XPath expression
builder and elephant in the living room example - file/directory
browser.
Reason: One of the most common complaints I hear about NAnt is that its
too hard to use, even though it oozes power and flexibility. A lot of
people run with Visual Build from Kinook (another fine product), but I
think some kind of designer support would give NAnt the edge.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
