snusnu, thanks for the detailed answer, and for all your hard work on making DM work with Rails3. Your post below concerns changes that will be made to Merb, but I my question was of a different nature.
Specifically, I have an existing Merb app that I am considering porting to Rails 3. I was wondering if anyone has written a document specifying all the differences between Merb and Rails 3, so I know what needs changing in my code. I am happy to contribute to this effort if no doc exists yet. ..tony.. On Fri, Feb 12, 2010 at 9:32 AM, Martin Gamsjaeger <[email protected]>wrote: > Tony, > > I can say which work has already been done :) Pavel added support for > bundler-0.9.x ! (currently it's only in his fork, but it'll be pushed > to master soon) > > Then I can say which work I will probably be doing for merb to make it > more compatible with rails3 (at some point in the not too distance > future) > > 1) > Use the same datamapper integration base that supports dm on rails3 > for merb too. This will mean that dm will be integrated with merb in > the same manner that it is with rails3. This includes setup for > multiple repositories in multiple environments, as well as rake tasks > to perform common operations like create/drop/automigrate/autoupgrade. > For the interested, I have started extracting core functionality from > http://github.com/datamapper/rails3_datamapper, and this will form the > basis for upcoming dm-rails, dm-merb, dm-sinatra and dm-rango gems. > The gem isn't currently up on github, but it will probably arrive > there during the weekend > > 2) > Make merb use active_support (while still being compatible with extlib > too). There's no chance (I see) to get those 2 libs to work in > parallel, so it will be like this: if AS can be required, it will use > that, otherwise it'll fallback to extlib. > > Those are the 2 things i will probably be working on. Still, other > stuff would be cool to have too, like: > > 2) > Make merb use active_model under the hood, which allows supporting the > next point: > > 3) > Building merb-helpers on top of action_view and deprecate merb-helpers > API in favor of action_view > > 4) > Provide a controller API that looks the same as rails3's where that's > possible. > > 5) > Maybe rack integration could be revamped a bit too, not sure if that's > necessary or even desired tho. > > So, this is what comes to my mind when I think about what'd be cool to > slowly support a migration path. However, I know for sure that I won't > be doing all of this. I will try my best to keep merb datamapper > compatible (which is a big part for the motivation to support both AS > and extlib for merb - as dm will soon use AS under the hood - but > keeps supporting extlib mainly for merb reasons). > > Everyone is invited to contribute to any of the above mentioned > points, or do something else I haven't thought of now. > > In my opinion, these should probably be the last efforts that should > go into the development of merb. Merb isn't different enough from > rails anymore! If it were to fit a niche that rails(3) doesn't cover, > then I'd say yeah, go ahead, but in the current state, there really is > too little difference to justify great development efforts. Also, too > few people seem to be interested anyway. > > Now these are only my thoughts. Feel free to add your own! > > cheers > snusnu > > On Fri, Feb 12, 2010 at 18:10, Jeff Pollard <[email protected]> > wrote: > > There was this thread last week that talked about it slightly. > > > > > http://groups.google.com/group/merb/browse_thread/thread/4401164903104838?hl=en > > > > The Datamapper people (assuming you're using it) have a rails3 plugin > that > > works pretty well. > > > > http://github.com/dkubb/rails3_datamapper > > > > -J > > > > On Fri, Feb 12, 2010 at 8:59 AM, Tony Mann <[email protected]> > wrote: > >> > >> I looked around for a doc that spelled out all the steps for porting a > >> Merb app to Rails 3, but surprisingly I could not find one. Anyone know > if > >> such a doc exists? If not, any ideas how to get one going? I would be > happy > >> to contribute. > >> ..tony.. > >> > >> -- > >> 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] <merb%[email protected]> > . > >> For more options, visit this group at > >> http://groups.google.com/group/merb?hl=en. > > > > -- > > 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] <merb%[email protected]>. > > For more options, visit this group at > > http://groups.google.com/group/merb?hl=en. > > > > -- > 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] <merb%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > > -- 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.
