Comments for Adam @ Bitscribe

Comment on Go Ahead, Do The Big Rewrite by The Big Rewrite - Other articles | Lazycoder

The Big Rewrite - Other articles | Lazycoder — Thu, 04 Oct 2007 16:28:50 +0000

[…] Adam Wiggins: Go Ahead, do the big Rewrite […]

Comment on Solution Without a Problem by Adam @ Dusk » Learning Through Information Bombardment

Adam @ Dusk » Learning Through Information Bombardment — Sat, 15 Sep 2007 04:35:19 +0000

[…] The reason I think that this approach works so well is what I call a solution without a problem. You might have had this happen to you before: you come across a tool at the hardware store for which you cannot fathom any use. Spending time to try to learn how the tool works would be a waste of time - it’s a solution without a problem. On the other hand, go try to do whatever it is the tool is for first. Once you have a mental model of the problem, examining the tool will make perfect sense. Respond / Trackback / RSS 2.0 Post a comment […]

Comment on Javascript Text Editor by Kevin Hoang Le

Kevin Hoang Le — Thu, 13 Sep 2007 00:01:34 +0000

Adam,

Your JavaScript text editor is very good. I hope to be able to use it in a near future project. The cursor seems a little short. Is there any way to fix that? Thanks

KHL

Comment on Zero, Blank, and Nil by Fun Facts about Rails: nil.blank? | thirdbIT

Fun Facts about Rails: nil.blank? | thirdbIT — Sun, 02 Sep 2007 17:17:09 +0000

[…] That’s useful, but I had either never read it, or had read it and forgotten it. Apparently I’m not the only one. […]

Comment on Comet with Rails + Mongrel by saracen

saracen — Thu, 16 Aug 2007 04:24:18 +0000

I think juggernaut solves this by using flash (an embedded .swf file that gets sent to the browser) and not javascript to do the connection. Flash doesn’t have the same port restrictions as javascript and so it gets around that problem.

Comment on Comet with Rails + Mongrel by Pete

Pete — Thu, 02 Aug 2007 16:01:05 +0000

Port 1 not equal Port 2

(my last post was somehow crippled)

Comment on Comet with Rails + Mongrel by Pete

Pete — Thu, 02 Aug 2007 16:00:16 +0000

> Comet can only connect to the same host (and port) the original request was from.

So how does juggernaut solve this?

Port 1: Webserver
Port 2: Juggernaut

Port 1 Port 2

Comment on Rails Change Logger by adam

adam — Fri, 27 Jul 2007 19:13:19 +0000

Keeping detailed audit records of what rows have changed is a whole other ball of wax - you’ll probably need several tables (i.e. change_log_rows, with columns like field_name, old_value, new_value). I’ve done this on some enterprise projects before (not written in Rails) and the data gets huge and unmanageable VERY quickly. I’d think carefully about how much this is really needed.

If you decide you need it, I recommend checking out acts_as_audited. They use a serialized hash in place of a table - less flexible and transparent, but a little lower impact on your schema.

Comment on Rails Change Logger by Kurt

Kurt — Fri, 27 Jul 2007 03:26:21 +0000

This is working fine for me, but on one of my sites, the client wants detailed change records, e.g. “jane status at datetime (priority: 1 changed to 2, owner: joe changed to jeff)”. Have any tips for me? I’m thinking of a ‘before_save’ method that compares the text of the before and after records and stores the diff. Or maybe it would be easier to version all rows, keeping all changes forever (acts_as_versioned, I think).

Comment on Comet with Rails + Mongrel by adam

adam — Mon, 16 Jul 2007 20:48:01 +0000

Michael -

Interesting, I hadn’t seen this before. (It should be noted that the term “Comet” actually originates in the Python world, as part of Dojo.) Here’s the Orbited homepage, but unfortunately the documentation is extremely sparse. (The “docs” link is a 404 error!) This appears to be the best bit of info: CherryChat