The code mixing is incredibly useful for allowing Engines to be
used/shared effectively in a DRY way. But if it's not in Rails distro,
it can always still be in a very small separate Engines package. This is
good stuff, thanks Rails core.
Jonathan
James Adam wrote:
Asset management will be in, probably migrations too, although in a
simplified form. The only thing we haven't discussed so far is the
code mixing.
James
On 26 Nov 2008, at 15:28, Rob Morris wrote:
AWESOME news! Any idea what won't make the cut? Asset management
stuff, perhaps?
-Rob
James Adam wrote:
David spoke to me yesterday about this. We're going to be folding a
lot (but possibly/probably not all) of the functionality into Rails :)
On 26 Nov 2008, at 15:15, Tekin Suleyman wrote:
http://github.com/rails/rails/commit/63d8f56774dcb1ea601928c3eb6c119d359fae10
Tekin Suleyman
Freelance Ruby on Rails Developer
+44 (0) 7968 355 460
http://tekin.co.uk
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
------------------------------------------------------------------------
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
