Rails - Oct 2013 - New Application, iTunes like application, MVC architecture

Hey guys!

I am a little new and developing a new lightweight application and am 
curious about my structure. I want users to add songs and also be able to 
make playlists. If they so choose, the songs in the library can move to a 
playlist. Then the songs library can be searchable.

So I thought of making a user controller and a playlists controller. But 
for the songs, should I make a pages or songs controller. What would be the 
best way to tie everything together? In a way, this is very similar to a 
basic iTunes. 

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/d16fbcc3-bed4-4208-beac-749f74758243%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On 9 October 2013 02:57, Mike Adeleke
<madeleke13-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Hey guys!
>
> I am a little new and developing a new lightweight application and am
> curious about my structure. I want users to add songs and also be able to
> make playlists. If they so choose, the songs in the library can move to a
> playlist. Then the songs library can be searchable.
>
> So I thought of making a user controller and a playlists controller. But
for
> the songs, should I make a pages or songs controller. What would be the
best
> way to tie everything together? In a way, this is very similar to a basic
> iTunes.
Are you asking what the user interface and navigation should look
like, or how to get the UI that you have already defined?  If you know
how the UI and navigation should function then the answer should be
fairly obvious.  If you can obtain the functionality in a number of
ways and don''t know which is best then just go for the one you feel
most confident with and if it ends up not right then change it.  That
is the best way to learn when you are just beginning.  The effort
involved in re-factoring should not be great.  Make sure you have full
test coverage as you develop it so that you know it still works when
you have refactored.

I presume you have already worked right through a good tutorial such
as railstutorial.org.

Colin

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtAo7Wh-WuZxSsSbwpAGtZ12EDNzRr1H9airLRUYvJQxA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.