Yehuda Katz Developer | Engine Yard (ph) 718.877.1325
On Fri, Feb 12, 2010 at 12:15 PM, Pavel Kunc <[email protected]> wrote: > Hm... I don't know. > > On Feb 12, 5:32 pm, 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) > > Yep very soon. I've ported my app to that and it works. App generators > needs some care but that's minor. > > > > > 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 > fromhttp://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. > > This for sure will happen. I have no problem working on that but you > did that for DataMapper so you have some experience. > Great news! If there's anything about active_support that doesn't work for you for some reason let's get it fixed. > > > > > 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: > > I thought that we done this. Maybe not, merb_sequel is updated to use > AM model layer now. > > > > > 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. > > > > Not really sure about 3 & 4. I have app which I'm not going to rewrite > to R3 for many reasons. At least in next year or so. Which means that > I need Merb in the shape which it is currently; if improved no > problem. > For #3, it's simply a matter of creating merb-rails-helpers! Merb is already modular so it should be possible to have merb-helpers and merb-rails-helpers with no problems :) For #4, it should be easy enough to alias things like before/before_filter who want to move to Rails, but without harming people who want to stick with Merb. We could even have a "switch" mode that could emit warnings when using "before", but not impact people who want to stick with Merb. > > I don't want to change Merb in such a way that I need to change my > existing code. That doesn't make sense for anybody who wants/must to > stay on Merb. > > If there are any changes to get closer to the Rails 3 API than it must > be in separate branch. And also my opinion is that if someone wants to > rewrite Merb app to Rails 3 than he can, what is the reason to rewrite > Merb to be something like Rails 3 but not really Rails 3? > > > 5) > > Maybe rack integration could be revamped a bit too, not sure if that's > > necessary or even desired tho. > > Desired from my point of view. I'll work on that. > I personally really like FooController.action(:index) from Rails. Should be easy to make the same thing work in Merb :) > > > > > 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! > > As for my side. I'm not going to migrate to R3 any soon. And don't get > me wrong, I think Rails 3 are amazing achievement, but I just don't > want to rewrite/change huge amount of code just because there are R3. > Understood. EngineYard is in the same place. > So my focus is to make Merb better for my purposes which means that > I'll continue working on 1.1.x and 1.2.x branches and include some > aspects which makes Merb up-to-date but will keep it Merb. > Sounds good to me. I'd like it if we could, in parallel, make it easy for people with Merb apps who want to switch to switch (again, without harming people who want to continue using Merb). > I want to remove forking/clustering and rack adapters and do proper > standard Rack support + Unicorn for clustering. That should remove > much of the current hassle. > +1. Unicorn is basically the same thing I was trying to do :) > There are some more things which might come such as full Rack > integration and Rack endpoints. > > If you ask why? Well I just feel that it would be easier for me to add > these features to Merb than to rewrite app to R3. > Makes sense to me :) > > > > > 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/440116490310. > .. > > > > > 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.
