@sean I'd go for the warden as well as it's natural successor of the merb- auth. I've tried to make warden working on the latest Merb release and got it to work so you can start playing with it even before the Rails3 switch.
There needs to be done some work on the Merb and Rack integration which is not as tight currently as the Rails3. One thing which might influence your warden integration is the fact that currently Merb session & Rack session (used by warden) are not shared. These changes should come in next releases. Which sould make switch to Rails3 easier as well. @jacques How you envisage Merb 2.0 being built on top of the Rails 3 core? I mean not from the technical point of view but the purpose of the project? I can see that as clearly easiest way how to make the transition from the Merb to Rails 3. What "future extensions" in this scenario do you have in mind? Wouldn't having Merb 2.0 build on top of the Rails 3 make Merb 2.0 a "transition project" which live span is limited by the number of users who didn't migrate to Rails 3? Basically making Merb 2.0 redundant in the future? Having all that questions I should provide some answers as well. JAZ asked how is it with Merb 2.0. We're still considering what direction we want to develop in for Merb 2.0, but we don't think a layer on top of Rails 3 is what we want at this time. That being said, if there is need to write rails-merb, to help those users who do want to transition, then go for it. Pavel Kunc On Apr 5, 12:20 pm, Sean Kellogg <[email protected]> wrote: > This is certainly an attractive idea to me and likely to my employer. > Converting over to rails3 is "on the agenda" but if we could do that work > without having to actually port a ton of code, that would be a big win for us. > > In addition to the items mentioned, I'd be curious as to what sort of > challenges we might expect in rewiring merb-auth, which is something of a > beast. I had made a mental note to switch over to authlogic when we ported to > rail3, but maybe that won't be necessary? > > -Sean > > On Sunday 04 April 2010 4:39:22 pm Jacques Crocker wrote: > > > > > > > I agree, however I do think Rails3 is flexible enough to be able to > > add these features back on. Creating a merb style controller in Rails3 > > would be very cool so that whatever the the actions returns gets > > processed merb style. So if you return a string, a string gets > > rendered. I think this would be pretty trivial to implement on top of > > ActionController. I talked to Yehuda at mnt west about duplicating the > > url() helper from merb, and it looks like its very near possible as is > > (I think he mentioned it might need a small tweak in rails-core). > > > Rails3 I think is a huge step in the right direction of modularity, > > and I think will establish a huge community and platform around it. It > > still has some of the old "cruft" from Rails2, however those things > > should be able to be overridden and made better I think using some of > > the really cool techniques that came out of Merb. > > > I wonder, what if "Merb 2.0" used rails3 at its core and allowed any > > existing merb app to run on top of it? And we could then make future > > extensions while reusing the community and lots of existing code built > > for Rails3. > > > Not sure how many current Merb developers would be interested in > > something like that, but if anyone wants to help out, I'd be willing > > to contribute to an effort to try to get something like that up and > > running. > > > On Apr 4, 4:22 pm, JAZ <[email protected]> wrote: > > > I wonder what is the future for Merb after Rails 3.0 final version > > > will be released? Will it be continued as indepenedent Merb 2 > > > project? It might be quite possible... > > > > Although Rails 3 is apparently improved over Rails 2, it still uses a > > > lot of crappy features of Rails 2. > > > > E.g. named route helpers. In Merb I can just write: > > > > %w(search read faq).map{|menu| url(menu)} > > > > In Rails 3 I have to write nasty: > > > > %w(search read faq).map{|menu| eval("#{menu|_url")} > > > > or even more verbose: > > > > %w(search read faq).map{|menu| link_to(menu, url_for(menu.to_sym))} > > > > Another example - rendering. I do not know why Rails 3 borrows from > > > Rails2 magic render() method with its stupid DoubleRenderException > > > error... > > > > -- > > > JZ > > -- > Sean Kellogg > e: [email protected] > w:http://blog.probonogeek.org -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
