Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
sinatrarb
Home
+ new post
About this group
Join this group
Message from discussion Separating actions into multiple files
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Thomas Sullivan  
View profile  
 More options Aug 3 2009, 9:33 am
From: Thomas Sullivan <sulliva...@gmail.com>
Date: Mon, 3 Aug 2009 09:33:56 -0400
Local: Mon, Aug 3 2009 9:33 am
Subject: Re: Separating actions into multiple files
Print | View thread | Show original | Report this message | Find messages by this author
I'm still grasping the best method between having a straight program
or a "modular" one that requires sinatra/base - most of my skeleton
apps have been small enough, but lately I've wanted to toss them up
into Heroku and think the sinatra/base method is best.

A bit of a digression here, just saying that the idea of having a
"best method" may work for some - but the "simplest" method may be the
one we want in the docs.

On Mon, Aug 3, 2009 at 9:30 AM, Rick  Moynihan<rick.moyni...@gmail.com> wrote:

> On Jul 31, 2:16 pm, Alex Chaffee <ale...@gmail.com> wrote:
>> Update: I went ahead and used the "extension" technique suggested by
>> Marcos. It works OK but is a little verbose for my taste. I'll post a
>> sample of what I have to a gist right now and I'll integrate it into
>> Vegas when I get some time.

>> http://gist.github.com/159216

> A question... The Sinatra extensions page ( http://www.sinatrarb.com/extensions.html
> ) indicates that when creating a module you should place it in the
> Sinatra namespace and explicitly call register.  Yet your module
> doesn't appear to do this.  Is this deliberate or not?

> I'm not entirely clear why the pattern below is important...  Is it to
> force classic apps to register modules without an explicit call to
> register?

> module Sinatra
>  module MyModule
>    #... stuff here
>  end
>  register MyModule
> end

> Should modules be registered within the Sinatra namespace as above?
> Or should they be defined as in Alex's gist, i.e. in their own
> namespace with no call to register.  Either way some clarification of
> these issues on the extensions page would be great! :-)

> R.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google