Article: Open Says Me


#1

I just finished my latest contribution, “Open Says Me”.

http://unspace.ca/discover/opensaysme/

Managing the browser experience using JavaScript, Ajax and a Cookie.

It’s built on top of Rails, of course. Feedback is always appreciated!

Pete


#2

On 4/26/06, Pete F. removed_email_address@domain.invalid wrote:

I just finished my latest contribution, “Open Says Me”.

http://unspace.ca/discover/opensaysme/

Managing the browser experience using JavaScript, Ajax and a Cookie.

It’s built on top of Rails, of course. Feedback is always appreciated!

Great article, love the idea, the only thing that turns me off is the
need
for multiple controllers. I’m wondering if you can use respond_to, or a
similar mechanism to handle the backwards compatibility. By keeping a
single controller you are reducing the risk of repeating your business
logic
in multiple places.

Something like this perhaps:

def show
broswer.supports do |type|
type.flash?
render ui.flash
type.cookies? && type.ajax?
render ui.v2.0
default
render ui.v1.0
end
end

Thoughts?

Josh


#3

Hey Josh!

Thanks for the kind words.

I try to keep my articles super-conceptual so that people that read them
are more likely to apply the ideas to their problem domain.

before_filter is awesome for its’ simplicity, but in lots of cases -
it’s overkill. respond_to would definately work on a per-page basis.

See - when I write, I always try to sneak in gratuitous “look how easy
this was to do with Rails!” subliminal messages. PHP developers don’t
have before_filter functionality. *

Pete

  • do they?
    ----- Original Message -----
    From: Josh K.
    To: removed_email_address@domain.invalid
    Sent: Wednesday, April 26, 2006 6:13 PM
    Subject: Re: [Rails] Article: Open Says Me

    On 4/26/06, Pete F. removed_email_address@domain.invalid wrote:
    I just finished my latest contribution, “Open Says Me”.

    http://unspace.ca/discover/opensaysme/

    Managing the browser experience using JavaScript, Ajax and a Cookie.

    It’s built on top of Rails, of course. Feedback is always
    appreciated!

    Great article, love the idea, the only thing that turns me off is the
    need for multiple controllers. I’m wondering if you can use respond_to,
    or a similar mechanism to handle the backwards compatibility. By
    keeping a single controller you are reducing the risk of repeating your
    business logic in multiple places.

    Something like this perhaps:

    def show
    broswer.supports do |type|
    type.flash?
    render ui.flash
    type.cookies? && type.ajax?
    render ui.v2.0
    default
    render ui.v1.0
    end
    end

    Thoughts?

    Josh



Rails mailing list
removed_email_address@domain.invalid
http://lists.rubyonrails.org/mailman/listinfo/rails


#4

Pete F. wrote:

See - when I write, I always try to sneak in gratuitous “look how easy
this was to do with Rails!” subliminal messages. PHP developers don’t
have before_filter functionality. *

Pete

  • do they?
    At the php.ini-level, yes. You can specify a file to get processed
    before anything else gets loaded.

I added something more similar to before_filter to a PHP framework I was
working on last year which, over time, started to look remarkably
familiar :slight_smile: