Rails - Dec 2006 - Design doubt- putting a method in the controller, in model..

Hi you all,
I have a textarea in a wiki application where users can write things in
the way "{{property value}}". These thing will be later transformed in
Annotations (a table in the DB)
I''ll do all the scanning of the content and then save these annotations
in the "def create" and "def edit" of my wiki controller. My
question
is, where should I put this scanning and stuff better, in the wiki
controller as I was gonna do, in the annotation controller, or in the
annotation model?
My first though was putting it as a method of the model "Annotation",
but is something related with an input from the view, and I think a
model hasn''t have to manage this. But..if not… the controller will have
to do all the stuff so… do I have to add any class in between?
Thank you in advance.
-- 
Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

Put it in the application helper module.
On 12/19/06, Damaris Fuentes
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:
>
>
>
> My first though was putting it as a method of the model
"Annotation",
> but is something related with an input from the view, and I think a
> model hasn''t have to manage this. But..if not… the controller will
have
> to do all the stuff so… do I have to add any class in between?
>
> Thank you in advance.
>
>
--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

On Tue, Dec 19, 2006 at 04:12:54PM +0100, Damaris Fuentes
wrote:
> 
> Hi you all,
> 
> I have a textarea in a wiki application where users can write things in
> the way "{{property value}}". These thing will be later
transformed in
> Annotations (a table in the DB)
> I''ll do all the scanning of the content and then save these
annotations
> in the "def create" and "def edit" of my wiki
controller. My question
> is, where should I put this scanning and stuff better, in the wiki
> controller as I was gonna do, in the annotation controller, or in the
> annotation model?
> 
> My first though was putting it as a method of the model
"Annotation",
> but is something related with an input from the view, and I think a
> model hasn''t have to manage this. But..if not??? the controller
will have
> to do all the stuff so??? do I have to add any class in between?
I''m not sure I understand your resistance to putting things in the
model. Maybe you can think about it this way:

Would you like to be able to do the same kind of insertion in the console
or in another controller, like:

        some_model.set_text("{{foo}}")

The it should most likely be on the model.

-- 
Cheers,
- Jacob Atzen

--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

> I''m not sure I understand your resistance to putting things in the
> model. Maybe you can think about it this way:
> 
> Would you like to be able to do the same kind of insertion in the 
> console
> or in another controller, like:
> 
>         some_model.set_text("{{foo}}")
> 
> The it should most likely be on the model.

Um, the thing is that the model will have to "analyze" the data
between
brackets.

What if tomorrow I change the annotation way and there is no more text 
in brackets, but...I dunno...selecting checkboxes? Has the model to 
manage the changes in the app View? has to be aware if the annotations 
are coming to it in form of text in brackets or in checkboxes?

Thanks.

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

On Tue, Dec 19, 2006 at 07:23:23PM +0100, Damaris Fuentes
wrote:
> Um, the thing is that the model will have to "analyze" the data
between
> brackets.
Yes, that''s what model''s do, they "analyze" or in
other ways handle
data. Some might even say, that the model _is_ the data. The controller
is simply a way of manipulating the model.
> What if tomorrow I change the annotation way and there is no more text 
> in brackets, but...I dunno...selecting checkboxes? Has the model to 
> manage the changes in the app View? has to be aware if the annotations 
> are coming to it in form of text in brackets or in checkboxes?
If you are really doing the same thing you could either update the model
to account for an alternative way of setting the same attribute or you
could make the controller convert the checkbox input into a string for
your model, though I would probably go for the former in most cases.

-- 
Cheers,
- Jacob Atzen

--~--~---------~--~----~------------~-------~--~----~
 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 model must be agnostic. It should accept (require) a specific type of
input and your views / controllers should respect that format. This allows
you to keep your code simple.

User.new()  accepts a hash.  It just so happens that Rails takes parameters
from a view and stores them as a hash.

I believe this is called "programming to an interface." That said,
Ruby does
make it more interesting by allowing you to determine what was passed into
the method,.



On 12/19/06, Damaris Fuentes
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:
>
>
> > I''m not sure I understand your resistance to putting things
in the
> > model. Maybe you can think about it this way:
> >
> > Would you like to be able to do the same kind of insertion in the
> > console
> > or in another controller, like:
> >
> >         some_model.set_text("{{foo}}")
> >
> > The it should most likely be on the model.
>
>
> Um, the thing is that the model will have to "analyze" the data
between
> brackets.
>
> What if tomorrow I change the annotation way and there is no more text
> in brackets, but...I dunno...selecting checkboxes? Has the model to
> manage the changes in the app View? has to be aware if the annotations
> are coming to it in form of text in brackets or in checkboxes?
>
> Thanks.
>
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

Bala Paranj wrote:
> Put it in the application helper module.

Yes, i also thought aboutit, but the applications helpers keep methods 
FOR the view, not FROM the view...am I right?

Thank you all.

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---