Adding routers to app after it has started - backbonejs

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Adding routers to app after it has started
Received-SPF: pass (google.com: domain of aidan.feld...@gmail.com designates 209.85.160.47 as permitted sender) client-ip=209.85.160.47;
MIME-Version: 1.0
In-Reply-To: <CACbAZ06=HJ17XKe0j4V4CP8pCghdmxBgPLRj6eG9qUUfnnw...@mail.gmail.com>
References: <CACbAZ06=HJ17XKe0j4V4CP8pCghdmxBgPLRj6eG9qUUfnnw...@mail.gmail.com>
Date: Mon, 2 Apr 2012 16:50:21 -0400
Message-ID: <CAPgiXS5RSprBZwKB71O8QoxJ1w8aMAORxEMdLEJ58H1MXw5...@mail.gmail.com>
Subject: Re: [backbonejs] Adding routers to app after it has started
From: Aidan Feldman <aidan.feld...@gmail.com>
To: backbonejs@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8ff1caeeafbb4c04bcb85601

--e89a8ff1caeeafbb4c04bcb85601
Content-Type: text/plain; charset=ISO-8859-1

I don't think this is a great approach - the nice thing about the router is
that having the routes statically defined makes it easy to read.  I'd
personally do something like:

routes: {
  ...
  "the/path/less/traveled": "thePathLessTraveled"
},

thePathLessTraveled: function() {
  if ( this.extraFeatureLoaded ) {
    // do stuff
  } else {
    // error?
  }
}


On Mon, Apr 2, 2012 at 1:41 PM, Tauren Mills <tau...@groovee.com> wrote:

> Is there a way to add additional routers to an application after
> Backbone.history.start() has been executed?
>
> I have some rarely-used features of my application that are loaded
> on-demand after the application has already started. Some of those features
> need to add additional routes to the application. But since the feature and
> it's router hasn't been loaded at DOM ready, and Backbone.history.start()
> has already run, the routes aren't available.
>
> Would it be better to have one application level router instead of a
> router for each feature? If I did this, each feature would manually add its
> routes and callbacks to the main application router. Any thoughts on this
> approach?
>
> Thanks,
> Tauren
>
>
>
>
>  --
> The Unofficial Backbone.js Group
>

--e89a8ff1caeeafbb4c04bcb85601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I don&#39;t think this is a great approach - the nice thing about the route=
r is that having the routes statically defined makes it easy to read. =A0I&=
#39;d personally do something like:<div><br></div><div><div><font face=3D"&=
#39;courier new&#39;, monospace">routes: {</font></div>
<div><font face=3D"&#39;courier new&#39;, monospace">=A0 ...</font></div><d=
iv><font face=3D"&#39;courier new&#39;, monospace">=A0 &quot;the/path/less/=
traveled&quot;: &quot;thePathLessTraveled&quot;</font></div><div><font face=
=3D"&#39;courier new&#39;, monospace">},</font></div>
<div><font face=3D"&#39;courier new&#39;, monospace"><br></font></div><div>=
<font face=3D"&#39;courier new&#39;, monospace">thePathLessTraveled: functi=
on() {</font></div><div><font face=3D"&#39;courier new&#39;, monospace">=A0=
 if ( this.extraFeatureLoaded ) {</font></div>
<div><font face=3D"&#39;courier new&#39;, monospace">=A0 =A0 // do stuff</f=
ont></div><div><font face=3D"&#39;courier new&#39;, monospace">=A0 } else {=
</font></div><div><font face=3D"&#39;courier new&#39;, monospace">=A0 =A0 /=
/ error?</font></div>
<div><font face=3D"&#39;courier new&#39;, monospace">=A0 }</font></div><div=
><font face=3D"&#39;courier new&#39;, monospace">}</font></div><div><br></d=
iv><br><div class=3D"gmail_quote">On Mon, Apr 2, 2012 at 1:41 PM, Tauren Mi=
lls <span dir=3D"ltr">&lt;<a href=3D"mailto:tau...@groovee.com">tauren@groo=
vee.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Is there a way to add additional routers to =
an application after Backbone.history.start() has been executed?=A0<div><br=
></div>
<div>I have some rarely-used features of my application that are loaded on-=
demand after the application has already started. Some of those features ne=
ed to add additional routes to the application. But since the feature and i=
t&#39;s router hasn&#39;t been loaded at DOM ready, and Backbone.history.st=
art() has already run, the routes aren&#39;t available.<br>


<br>Would it be better to have one application level router instead of a ro=
uter for each feature? If I did this, each feature would manually add its r=
outes and callbacks to the main application router.=A0Any thoughts on this =
approach?</div>


<div><br></div><div>Thanks,<br>Tauren</div><span class=3D"HOEnZb"><font col=
or=3D"#888888"><div><br></div><div><br></div><div><br><br></div>

<p></p>

-- <br>
The Unofficial Backbone.js Group<br>
</font></span></blockquote></div><br></div>

--e89a8ff1caeeafbb4c04bcb85601--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
