durandal

In my HotTowel based project, I'm using Durandal 1.1.1 for routing. I have a login route, which I want to activate if the user is not logged in. my route config is like: var routes = [ { url: 'login', moduleId: 'viewmodels/login', name: 'Login', visible: true, caption: 'Login' },{ url: 'moduledetail/:id', moduleId: 'viewmodels/moduledetail', name: 'ModuleDetail', visible: true, caption: 'ModuleDetail' } I want if user want to go #/moduledetail/1 and is not authenticated yet, the browser navigate to route #/login/moduledetail/1 so after successful login route back to the #/moduledetail/1 . A

I have a regular anchor tag with href attribute set to "#". Normally, this prevents from any navigation but in durandal it navigates me to the home view. How can I stop it from navigating to that view? I can't change the html and stylings. It needs to be that anchor tag. But I can bind a click event to it. Is there any way to cancel navigation in anchor click event? regards Evan Larsen Bind a click event to it and call event.preventDefault() <a href="#" id="someAnchor">Example</a> $(function() { $('#someAnchor').click(function(event) { event.preventDefault(); }); }); This will prevent the

I am trying to use the "any" operator in Breeze to query a many table and I am getting the following error - TypeError: Unable to get value of the property 'isAnonymous': object is null or undefined The only stackoverflow question I can find that seems related is this one, but there is no solution to the isAnonymous issue because the poster did not provide more code: breeze projection : error selecting non scalar navigation properties I am using Breeze 1.4.11 with Entity Framework 5 The query I am trying to run is var getEntities = function (entitiesObservable) { var whereClause = "";

Let's say I have the following durandal code: define(['durandal/app', 'plugins/http'], function (app) { var vm = function(){ var self = this; self.myData = ko.observableArray([]); } }; vm.activate = function() { this.myData([]); }; vm.deactivate = function(){ }; return vm; }; I know by returning a constructor function, every time the view model is activated, it will return a new instance. My question is: is there anyway that when I access, if there's myData() from previous access, then I don't want to set this.myData([]); but to use the previous myData() ? I know by returning a singleton

I have 3 routes: items/one, items/two, and items/three and they're all pointing to 'items' vm/view. in the items.js activate function, I'm checking the url, and based on that, I'm changing a filter: function activate(r) { switch (r.routeInfo.url) { case 'items/one': vm.filterType(1); break; case 'items/two': vm.filterType(2); break; case 'items/three': vm.filterType(3); break; } return init(); //returns a promise } The items view has a menu with buttons for one, two, and three. Each button is linked to an action like this: function clickOne() { router.navigateTo('#/items/one'); } function

I'm trying to eliminate "css modal windows" (modal windows are not mobile device best friends) of a web client side application (SPA), built with DurandalJS version 2. I would like to convert the modal windows to full page dialogs. It would still be a dialog window but instead of superimpose the div over the current view, I would like to hide the current view (while keeping its state) and show the div containing the dialog (using the "entrance" transition if possible or a similar technique - to keep a consistent flow). I think I am close to a solution. The two options I'm trying at the moment

I am working on a SPA using Durandal, and I have created a widget for displaying a particular page component. Following the Durandal Documentation , the widget is in app/widgets/my-widget and is composed of viewmodel.js and view.html . Now, I want to add a different view to the same widget - in effect, to have a "Basic" view and an "Advanced" view, with a flag in the ViewModel for which one will be used. I do not want to create two different widgets, because the ViewModel is exactly the same and I want to avoid unnecessary code duplication. I also do not want to put both versions of the view