Databases
StackOverflow2013
Postsdbo
POAngularJS - templating with sub-routes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAngularJS - templating with sub-routes
    primarykey
    data
    text
    <p>I'm quite new to Angular.js and I can't seem to figure out how to solve my problem.</p> <p><strong>The app</strong> consists of three main tabs which are also top-level routes, ie.</p> <pre><code>#/home #/inbox #/products </code></pre> <p>The current route-configuration looks something like this (coffeescript):</p> <pre><code>$routeProvider. when('/home', templateUrl: 'home.html'). when('/inbox', templateUrl: 'inbox.html'). when('/inbox/:thread_id', templateUrl: 'inbox.html', controller: 'MessagesCtrl'). otherwise(redirectTo: '/inbox') </code></pre> <p>Now, the <strong>problem is the inbox view</strong>. </p> <p>The inbox view (<code>inbox.html</code>) is a split column template with a list of message-threads to the left and the messages of the selected thread to the right:</p> <pre><code> -------------------------- | Navigation | -------------------------- | | | | Threads | Messages | | | | | | | </code></pre> <p>The list of threads should be visible for all <code>#/inbox</code> routes no matter if a thread has been selected or not.</p> <p>As you can see from the routes, the inbox view is a separate template (<code>inbox.html</code>) which is loaded both when a thread is selected and when it's not. This makes Angular re-render the entire view each time a thread is selected, which also causes the thread-list (to the right) to re-render and loose its scroll-position.</p> <p>I would like to keep the thread-list from re-render whenever a thread is selected and I can't seem to figure out how to organize my routes/templates in order to achieve this.</p> <p>Any suggestions would be greatly appreciated!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USsewa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAngularJS - templating with sub-routes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAngularJS - templating with sub-routes
      1. UShonzajde
      1. VTFavorite
    3. VO
      singulars
      1. POAngularJS - templating with sub-routes
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODid you tried to add [reloadOnSearch=false] parameter to your route definition object where you dont whant reload?
      singulars
      1. POAngularJS - templating with sub-routes
      1. USValentyn Shybanov
    2. COThanks! Unfortunately it doesn't help. To my understanding, $location.search() only refers to the query-string-part of the URL (http://docs.angularjs.org/guide/dev_guide.services.$location).
      singulars
      1. POAngularJS - templating with sub-routes
      1. USsewa
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload