Comments on: Implementing Django’s Modular Apps Feature in Rails http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails Let There Be Software! Sat, 19 Sep 2009 09:36:06 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: zerohalo http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-27 zerohalo Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-27 <p>I agree that the Django approach to a project, with apps within it, makes a lot of sense - especially for websites that have more than one application running in them (which is many of them).</p> <p>Django's "free" Admin interface is a killer feature. Rails is getting there with Streamlined and AjaxScaffold, but still has some catching up to do.</p> <p>That's not to say I prefer Django to Rails in general, but it would be nice if Rails could implement the best of Django.</p> I agree that the Django approach to a project, with apps within it, makes a lot of sense - especially for websites that have more than one application running in them (which is many of them).

Django’s “free” Admin interface is a killer feature. Rails is getting there with Streamlined and AjaxScaffold, but still has some catching up to do.

That’s not to say I prefer Django to Rails in general, but it would be nice if Rails could implement the best of Django.

]]> By: Adrian Holovaty http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-28 Adrian Holovaty Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-28 <p>One cool way to get into Django (and to take advantage of modularity in general) is by using it for the admin interface while maintaining the rest of your legacy Rails site. There's no reason not to mix and match, if you've got legacy Ruby code.</p> One cool way to get into Django (and to take advantage of modularity in general) is by using it for the admin interface while maintaining the rest of your legacy Rails site. There’s no reason not to mix and match, if you’ve got legacy Ruby code.

]]> By: Luis Lavena http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-29 Luis Lavena Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-29 <p>@zerohalo: There is also <a href="http://agilewebdevelopment.com/plugins/roar_offers_automated_rails">Roar</a></p> <p>Their approach is quite different, but very easy to implement admins views to your existing controllers (thinking in a REST way, of course).</p> <p>Its good to see that engines now is just a simpler "patch" to rails 1.2 to provide additional paths to controllers, models and views, compared to previous versions ;-)</p> <p>Good article, btw :-)</p> @zerohalo: There is also Roar

Their approach is quite different, but very easy to implement admins views to your existing controllers (thinking in a REST way, of course).

Its good to see that engines now is just a simpler “patch” to rails 1.2 to provide additional paths to controllers, models and views, compared to previous versions ;-)

Good article, btw :-)

]]> By: Ian Bicking http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-30 Ian Bicking Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-30 <p>Another way to support multiple apps (used by <a href="http://pylonshq.com">Pylons</a>) is <a href="http://pythonpaste.org/deploy/">Paste Deploy</a> -- which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with <a href="http://rack.rubyforge.org/">Rack</a> is now something of a possibility in Ruby as well.</p> Another way to support multiple apps (used by Pylons) is Paste Deploy — which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with Rack is now something of a possibility in Ruby as well.

]]> By: Ian Bicking http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-31 Ian Bicking Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-31 <p>Another way to support multiple apps (used by <a href="http://pylonshq.com">Pylons</a>) is <a href="http://pythonpaste.org/deploy/">Paste Deploy</a> -- which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with <a href="http://rack.rubyforge.org/">Rack</a> is now something of a possibility in Ruby as well.</p> Another way to support multiple apps (used by Pylons) is Paste Deploy — which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with Rack is now something of a possibility in Ruby as well.

]]> By: Ian Bicking http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-32 Ian Bicking Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-32 <p>Another way to support multiple apps (used by <a href="http://pylonshq.com">Pylons</a>) is <a href="http://pythonpaste.org/deploy/">Paste Deploy</a> -- which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with <a href="http://rack.rubyforge.org/">Rack</a> is now something of a possibility in Ruby as well.</p> Another way to support multiple apps (used by Pylons) is Paste Deploy — which is more of a package-based system (gem-based in Ruby). It uses WSGI for dispatching, which with Rack is now something of a possibility in Ruby as well.

]]> By: Joe Grossberg http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-33 Joe Grossberg Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-33 <p>"There's no reason not to mix and match, if you've got legacy Ruby code."</p> <p>Yeah, there is -- you now need a team that can develop, debug, deploy, maintain and optimize in both Ruby/Rails and Python/Django.</p> <p>That's not the end of the world, and I personally like both languages and both frameworks.</p> <p>But I don't think adding another language and framework to a site is a decision that should be taken lightly.</p> “There’s no reason not to mix and match, if you’ve got legacy Ruby code.”

Yeah, there is — you now need a team that can develop, debug, deploy, maintain and optimize in both Ruby/Rails and Python/Django.

That’s not the end of the world, and I personally like both languages and both frameworks.

But I don’t think adding another language and framework to a site is a decision that should be taken lightly.

]]> By: Kev Mises http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails/comment-page-1#comment-34 Kev Mises Wed, 30 Nov -0001 00:00:00 +0000 http://fiatdev.com/2007/03/31/implementing-djangos-modular-apps-feature-in-rails#comment-34 <p>'Legacy' rails code????</p> <p>That's rich.</p> ‘Legacy’ rails code????

That’s rich.

]]>