search for: chneukirchen

This is an informal poll. If you are primarily a Ruby programmer, - What was your primary language before you started coding in Ruby? Else, - What''s your current programming language of choice? I''ll start: Perl -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ting a site with 32 pages. I don''t really care about the speed (it''s ruby after all), but it should have the right complexity -- i.e. if I write a post a day, after 100 days, it should not take 100 times more than the first day. The program I used before webgen is nukumi2: http://chneukirchen.org/blog/static/projects/nukumi2.html which I left because it''s not actively developed. One cool thing about nukumi2 is that each regeneration only regenerates the minimum set of files, and it seemed very smart. So I CCed this to Chris, nukumi2''s author, maybe he can share its e...

On 3/14/06, David Holroyd <ruby-talk@badgers-in-foil.co.uk> wrote: > On Wed, Mar 15, 2006 at 02:23:04AM +0900, Mauricio Fernandez wrote: > > On Tue, Mar 14, 2006 at 09:27:14AM +0900, David Holroyd wrote: > > > On Wed, Mar 01, 2006 at 01:31:11AM +0900, Mauricio Fernandez wrote: > > > > Source code, additional information, screenshots... available at > >

I''m curious, Christian Neukirchen has released test/unit[1] that seems to mirror much of RSpec, but built on Test::Unit, so in some ways less brittle from a Rails-integration perspective, and also allowing you to mix the two together as appropriate. So, has anyone made an informed comparison? I''m new enough that I don''t really know the finer points yet. The syntax is

This release upgrades the included Ruby to version 1.8.4 and will become the final 1.0 release of Instant Rails if no serious problems are found. Instant Rails is a one-stop Rails runtime solution containing Ruby, Rails, Apache, and MySQL, all preconfigured and ready to run. No installer, you simply drop it into the directory of your choice and run it. It does not modify your system environment.

...'re using the terminal, it'll even colour the output.?? ??`testthat` draws inspiration from the xUnit family of testing packages, as well from many of the innovative ruby testing libraries, like [rspec](http://rspec.info/), [testy](http://github.com/ahoward/testy), [bacon](http://github.com/chneukirchen/bacon) and [cucumber](http://wiki.github.com/aslakhellesoy/cucumber/). I have used what I think works for R, and abandoned what doesn't, creating a testing environment that is philosophically centred in R. Version 0.6 ----------------------------------------------------------------------------...

...'re using the terminal, it'll even colour the output.?? ??`testthat` draws inspiration from the xUnit family of testing packages, as well from many of the innovative ruby testing libraries, like [rspec](http://rspec.info/), [testy](http://github.com/ahoward/testy), [bacon](http://github.com/chneukirchen/bacon) and [cucumber](http://wiki.github.com/aslakhellesoy/cucumber/). I have used what I think works for R, and abandoned what doesn't, creating a testing environment that is philosophically centred in R. Version 0.6 ----------------------------------------------------------------------------...

...you're using the terminal, it'll even colour the output. `testthat` draws inspiration from the xUnit family of testing packages, as well from many of the innovative ruby testing libraries, like [rspec](http://rspec.info/), [testy](http://github.com/ahoward/testy), [bacon](http://github.com/chneukirchen/bacon) and [cucumber](http://wiki.github.com/aslakhellesoy/cucumber/). I have used what I think works for R, and abandoned what doesn't, creating a testing environment that is philosophically centred in R. Changes in version 0.3 -----------------------------------------------------------------...

...you're using the terminal, it'll even colour the output. `testthat` draws inspiration from the xUnit family of testing packages, as well from many of the innovative ruby testing libraries, like [rspec](http://rspec.info/), [testy](http://github.com/ahoward/testy), [bacon](http://github.com/chneukirchen/bacon) and [cucumber](http://wiki.github.com/aslakhellesoy/cucumber/). I have used what I think works for R, and abandoned what doesn't, creating a testing environment that is philosophically centred in R. Changes in version 0.3 -----------------------------------------------------------------...

=== 1. Camping on Rack === I''ve just finished rewriting Camping to use Rack in the "core". I got rid of (a little less) than 1kB in camping.rb and removed lots of un-necessary files (lib/server/*.rb, fastcgi.rb & mongrel.rb). bin/camping does now only provide WEBrick, Mongrel and console-support and should only be used in development. It uses Rack::ShowExceptions to catch

I''ve been working through the book ''Beginning Ruby on Rails E-Commerce'' which is very heavy on Test Driven Development. As in, you have to write tests for scaffolding methods and validations and crap like that. And then they fail. And you KNOW its the test not the method. So you spend 2x the time writing a test that has to be adapted when requirements change. You