Hi, everyone!
It has been a while since I posted here, given that I get to find most
of my answers on google. However, there is one particular coding
practice I am after, for which I have thought of a solution, as well as
found the exact same solution for .Net.
Basically, I am working with a blog post model, where I sometimes need
to spread a post into several pages. There are two ways I can think of.
Create a model Post with a content field, and in the content field we
add some tag that signals the page breaks, something similar to what
wordpress uses. I would then have to write some code to split the
content into several pages, and create the pagination code as well. The
second alternative is to create a post model, and a pages model. The
post model would have many pages, and the pages would belong to the post
model. I can sort of see the advantages and disadvantages of both
models, and to be honest, I would prefer the solution where I have a
post model and a page model. But, given that I want to follow best
practices, I was wondering what you guys have been using to sort this
multi-page issue.
Could someone share his experience in this area?
I look forward to hearing from you guys.
Regards,
Fidel.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/51F58D8F.8010400%40kazomosolutions.biz.
For more options, visit https://groups.google.com/groups/opt_out.
