This is the conclusion of Ramaze by Example, a tutorial on web development. In Part 11: Validation and Error Handling, we added a custom error page and handlers for common user errors.
Having gone through this tutorial, you should now know about:
This is part 11 of Ramaze by Example, a tutorial on web development. In Part 10: Cosmetics, I improved the look of our application.
Up to this point, we’ve been assuming users will always behave nicely and in predictable ways. As we all know, this is not a safe assumption in practice, so now we’ll add some validation and error handling to our application. I’ll introduce the changes I made somewhat in reverse order, beginning with error message display. (more…)
This is part 10 of Ramaze by Example, a tutorial on web development. In Part 9: Layout, I demonstrated how to use layouts for a consistent frontend look.
In this part, I change several things in the view layer so that the site looks a bit better. The exact details of the HTML changes are not pertinent to learning Ramaze, so I won’t go over them. You can view them yourself by doing the usual branch diff.
In this part of the tutorial, I introduce a CSS file. The reference in layout.xhtml is typical for web development in general: (more…)
This is part 9 of Ramaze by Example, a tutorial on web development. In Part 8: Deleting Tasks, we added the ability to delete tasks.
If you look at our two views, you might notice that there is some common code in both. Being good coders, we know that such unnecessary duplication is bad for maintenance and debugging, and also hinders our flexibility for future changes we might want to make.
Fortunately, Ramaze has some facilities that let you consolidate shared view code. One of these facilities is the ability to use layouts. (more…)
This is part 8 of Ramaze by Example, a tutorial on web development. In Part 7: Checking off Tasks, we added to our application the ability to check off completed tasks.
We’ll round out the functionality of our app by adding a way to delete tasks from the list. As is commonplace when building a feature into an app, we think about implementation in terms of changes to the three parts of MVC. In this case, we don’t need to make any changes to the model, because M4DBI provides us with deletion functionality for free.
In the list view, we add a link for users to click on to delete tasks: (more…)
