We’ve finally arrived at the moment of the map. For the last several articles in the Loccasions series , I have promised things like “in the next post we will deal with the map” and “I will lower taxes,” and I have not delivered. In this post, I will fulfill at least one of those promises. Adding the map to this application is almost completely a client-side proposition.

Read this article:
Loccasions: Going Client-Side with Leaflet, Backbone, and Jasmine

Here are some of the best posts on RubySource in the month of October, in case you missed them.

• Short, Long, and Pretty URLs: Darren Jones shows how to create your own URL modifier in Sinatra, complete with why you might use short, long, or pretty URLs.
• How Can a .NET Developer Get Started with Rails: Claudio Lassala paves the road from .NET to Ruby and Rails.
• Creating Your First Gem: John McAliley teaches the way of making gems.
• Loccasions: Pair Programming: In this installment of the Loccasions series, Glenn Goodrich has a pair-programming session.
• Debugging and Dissection Dojo: Marc Berszick uses martial arts to explain the basics of debugging in Ruby.

You see gems everywhere in the Ruby world. They are the backbone of just about every Ruby app out there. I’ll admit that I was a bit intimidated the first time I tried to create a gem, but I soon found out that it’s dead simple.

See the article here:
RubySource: Creating Your First Gem

Adding and Deleting Resources in Sinatra In this tutorial I’m going to go through how to use Sinatra to add and remove resources to and from a database. To demonstrate this, I’m going to build a tiny web app called The Robot Factory that allows users to ‘build’ a production line of robots. Each robot will be saved to a database with randomly chosen head, body and legs and can also be deleted after it has been built. You can see the final version running here – http://robotfactory.heroku.com/ .

Read the original:
RubySource: The Robot Factory – Part One

Our last post flushed out the Events model and created a very basic home page. Hopefully, by the end of this post, we will be able to add, modify, and delete events from our user home page. CRUDdy Events Unless you’ve just been unfrozen from a decades long, icy slumber, you know what CRUDifying a model entails.

Taken from:
RubySource: Rails Deep Dive: Loccasions, Making Events

Common question for .NET developers deciding to venture into Ruby are: Where do I start? What should I learn first: Ruby or Rails? What do I need installed? What are the best resources to get started

More:
RubySource: How Can a .NET Developer Get Started on Ruby or Rails?

If you’ve ever developed something using Ruby then you know it’s a blast to use. It flows well, reads well, and has lots of cool ways to get things done. Beyond the day-to-day APIs you might be used to, there lies a bunch of goodies that are often overlooked or never seen until now! In this article I’ll explore some of those gems, no pun intended, that could deliver you straight to Ruby zen.

View original post here:
RubySource: Less Used Ruby APIs

In the last article we had a whistle stop tour of blocks. How they are defined, what purposes they serve and the differences between various Ruby versions. It was all very academic.

View article:
RubySource: Getting to Grips with Blocks II

Ruby is an opinionated language, and it has an opinionated community. This is a great thing. It keeps the language clean, understandable, and fun. Ruby can be antagonistic when it comes to a framework like .NET, and I’ll touch on that in this post.

Link:
RubySource: .NET to Ruby: Namespacing, Naming Conventions, Comments & Documentation

In our last post, we ended with very basic authentication working. However, we are faking out the events_path in our sign_in spec, which is where we’ll start. A successful sign-in redirects to the user events page which, presumably, has a list of the events owned by that user. Let’s go back to Mockbuilder and crank out a layout for our events page.

View original post here:
RubySource: Rails Deep Dive: Loccasions, Spork, Events and Authorization

In the last post in our series on Switching from .NET to Ruby, we looked at Classes . Classes were a real in depth topic since there’s a large number of class differences between .NET and Ruby. This post is going to take an a look at Methods and Variables.

Taken from:
RubySource: .NET to Ruby: Methods and Variables

Welcome to the last part of this series. The aim of this series of tutorials has been to take somebody who has never used Sinatra from creating an app to deploying it. You can find the other parts of the series at the following links: Part 1 – Introduction to Sinatra Part 2 – Using DataMapper Part 3 – Database Associations After those three parts, we have now finished most of the main functionality of our To Do List app. In this final part we are going to look at using Sass for the CSS before deploying the app on the Heroku cloud hosting service

More:
RubySource: Just Do It: Learn Sinatra, Part Four

I’ve noticed there’s quite a bit of misunderstanding among .NET developers as to what Ruby or Rails are, and how those compare to what they came to know and love in .NET. I know I didn’t understand it myself for a while. The following comments, drawn from my two previous posts ( Switching to Ruby from .NET and Why should a .NET developer look into Ruby or Ruby on Rails ) serve to illustrate my point: “Had a look at Ruby but no thanks, .NET remains the way for me.” “…are there demos or samples of Ruby on Rails that can compare with the web apps that I can create with ASP.NET or Silverlight, and components like DevExpress for the ASP.NET MVC? Is there something like that in Ruby?” While the first comment compares Ruby to .NET, which is a comparison between a language and an entire development platform, the second comment mixes html-based applications with rich client applications built on Silverlight, brings 3rd part visual controls into the equation, and wonders whether such controls are available in Ruby (a language…)

Read this article:
RubySource: Putting Ruby, Rails, C#, and ASP.NET in context

In the previous post of this series .NET to Ruby: The Ruby Environment , we went through the fundamental tools that made up Ruby. If you recall we talked about running Ruby on the command line, using IRB, we wrote our first Hello World program, and figured out what was going on below the covers. In this post we’ll look to compare a fundamental object oriented feature: Classes. Yup that’s it.

View article:
RubySource: .NET to Ruby: Classes