Some "progress" on my Tau in Ruby patch

Its category was changed from "core" to "joke" :(... How does the quote go? "First they ignore your patch, then they classify it as a joke, then... " I forget the rest ;)

"Once τ is widely accepted in these communities, we might add it..."

But also:

"...if it were just up to me, I'd add it just to show support. It's a rather tiny and harmless addition."

See the ticket here.

Make it easier to use partials with blocks in rails

The shorter version of render :partial is widely known and used. These are equivalent, but the second version is so much more succinct and readable. To use a partial with a yield in it, (what I call a "block partial"), you can use render :layout which a. doesn't read very well, (it's a partial, not a layout clearly), and b. can't be shortened nicely the way that render :partial can. So here is block_render: It lets you have nice neat render calls like this: This is a real-life example of a block partial I like to use. Those classes are bootstrap classes for making a nice drop down menu.

Make ActiveRecord::Base#create respect the :type attribute

I think I've needed and implemented this twice now, so let's make a post about it.

The problem occurs when you are using f.fields_for and nested forms, as per these railscasts, and the nested objects are using STI.

(Will leave a more detailed explanation for future posts).

Update 1: Even though this works as described, I don't think it solves my problem. Will post again if I figure it out...

Update 2: Found this which is I think what I was using last time I had this problem... :S

Another approach to using helper methods in your controller actions in Ruby on Rails

A Rails 3 gotcha with html_safe

This was causing me to scratch my head a bit today. I'm glad I know what's going on now and why you need to use safe_concat. It still seems a little unintuitive though. For more into see the explanation here (under the "the tricky part") and the api docs on ActiveSupport::SafeBuffer

My (first) contribution to Rails

I fixed a little mysql configuration bug in Rails. It counted as three commits (even though they are the same thing, just in different branches), which puts me unfairly into the top 500 all time committers. ;) See here.

You'd think DHH would be number one, but actually he's not. Take a look at the list.

Here is my original pull request if you'd like to read more about it.

Ps, I also reported a capybara bug (along with a failing test) that got fixed pretty quickly. But my fork didn't get merged so none of my commits are recorded. :P

Tau in Ruby

Inspired by http://bugs.python.org/issue12345 and of course The Tau Manifesto, here is a patch for ruby to define tau, the true circle constant. Of course we don't need to really need to patch ruby to get this functionality (but I had fun doing it anyway).

Here is tau.rb so you can just require 'tau'. (Maybe this should be a gem...) Ps, I just learned about module_function.

Update 1: I made this ticket which has been mostly ignored.


Update 2: Ticket has been noticed and discussed! :) Ticket has been categorised as joke! :(


Update 3: Some active debate is going on now and the ticket is now 'assigned'! :) See the details.


Update 4: (28-Jun-2014) Made a pull request in Github.


Update 5: See https://github.com/jneen/math-tau/

beginning_of_fortnight gem is out

As promised I've cleaned up my beginning of fortnight hack and turned it into a proper ruby gem.

Install in the usual way:

sudo gem install beginning_of_fortnight

It requires ActiveSupport and adds {next,end_of,beginning_of}_fortnight methods to the Date and Time class. They work the same as the *_week methods defined by ActiveSupport. You can set where you want fortnight boundaries to be (or just use the default).

For more info see:

• Code (github)
• Docs (rubydoc.info)
• Gem page (rubygems.org)

I carefully made sure the docs look good in RDoc but, rubydoc.info uses YARD. So they don't look so great and actually the main usage examples which I put at the top of the file aren't showing at all...

I guess I will convert to using YARD. Is RDoc fading away? The website looks pretty musty.

(Just for fun, here are tweets where it all began).

Using the singleton class to include a module on-the-fly

I still don't entirely understand the syntax for accessing the singleton class, but I have found a use for it. :) The goal is to be able to make an object include a mixin on the fly.

If you do self.class.send(:include,module_name) instead of using the singleton class then the change affects every instance, not just the one you intended.

So it seems to work pretty well. Ruby is all like "sure buddy, have some rope, take as much as you need". :)

I should say that this technique was designed to be a quick fix to let us work around some legacy code that really should be refactored and fixed properly. I'm not saying this is a sensible design pattern, but it is cool that ruby can do it.

Here is a good explanation of singleton classes in ruby.

Some meta-progamming fun with Ruby (a define_method example)

I am currently working on my first gem which I hope to publish soon. It will be based on this beginning_of_fortnight method but will be more complete and flexible and (hopefully) it will be properly tested and documented. And it will be a gem of course, so it will be easy to install.

So the logic used to determine which half of a fortnight a given day falls in I wrote to work with Time objects. I decided that re-implementing it with Date objects would not be trivial. Take a look at this:

>> (Date.today + 1.week) - Date.today
=> Rational(7, 1)
>> (Time.now + 1.week) - Time.now
=> 604799.999613
>> (Time.now + 1.week) - Time.now
=> 604799.999532
>> 7.days.to_i
=> 604800

The result of subtracting two Dates surprised me a little. I guess Rational(7, 1) is 7 days. But anyway I didn't want to get any deeper into that so I did it like this:
So instead of figuring out how to apply my algorithm to Dates I will just convert them to Times, call the Time method on them, then convert them back to Dates afterwards.

Actually Date#to_time and Time#to_date are not part of the standard library but are defined by ActiveSupport. Since my gem requires ActiveSupport that's fine. Of course I could have written out the three methods but why not add some meta-programming coolness to the lazy to DRY it right up.

The splat on *args is important. My Time methods take an argument with a default value. The splatted args takes care of that so no matter how many arguments there are (or aren't), they will get passed correctly into the send. If anyone wants to check out (and/or checkout) the WIP gem, you can find it here (github). Feedback is welcome.

Todos include cleaning the rdoc output and adding gem dependencies to the gemspec (though I don't know if I'd want it to auto-install active support if you didn't have it already...)

hamrbl: write ruby with python style whitespace (a haml hack)

Did you ever wish your code looked more like your haml?

Did you ever wonder what ruby would be like with python style significant whitespace?

Without further ado, I present hamrbl.rb

Surprisingly the syntax highlighting works fine in vim and github. :)

Ps, it's pronounced "hammerable"

Disclaimer: This is for amusement purposes only. It is almost certainly a terrible misuse of Haml :).