Ah, good point. I'll try that today and see if it meets my needs. Not sure if there is a nantcontrib list or not. I signed up for one, but haven't gotten any mail from it since I signed up. And it appears that SF is going through some issues with their mail archives, as sometimes I can get to them, but often it just errors.
Thx D Quoting Jason Diamond <[EMAIL PROTECTED]>: > You're more than welcome to add both of these features if you think you'll > need them. > > I, personally, have no problem redirecting the output to a file. And by > outputting to stdout you can always pipe that into some other tool. > > For your transform idea, you can pipe the output into MSXSL.exe or any other > XSLT processor that can read the source document from stdin. This is the > most flexible solution to me because it gives you a chance to pass custom > parameters to your XSLT processor including the kind that can then get > passed into your stylesheet. > > But don't let my opinion stop you from implementing something you need. > > Is there a nantcontrib list? Maybe I goofed, too. > > Jason > > ----- Original Message ----- > From: "Dave Sanders" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, February 04, 2003 2:25 PM > Subject: [nant-dev] SLiNgshoT request > > > > (not going to quote my previous email, since it was so long, but the long > and > > the short of it is that I got it sort of working right now.) > > > > However, I see what you mean about the SLN files not being XML. Go > figure - I > > just assumed they were since everything ELSE is XML. Ah well. > > > > But, an idea (or if it already exists in SLiNgshoT, let me know) would be > for an > > optional -style param to be passed into slingshot that specifies an XSL > file to > > run slingshot's output against. This would give folks the ability to > quickly > > tweak some things, or adjust paths, etc, after Slingshot does the bulk of > the > > work. Would be easy enough to do, just style the output before it leaves. > > > > Speaking of which, it'd be nice too to have an -output flag too. Instead > of > > piping it to a text file. Or is that by design? > > > > Both would be easy enough to add I think - and I could probably throw them > in > > there if I'm not way off base with other plans. > > > > Also, I just realized, but should this message be going to nantcontrib > list > > instead? Sorry if I goofed. > > > > thx > > D > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > Nant-developers mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/nant-developers > > > > -- SteelSphere.com - Meandering Through the Information Age ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
