Hi, On Thu, Oct 27, 2011 at 2:47 AM, Dominik Guder <o...@guder.org> wrote: > Am 26.10.2011 23:54, schrieb Ryan Boggs: >> Hey Dominik, >> >> On Wed, Oct 26, 2011 at 2:35 PM, Dominik Guder<o...@guder.org> wrote: >>> Hi Ryan, >>> >>> +1 for github. >> How many responses should we collect before we make an official >> decision on this? :) > > Just count :) I don't expect many votes for others like bitbucket. Ok :) > >>> >>> Other proposals: >>> - Color output. Red for errors, yellow for warning and green for >>> sucessfull build. I added this to my own net_2.0 build and I'm addicted >>> to this easily identifying Green successfull build message. >> Hehehe, That's a good idea. I actually like that. >> >> This would be good for Windows but we should take care in *nix systems >> as some terminal emulators do not support color. > > A short look at mono's BCL implementation showed that Console.ForeGround > is basically is implemented. But this must be checked for sure. > Maybe we can check this with Log4Net team since they are providing the > ColoredConsoleAppender. (not for Mono currently) I've seen Mono use Console.Foreground on a *nix machine just fine using Boo's interactive shell (booish) just fine. The problem that I saw was once the user gets out of booish when using certain terminal types, the output would no longer print to the screen. All I am saying is to keep that in mind. I still like this idea. :) > >>> >>> - fix/polish commandline handling: >>> - remove anoying ":" as separator, this prevents you from using tab >>> completion in cmd window (even WiX did this with 3.5 release) >>> - add double dash as parameter prefix (as used at gnu tools) at least >>> for --help and --version >> One thing I would like to investigate is implementing something like >> Mono.Options instead of the home grown command args parser. I've used >> it in personal projects and it was pretty cool. That may address your >> concern here. > > This would be fine. But we also check how we can provide backwards > compatibility. I think backward compatibility (ie: jkeeping "-t::net-2.0" while adding something like "-t net-2.0") is definitely possible. But now that I am reading the source code, I'm not 100% sure it would work on .net 2.0. I'll look into it further...
Thanks, Ryan > > So far Dominik > > -- > The answer to the great question of life, > the universe and everything is 42 (Douglas Adams) > > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > nant-developers mailing list > nant-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
