One feature of merb that for me was truly exciting was the potential
of slices. In particular, the plan for merb 1.1 allowing any merb app
to be mountable in another.
I was wondering if the merb-core team had figured out whether this
feature would make it into rails 3.0 ?
> One feature of merb that for me was truly exciting was the potential > of slices. In particular, the plan for merb 1.1 allowing any merb app > to be mountable in another.
> I was wondering if the merb-core team had figured out whether this > feature would make it into rails 3.0 ?
> weepy
Yes this is definitely one feature that will be making it across.
To be even more clear, slices in Merb were going to be replaced by
first-class apps (any app can be a slice). This should make it in to Rails3.
-- Yehuda
On Wed, Dec 24, 2008 at 1:56 PM, Ezra Zygmuntowicz <ezmob...@gmail.com>wrote:
> > One feature of merb that for me was truly exciting was the potential
> > of slices. In particular, the plan for merb 1.1 allowing any merb app
> > to be mountable in another.
> > I was wondering if the merb-core team had figured out whether this
> > feature would make it into rails 3.0 ?
> > weepy
> Yes this is definitely one feature that will be making it across.
I'm still a bit dubious about slices being ready for prime time.
The only real world slice is the auth one. Its great, as is auth-
core, but has some obvious issues:
Doesn't inherit from my application controller so I lose common
behavior. I end up copy/pasting code from application into
global_helpers to get around some of the quirks. Other things I've
yet to find a solution for (like fixing bugs - https redirect??))
besides patching the slice.
The password slice is very nicely written, but its an example of
"advanced" ruby coding. Its highly factored and parameterized. We
really cannot expect the masses to dig through this level of code on a
regular basis. I had to read and re-read the auth slice many times to
ensure I was using it correct.
The extra files littered in my project is another oddity about
slices. I get not one, but two new trees of files ;).
I'm sure your aware of these issues. I'll re-post them in the future
if somehow things slip ;).
thanks, Jon
On Dec 25, 6:39 am, "Yehuda Katz" <wyc...@gmail.com> wrote:
> To be even more clear, slices in Merb were going to be replaced by
> first-class apps (any app can be a slice). This should make it in to Rails3.
> -- Yehuda
> On Wed, Dec 24, 2008 at 1:56 PM, Ezra Zygmuntowicz <ezmob...@gmail.com>wrote:
> > On Dec 24, 2008, at 1:39 PM, weepy wrote:
> > > One feature of merb that for me was truly exciting was the potential
> > > of slices. In particular, the plan for merb 1.1 allowing any merb app
> > > to be mountable in another.
> > > I was wondering if the merb-core team had figured out whether this
> > > feature would make it into rails 3.0 ?
> > > weepy
> > Yes this is definitely one feature that will be making it across.
Michael,
Do you simply mean I should put my repeated code in a module and
include that module in both places? If so, sure it works to reduce
text but duplicates code in different classes. Is this just more of
"ruby style OO"? ;)
thanks, Jon
On Dec 25, 7:29 am, Michael Klishin <michael.s.klis...@gmail.com>
wrote:
|
