It's clearly just a troll--seems plausible at first with plenty of
details, but if you think about it this guy is yanking our chain.

* "after some months" - After several months it would be impossible to
be this clueless.
* Willful ignorance of render :partial, conditionals, or any other
basic building blocks of templates
* "It seems to me that Rails is better suited
as a back-end grungy file maintenance application" The Troll
* "or am i being too harsh?" The Bait



On May 22, 6:10 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On 5/22/07, SydneyStephen <[EMAIL PROTECTED]> wrote:
>
>
>
> > If the customer registers or logs in, this all happens in the sidebar,
> > leaving the products display intact.  In order to ensure that the
> > products remain in the display I have to persuade Rails not to look
> > for a register.html or login.rhtml file by using the render :action or
> > redirect_to_action statements.
>
> Seems that your knowledge of how to do things in Rails is clunky, not the
> framework itself.
>
> Am I being too ambitious with Rails in trying to provide a clean,
>
> > managed, user interface?  It seems to me that Rails is better suited
> > as a back-end grungy file maintenance application - or am i being too
> > harsh?
>
> This is pure flame bait. I advise you to try and have such discussions
> elsewhere, perhaps even on Rails Talk mailing list. It is obvious that you
> have much to learn how to use the framework and how to think MVC; until then
> you are not in position to spread FUD on the Core list where people usually
> hang out when they become experienced with the framework and its internals.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to