similar to: Routes patch w/ specs

I was reading here and there about the differences between Merb and Rails [1] and became curious about statements such as this: > It is threadsafe with configurable Mutex Locks (Routing is also > threadsafe) Having mucked with the routes system, I had this awful feeling that I don''t understand threading well enough to know if my contribution is "thread safe".

I didn''t quite see a direct answer to Matt''s question regarding running merb from SVN: http://rubyforge.org/pipermail/merb-devel/2007-July/000132.html In a merb application, is there something comparable to having rails in the vendor/ folder of a rails app? Thanks, Duane Johnson (canadaduane)

Check it out here: http://pastie.textmate.org/92610 Let me know if you have any questions. Duane Johnson (canadaduane) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/merb-devel/attachments/20070830/c808d045/attachment.html

I''ve submitted a few patches on Trac to help get Merb running under JRuby [0][1][2][3][4]. It''d be cool if any of you committers could find the time to look them over and apply/reject them. They''re mostly tiny, so it shouldn''t be too onerous. With all of these patches applied, there are still 3 spec failures. One is in the spec ''a merb mailer

Is there a simple way to bootstrap merb directly from the Subversion repository, rather than first installing it as a gem? I can do the following if I already have an old gem lying around: merb -g testapp # using an old gem cd testapp rake merb:freeze_from_svn Unfortunately, that means I''m using an old version of the generator. So for example, when I just tried this,

I''ve submitted some specs for the problem I found with parsing multipart forms. http://merb.devjavu.com/projects/merb/ticket/21 It looks like the problem is broader than I thought before. The multipart form parsing only takes the last field in the form, the others get thrown away. Luke -------------- next part -------------- An HTML attachment was scrubbed... URL:

I just had a problem that had me stumped for an hour. All of a sudden all of my view specs were failing, and I couldn''t get good troubleshooting information from the rspec output. The output from running `rake specs` was a bunch of HTML from app/views/exceptions/internal_server_error.html.erb, but there wasn''t enough info there to diagnose my problem. It just said

Following up on #190 [1], I''ve just added a simple patch that allows the manipulation of the TYPES hash from within the Merb module. Use like: Merb.add_mime_type(:png,%w[image/png]) Merb.remove_mime_type(:png) It specifically disallows the removal of the :all MimeType, since content negotiation relies on it. I''m not super wonderful at API design, so comments and

So this has been an idea ever since Rails came out. Why not use a pure regular expression router in similar fashion to gsub? I imagine it working something like this: Merb::Router.prepare do |r| r.add %r[^/(.*)/(.*)/(\d+)$], :controller => ''\1'', :action => ''\2'', :id => ''\3'' r.add %r[^/user-(\d+)$], :user_id =>

#set_status http://merb.devjavu.com/browser/trunk/lib/merb/mixins/render.rb#L270 refers to a non-existent constant. I tried, while creating #359, to make things OK, but I failed. I started by using STATUS_CODES instead, then used #[] instead of calling a method named STATUS_CODES, then I found out that during the call to #inherited

I have encountered a problem with a RESTful route, I have the simple route; r.resources :people With a corresponding controller, when I tried to access it using ActiveResource I get a server error, I have tracked this down to a problem where if the header ''Content-Type: application/xml'' is sent it errors out: > curl -H ''Accept: */*''

All, So I got passed my initial hurdles with merb 0.4. And all seems to work very nicely. Thank you all for your help ! One thing though, why should I have to bounce the merb server when I change my controller or associated classes ? Am I missing something ? I am having flash back to my java days where I now have to reflect on what changed and bounce the server accordingly...

Hello guys. I missed a lot of the development before 0.4 got out (btw, excellent work!). I checkout last night the merb-trunk code and run the specs, found that everything passes with 1 pending, but no errors or failures about missing ruby2ruby. There is a ticket (#274)[1] that discuss this, but I remember we discussed this back in September about depending on RubyInline... Also, the merb gem

Hello Guys, Doing some svn up and some looking at the code in the repo, found that MERB_ROOT and the replacement Merb.root constant based heavily on Dir.pwd (on trunk: http://merb.devjavu.com/browser/trunk/lib/merb.rb#L89) Dir.pwd present a problem when you try to run something "outside" the root of your app, let say inside app directory it will wrongly assing MERB_ROOT to Dir.pwd and

Hi, I''ve started looking at ticket 90<http://merb.devjavu.com/projects/merb/ticket/90>and there are a couple of situations that the current implementation doesn''t cater for. 1. Tag Attributes are wiped out. - <tag1 attr1=''1''>Content</tag1> #=> { "tag1" => "Content" } - I think it should return -

Hello, My name is Olle, and I am new here. I''d like to add some detail to Ez''s explanation in a previous email [1]. These are the steps I took to get Merb running Merb Edge (is that what you call it?). Start in the merb-root not in the dist-root. # Create dist/framework, plus script/merb stub rake merb:freeze cd dist rm -rf framework # Replace dist/framework with trunk

Hi all, apologies if this isn''t the right place to ask. merb.devjavu.com seems to be down for me everyday between 11:00am UTC and 5:00pm UTC. Anyone outside the US seeing this problem? Btw, merb is just... beautiful. Cheers, David

Hi there I just started my first Merb app and I''m running into some weird things in Specs. When I do: describe "create action" do it "should create a new project" do project_params = {:name => ''bekkunin''} Project.should_receive(:create).with(project_params) controller, action = post(''/projects'', :project

FYI, I blogged about the new system here: http://blog.inquirylabs.com/ 2007/08/27/new-router-in-merb/ Duane Johnson (canadaduane)

I remember having this discussion on IRC before, so Ezra if you could remind me that would be appreciated: Why do we check for the existence of the controller file in (what is now) Request#controller_class? The reason I ask is that I would like to implement some sort of "Rails engine" like features for gem plugins--in other words, drop in a gem that has controllers/views etc.