Rails - Jan 2008 - Using depreciated methods & things moved to plugins (ex. act_as_tree)

As a Rails newbie, I am not sure how to feel about methods that have
been moved into plugins. Why are they moved into plugins in the first
place? Should I use the plugin if it wasn''t good enough to keep in the
core code?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

It was moved out of the core because the functionality is not core
functionality. The plugins (acts_as_list / acts_as_tree) are the same, and
just as supported. It''s all about consistency, that code fits better as
plugins.

Jason

On Jan 11, 2008 4:26 PM, mel ram
<melvin-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> As a Rails newbie, I am not sure how to feel about methods that have
> been moved into plugins. Why are they moved into plugins in the first
> place? Should I use the plugin if it wasn''t good enough to keep in
the
> core code?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

So using code that has been moved out from rails into plugins is not a
bad idea? I''m afraid of learning how to use them and building apps w/
them and later find out that there is a better way to do it and that
is why it was removed in the first place.

On Jan 11, 1:28 pm, "Jason Roelofs"
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> It was moved out of the core because the functionality is not core
> functionality. The plugins (acts_as_list / acts_as_tree) are the same, and
> just as supported. It''s all about consistency, that code fits
better as
> plugins.
>
> Jason
>
> On Jan 11, 2008 4:26 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
>
>
> > As a Rails newbie, I am not sure how to feel about methods that have
> > been moved into plugins. Why are they moved into plugins in the first
> > place? Should I use the plugin if it wasn''t good enough to
keep in the
> > core code?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Well, the concern you''ve got here is slightly different. Unfortunately
with
software, this happens all the time, and Rails is a constantly evolving
library. Something that might be The Way (aka REST right now), may in a few
months time be replaced with something better. You can''t be afraid of
this
or you''ll never get any work done. Work with what''s available
now, and as
things change you can move with the changes or you can stay with the older
versions, which will still work.

Jason

On Jan 11, 2008 4:34 PM, mel ram
<melvin-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> So using code that has been moved out from rails into plugins is not a
> bad idea? I''m afraid of learning how to use them and building apps
w/
> them and later find out that there is a better way to do it and that
> is why it was removed in the first place.
>
> On Jan 11, 1:28 pm, "Jason Roelofs"
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > It was moved out of the core because the functionality is not core
> > functionality. The plugins (acts_as_list / acts_as_tree) are the same,
> and
> > just as supported. It''s all about consistency, that code fits
better as
> > plugins.
> >
> > Jason
> >
> > On Jan 11, 2008 4:26 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
> >
> >
> >
> > > As a Rails newbie, I am not sure how to feel about methods that
have
> > > been moved into plugins. Why are they moved into plugins in the
first
> > > place? Should I use the plugin if it wasn''t good enough
to keep in the
> > > core code?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

That being said, I would be really hesitant to use the "classic"
pagination
plugin instead of the recommended will_paginate [or it''s less
appreciated
but equally awesome sister paginating_find]. There''s a reason
pagination was
taken out of Rails core based on inefficiency.

RSL

On Jan 11, 2008 4:53 PM, Jason Roelofs
<jameskilton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Well, the concern you''ve got here is slightly different.
Unfortunately
> with software, this happens all the time, and Rails is a constantly
evolving
> library. Something that might be The Way (aka REST right now), may in a few
> months time be replaced with something better. You can''t be afraid
of this
> or you''ll never get any work done. Work with what''s
available now, and as
> things change you can move with the changes or you can stay with the older
> versions, which will still work.
>
> Jason
>
>
> On Jan 11, 2008 4:34 PM, mel ram
<melvin-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> >
> > So using code that has been moved out from rails into plugins is not a
> > bad idea? I''m afraid of learning how to use them and building
apps w/
> > them and later find out that there is a better way to do it and that
> > is why it was removed in the first place.
> >
> > On Jan 11, 1:28 pm, "Jason Roelofs"
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > > It was moved out of the core because the functionality is not
core
> > > functionality. The plugins (acts_as_list / acts_as_tree) are the
same,
> > and
> > > just as supported. It''s all about consistency, that code
fits better
> > as
> > > plugins.
> > >
> > > Jason
> > >
> > > On Jan 11, 2008 4:26 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
> > >
> > >
> > >
> > > > As a Rails newbie, I am not sure how to feel about methods
that have
> >
> > > > been moved into plugins. Why are they moved into plugins in
the
> > first
> > > > place? Should I use the plugin if it wasn''t good
enough to keep in
> > the
> > > > core code? > >
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Are there other plugins you would recommend staying away from?

~ mel

On Jan 12, 5:23 am, "Russell Norris"
<r...-ftMzyaTR+bHNyFkoKTPOtdi2O/JbrIOy@public.gmane.org>
wrote:
> That being said, I would be really hesitant to use the "classic"
pagination
> plugin instead of the recommended will_paginate [or it''s less
appreciated
> but equally awesome sister paginating_find]. There''s a reason
pagination was
> taken out of Rails core based on inefficiency.
>
> RSL
>
> On Jan 11, 2008 4:53 PM, Jason Roelofs
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > Well, the concern you''ve got here is slightly different.
Unfortunately
> > with software, this happens all the time, and Rails is a constantly
evolving
> > library. Something that might be The Way (aka REST right now), may in
a few
> > months time be replaced with something better. You can''t be
afraid of this
> > or you''ll never get any work done. Work with what''s
available now, and as
> > things change you can move with the changes or you can stay with the
older
> > versions, which will still work.
>
> > Jason
>
> > On Jan 11, 2008 4:34 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> > > So using code that has been moved out from rails into plugins is
not a
> > > bad idea? I''m afraid of learning how to use them and
building apps w/
> > > them and later find out that there is a better way to do it and
that
> > > is why it was removed in the first place.
>
> > > On Jan 11, 1:28 pm, "Jason Roelofs"
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > > > It was moved out of the core because the functionality is
not core
> > > > functionality. The plugins (acts_as_list / acts_as_tree) are
the same,
> > > and
> > > > just as supported. It''s all about consistency, that
code fits better
> > > as
> > > > plugins.
>
> > > > Jason
>
> > > > On Jan 11, 2008 4:26 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> > > > > As a Rails newbie, I am not sure how to feel about
methods that have
>
> > > > > been moved into plugins. Why are they moved into
plugins in the
> > > first
> > > > > place? Should I use the plugin if it wasn''t
good enough to keep in
> > > the
> > > > > core code? > >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

The classic pagination is the only one off hand that I can think of that was
specifically deprecated because Rails core found it to be suboptimal. IIRC
the others were moved to plugins because they were deemed to be peripheral
functionality. Someone please correct me if I''m wrong there. :)

RSL

On Jan 12, 2008 8:22 PM, mel ram
<melvin-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
>
> Are there other plugins you would recommend staying away from?
>
> ~ mel
>
> On Jan 12, 5:23 am, "Russell Norris"
<r...-ftMzyaTR+bHNyFkoKTPOtdi2O/JbrIOy@public.gmane.org> wrote:
> > That being said, I would be really hesitant to use the
"classic"
> pagination
> > plugin instead of the recommended will_paginate [or it''s less
> appreciated
> > but equally awesome sister paginating_find]. There''s a reason
pagination
> was
> > taken out of Rails core based on inefficiency.
> >
> > RSL
> >
> > On Jan 11, 2008 4:53 PM, Jason Roelofs
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > > Well, the concern you''ve got here is slightly different.
Unfortunately
> > > with software, this happens all the time, and Rails is a
constantly
> evolving
> > > library. Something that might be The Way (aka REST right now),
may in
> a few
> > > months time be replaced with something better. You can''t
be afraid of
> this
> > > or you''ll never get any work done. Work with
what''s available now, and
> as
> > > things change you can move with the changes or you can stay with
the
> older
> > > versions, which will still work.
> >
> > > Jason
> >
> > > On Jan 11, 2008 4:34 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org> wrote:
> >
> > > > So using code that has been moved out from rails into
plugins is not
> a
> > > > bad idea? I''m afraid of learning how to use them
and building apps
> w/
> > > > them and later find out that there is a better way to do it
and that
> > > > is why it was removed in the first place.
> >
> > > > On Jan 11, 1:28 pm, "Jason Roelofs"
<jameskil...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > > > > It was moved out of the core because the functionality
is not core
> > > > > functionality. The plugins (acts_as_list /
acts_as_tree) are the
> same,
> > > > and
> > > > > just as supported. It''s all about consistency,
that code fits
> better
> > > > as
> > > > > plugins.
> >
> > > > > Jason
> >
> > > > > On Jan 11, 2008 4:26 PM, mel ram
<mel...-IA9i2KS8NFBpEKysQ+xqfPpXobYPEAuW@public.gmane.org>
> wrote:
> >
> > > > > > As a Rails newbie, I am not sure how to feel about
methods that
> have
> >
> > > > > > been moved into plugins. Why are they moved into
plugins in the
> > > > first
> > > > > > place? Should I use the plugin if it
wasn''t good enough to keep
> in
> > > > the
> > > > > > core code? > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---