> > A CMS could be developed using one or another of those MVC kits -- a CMS > is a higher-level abstraction than MVC. So comparing them is a false > choice. >
What you mean is that i should develop a CMS using MVC, so that adding content to my website would be easy and simple? Em quinta-feira, 31 de outubro de 2013 10h12min47s UTC-2, Walter Lee Davis escreveu: > > > On Oct 30, 2013, at 9:59 PM, N2obie wrote: > > > Hello, > > > > This is my first post here! I`m a computer engineering with almost no > formation in web Development. What I do know, is software > engineering/architecture, Java and C/C++. I also have had some foundation > in XHTML/CSS. > > > > So, this said, a friend came to me asking to develop a Website similar > to eBay/Amazon/etc., I know it`s a huge project, so i don’t want to develop > it with SQL, PHP, HTML. I want to use some Modern technology... I`ve read > about a few of them: > > > > > > MVC -> facilitates the development of website by handling all those > "complicated" language (SQL, PHP, HTML) and it`s connection automatically > by the use of some language: > > • Java -> JSF > > • Ruby -> RubyOnRails > > • Python -> Django > > CMS -> facilitates the development of website by templates; in other > words, it has many templates of many kinds of websites and those templates > can be customized. > > • drupal > > • joomla > > > > The project has six months to be developed, at least a first working > prototype. In addition, there is going to be two or three programmers doing > it in their free time. > > > > I do know some of the strengths and weakness of each MVC/CMS.... the CMS > is faster to develop, but it`s less customizable... From what I`ve heard of > my friends project, it`s not a common website, it`ll provide a lot more > than eBay/etc. So I`m afraid of using CMS. > > > > Most of all, the project should be modular; in other words, it must be > possible to add new tools to the website after its completion. > > > > > > If anyone has something to add, suggest or ask, please feel free. > > > > > > A CMS could be developed using one or another of those MVC kits -- a CMS > is a higher-level abstraction than MVC. So comparing them is a false > choice. > > Unless the project fits neatly into the pattern of your CMS (f.e. Drupal > is perfect if you are building a community-written book, or a magazine, or > a corporate Web site with a contact form), then that's going to be the > fastest way to the finish line. But the moment you stray from the fall > line, you will be skiing in the trees, and often have to un-do the core > premises of the CMS in order to build some bit of functionality that you > really need. > > Walter -- 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/5045067d-df76-40c1-b795-7341c69098a3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
