Posts Tagged 'rails'

Blue highlight courtesy of Autotrace

Bindle 2 is fresh out of the oven; one of the main areas of focus was making Bindles more intuitive to create & navigate—to that end we’re making use of a binary called Autotrace which helps us calculate the boundaries of items [1].  Unfortunately there is no ruby interface for this library in rails just yet, so we needed to get a binary running on our Heroku Cedar instance. Luckily it was pretty easy to do.

Here’s how to use binaries with Rails on Heroku:

Keep reading »

  1. This makes dragging items more intuitive: click on the item to drag it, click on the negative space to pan. So no more rectangles to confine your images! []

TESTING AGAINST INTERNET EXPLORER IS NEVER FUN. That’s an understatement.

Even though at Bindle we limit our support to IE9, we still fear the obscure IE bug. It leads to an aversion to booting up a Windows 7 VM. jQuery + Compass have (greatly) reduced the worries over IE quirks, but from time to time I am still left shaking my head.

These days I find I can get away with deferring IE testing until towards the end of a release process, as most of the time all we need to do is double check things look and behave right. So imagine my surprise when seeing this while loading our latest release: Keep reading »

In response to this experiment from a couple of years ago.

I often wonder about when it’s appropriate to use helpers or partials in Rails. There’s the ideological question (answered well in this post).

However, there’s also a performance question. You can’t help but feel that helpers are better when you see things like this in your logs:

Rendered selections/_list_item.html.erb (11.5ms)
Rendered selections/_frame.html.erb (17.0ms)
Rendered selections/_list_item.html.erb (0.3ms)
Rendered selections/_frame.html.erb (2.2ms)
Rendered selections/_list_item.html.erb (0.2ms)
Rendered selections/_frame.html.erb (2.0ms)
...and so on when you are rendering a lot of partials

Keep reading »

  • Search: