Well, it depends on the scope of the application. The shopping cart is
production quality, but does *so* little you''d hardly want to put it
into
production.
I''d put it at the "very basic" level of complexity for RoR.
The moment you
start deviating from the built-in standards and function, and start having
to write "real code" (rather than merely glueing components together)
things
get more complex.
But "complexity" is a relative term anyway, depending on what you want
to do
and at what scale. Some applications are big and time-consuming, but not
complex, and vice versa. So I''m not really sure if that helps you, or
why
you want to know. It''s certainly a simplistic and easy application.
For a real world perspective, go take a look at the Typo source code -
nicely laid out, nice balance of builtin versus new functionality, the right
size you can get your head around - and you might even be aware of its
functionality.
t.
On 27/04/06, Jeremy Pettet <jeremy.pettet@gmail.com>
wrote:>
> I just started to learn RoR because I need to create a relatively simple
> but important application due next month.
>
> The Shopping cart app in this book is going ok but I have a question.
>
> Is the complexity of the shopping cart example in this book
> representitive of a real world application?
>
> Note that i am not saying if the application is production quality, I
> mean the ''complexity'' of the applications.
>
>
>
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060427/bfc4b48d/attachment.html