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
