Re: [nant-dev] Humbly submitted for your echoing pleasure. :)
Looks good to me. I'll commit this code later today. There have been logging discussions already; but that was almost 6 months ago, so bring it on :). I'm all for a revamp, esp. re-using work already done by log4net or some other existing system. http://www.mail-archive.com/nant-developers@lists.sourceforge.net/msg00492.h tml - Original Message - From: Brian Deacon To: [EMAIL PROTECTED] Sent: Wednesday, January 22, 2003 8:04 AM Subject: [nant-dev] Humbly submitted for your echoing pleasure. :) This allows the following: echo message=Hello / echoHello/echo echo This is some stuff. This is some more stuff that I want echoed on another line. /echo echo message=ValidationException This triggers a ValidationException because it has both inline content and the message attribute. /echo echo/ !-This causes a blank message to be echoed just because I thought it was silly to not allow someone to do so if they really want to. -- And I think I got the curly braces and non-tabs right this time. J Also, the use of ValidationException was my best guess as to the appropriate exception class to use. Please someone inform me if this was a bad call on my part. Any questions, critiques, suggestions, or hey go and change this before we include it are of course welcome. Brian Deacon p.s. - For my next trick, I saw that revamping the logging infrastructure was on the todo list. Is anybody already on this? I was gonna add support for a LogLevel enum, including -quiet, -debug, as well as -verbose that we have now. Any thoughts? Am I walking into an already-discussed consensus on how this ought to work? --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] documentation error
There's an HTML error at the bottom of the page describing the 'nunit' task (http://nant.sourceforge.net/help/tasks/nunittask.html). This error occurs in both IE 6.0 and Mozilla (Phoenix). It looks like the page wants to document an attribute of the nunit task, but it got munged somehow? Anyway. Does the project have someone whose job it is to specifically address documentation issues? If not, I'd be happy to help out. Jeffrey __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] documentation error
Hi Jeffrey, It looks like this has been fixed in cvs. There is no help/documenter person, but if you would like to help out, there is plenty to do :) And we would really appreciate it. The number one thing on my list is to convert the docs here (http://nant.sourceforge.net/help/index.html; excluding the task ref) into xml so we can more easily work with it. Then maybe we can generate more formats of help (like a chm or pdf). Currently these documents exist in a proprietary format (fogdesk, I think) and are pretty hard to do anything with but generate html from. If you need any more explanation, I can help out, or someone on the list will be able to fill in the details. Thanks, Scott - Original Message - From: Jeffrey McManus [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 22, 2003 10:57 AM Subject: [nant-dev] documentation error There's an HTML error at the bottom of the page describing the 'nunit' task (http://nant.sourceforge.net/help/tasks/nunittask.html). This error occurs in both IE 6.0 and Mozilla (Phoenix). It looks like the page wants to document an attribute of the nunit task, but it got munged somehow? Anyway. Does the project have someone whose job it is to specifically address documentation issues? If not, I'd be happy to help out. Jeffrey __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] documentation error
I'm happy to contribute as much as I can to docs; I've synched everything up with CVS and I'll start looking at them tonight. With your permission, one of things I'd like to start thinking about is a short introductory blurb/doc that introduces the concept of a build tool at a high level for experienced developers who have never used a build tool (a profile that will apply to many Microsoft tools developers, I suspect). With respect to XMLification of the docs, I've done this a few times before, and it has consistently taught me one thing -- frequently, the amount of time that developers spend managing the XML (fidding with tags, getting the elements correct, etc.) exceeds the benefits. I say this as a huge XML proponent who uses XML on a near-daily basis. But generally for documentation my watchword is make it as easy for people to contribute as possible. Whether it's in HTML, XML, or on the back of a cocktail napkin, getting good information is more important than what format it's in. Looking at your source, it looks like you're using inline XML comments already, which is great. I wonder if it would be OK, at least for now, if we just keep the HTML documentation in HTML and transform the inline XML comments into HTML/PDF/CHM/whatever, using the inline code comments emitted by the compiler? Does this sound insane? To me, this seems like it would be much less work -- at the end of the day if you want to (for example) convert HTML pages to PDF you could easily do so without bothering with an intervening XML step. One question -- what's the status of the tasks page (\nant\doc\help\tasks\index.html)? It's a dead link in the source I just checked out; is it going to be autogenned from the source at some point? Should we maybe stick a placeholder page in there until the real page is ready? Jeffrey --- Scott Hernandez [EMAIL PROTECTED] wrote: Hi Jeffrey, It looks like this has been fixed in cvs. There is no help/documenter person, but if you would like to help out, there is plenty to do :) And we would really appreciate it. The number one thing on my list is to convert the docs here (http://nant.sourceforge.net/help/index.html; excluding the task ref) into xml so we can more easily work with it. Then maybe we can generate more formats of help (like a chm or pdf). Currently these documents exist in a proprietary format (fogdesk, I think) and are pretty hard to do anything with but generate html from. If you need any more explanation, I can help out, or someone on the list will be able to fill in the details. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
