I’ve been interested for a while in getting underfloor heating, probably of the hydronic variety. Underfloor heating offers some benefits in terms of less air movement and noise, and of giving a more liveable ambient heat – there is some evidence that the warmth of your feet is a key determinant of how comfortable your house is in winter.
The concept has been to use a large water storage tank as thermal mass, and to use evacuated tube water heating to heat that tank. This gives most of the benefit of having large thermal mass in your house, whilst giving control over when you take the heat out of that thermal mass.
This blog post explains why I think that’s probably not a great idea anymore, and what I’m thinking instead.
In this portion of the tutorial we’re going to extend to the teams entity, and build the links between clubs and teams. This means passing parameters to our list controller, and dealing with optionality. We’ll let people create a team from within the context of a club – in which case we auto-populate the club, and we’ll let them create a team standalone and pick the club from a drop-down.
This tutorial mainly consolidates what we’ve already done, but it lays the groundwork for some more interesting functionality later, including user authentication and an editable grid.
If you’ve dropped into the middle of the tutorial, you can find the code for the previous section at github: PaulL : tutorial_8. You can go to the index page for this tutorial, or you can hit the tutorial menu above and see all the posts in the Rails 4 tutorial.
I’ve been working on making an editable ngGrid, allowing users to directly edit the grid rather than going to a detail page. I’m seeing that there are two modes of operation – for simple things (maybe changing the status of a bunch of items), it’s easier to interact with the grid directly. When you want to edit a full item, you’d do this in the detail page.
The aim is to have a grid that you can edit directly, and have it save to the server when you leave the cell you’re editing (this is a reason you wouldn’t want to edit the whole record this way – you’ll end up with lots of spurious saves if the user has lots of cells to edit).
Part 8 of the tutorial focuses on adding a delete button to our ngGrid, and adding error handling in case our rails application rejects our updates. You can find the tutoral index, or hit the tutorials menu at the top and select the Rails 4 tutorial.
Part 7, in which we create karma unit tests for the list and edit controllers, including mocking the http calls.
If you’ve jumped into the middle of this tutorial, you’ll need the code from github:PaulL:tutorial_6, or you might want to visit the index page or hit the tutorials link above and look in the rails 4 tutorial.
In this, the sixth post in the rails 4 tutorial, we change our clubs list page to use ngGrid instead of our home-made table. We also implement an edit page for our clubs. A key difference from the rails 3 version of this tutorial is that we’re implementing our edit page as a page rather than a modal dialog.
If you have dropped into the middle of the tutorial you can find the code from the previous step in this tutorial at github:PaulL:tutorial_5, or you can find those tutorial pages either from the index page, or by hitting the tutorials menu in the menu bar above.