Hello, I missed blogging this, not because was not important, but because right now, I’m attending RailsConf in Baltimore.
Posted on Jun 8, 2010
Posted on Mar 7, 2010
win32console 1.3.0.beta2 released
I’ve just released a second beta of win32console gem.
What’s new?
Only two new things: STDERR is now redirected (wasn’t before) and the addition of ECHO on/off functionality thanks to Justin Love
How to install?
You can read previous post with installation instructions, since it is a prerelease, please test it and report me any new issue here
Known Issues
AutoSpec is known to have problems, but is not an issue of win32console, as you can read in GH-3
Cheers!
Posted on Mar 7, 2010
mongrel_service 0.4.beta3 released
This is a followup to my previous post
I’ve pushed to RubyGems a version 0.4.beta3, you can access it from here
What’s new?
Bugsfixes, thanks to sinclair that fixed a couple of regressions due the refactoring and removal of win32-service dependency.
Please read the previous post about install and usage instructions. Thank you.
Posted on Jan 1, 2010
mongrel_service 0.4.beta2 released
I think nobody expected this project hit the 4 years mark… guess I didn’t expected it either!
Posted on Dec 29, 2009
win32console 1.3.0 prerelease
I mentioned in previous post that I was working in a updated version of win32console.
So, just pushed to Gemcutter the prerelease version (_beta1_) so you guys can test with your current Cucumber/RSpec scenarios.
How to install prerelease versions?
All the RubyGems 1.3.x series sport the feature to prerelease gem installations. I recommend update to RubyGems 1.3.5 first in case you haven’t already, and proceed to install the gem:
gem install win32console --prerelease
The process will install version 1.3.0.beta1, which will be automatically available to any require done by Cucumber or RSpec.
What changed on this release?
As I mentioned before, there are a couple of changes required to support 1.9. On this release, I got rid of hardcoded translation tables used to convert codepages from input/output consoles.
How this affects me?
It will only affect you if you use accented characters in the output. If you do, then you should verify that your console codepage supports them. There is more information in the Cucumber wiki troubleshooting page
Now that text is sent transparently to the output, you have the control to feed the stream with different encodings and ensuring the output matches the console codepage.
A working example of this is located here
Please test it out so a formal 1.3.0 release can be done the upcoming days.
Cheers!