Ruby on Rails

On Jun 5, 2014, at 5:49 AM, Ronald Fischer wrote:

> - Since I have no experience with Ajax, and are even a newbie when it
> comes to Rails, I will first make the application as simple and
> straightforward as possible, not using the benefits of Ajax, even if it
> means that the page might be less user friendly, and after I mastered
> Rails fully, I will learn Ajax and do a redesign.


This is an excellent idea, and if you read the Agile Web Design with RoR book, is exactly the approach they recommend. It has two immediate benefits:

1. The site still works in the presence of a broken browser or a screen reader.

2. The logic you build is well thought out, and doesn't go "off the rails". The Rails UJS helpers make it easy to "Ajaxify" a form or flow that already works without Ajax.

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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0F27BEFF-C4DE-4723-B98D-53EE1FDF186B%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.