This event should include both the current url and the path segments, split on /.

For example, when navigating to /user/marius/1234, it would produce the following event:

thePageHasChanged('/user/marius1234', ['user', 'marius', '1234']);

This includes 404 messages

An observable only has one validator, but can be used in multiple commands/queries, which have different validation rules. This causes trouble!

This is usually the case when the server has thrown an exception. The exception should be handled instead.

When executing a command/query there should be a way to react to the result/success/failure, without using the success, result, error callbacks. This is useful when the executable can be called from multiple places but should have a different success callback.

Currently it lists them with a comma between (without a space), but they should probably be listed one on each line

There should be a special type of bindings/viewmodels that only work on the selected element, not its children. This usually involves a single custom binding, so instead of having a viewmodel, a binding and a stopBinding, it could be something like this:

<div data-binding="slideIn: {width:200}">
  <!-- other content here -->
</div>

which would be translated to something like this:

<div data-viewmodel="AnonymousVM" data-bind="slideIn: {width:200}, stopBinding: true">
  <!-- other content here -->
</div>

error messages thrown while the spa is starting aren't very nice in Firefox

It should be reset to isBusy = false

Currently it is a very non informative error. It should include the command/query name and the field name

Setting this header will inform asp.net that the request is an ajax request. This can be done by adding the following line to ajax.js on line 46

xhr.setRequestHeader('X-Requested-With', 'XMLHttpRequest');

error is a bit strong,especially when the executable does not execute because something is invalid. failure is a more descriptive word.

Currently it fails silently. If the value is not an observable, it should probably say that it needs to be an observable.

When the page is unloaded the ViewModels should be notified. An event listener on the when object passed as the first parameter to the constructor can do this. It should probably work like this:

when.thisPageIsUnloaded(function(){
  console.log("I am unloaded");
});

The spa should either start and work or throw an error when the outlet is missing on the page

For example: [Event somethingHasHappened]

The code should throw an Error with the message that the server threw an exception

Instead of having to create the command or query and then executing it, have it immediately execute.

qvc.command("DoSomething", {
    param1:true, 
    param2:45
  }).success(function(){
    callback();
  });

This should not fetch the validation constraints, since they are not needed. It still needs to extend the parameters, in case the server returns a validation result.

Make sure that an observable isn't extended multiple times!

It must be added to the page as a script tag. There should be a way to load it dynamically, by setting the location in the config file

This produces better tests when sinon is used

See https://github.com/froots/jasmine-sinon

Currently it fails if a field with no constraints is not an observable. It should quietly allow this

Currently model (the first argument to viewmodel constructors) is null when there is no data-viewmodel. It should default to an empty object

In the config there should be hooks for when the page has loaded and when the page has been bound to viewmodels, so other declarative components can be used. These hooks should take the element of the current page (ie, the outlet) and a callback for when the page is destroyed (so event listeners can be released). An example:

ordnung.config({
  spa:{
    onPageLoaded: function(pageElement, onPageElementDestroyed){
      myDeclarativeLibrary.findInElement(pageElement);
      onPageElementDestroyed(function(){
        mDeclarativeLibrary.release(pageElement);
      }
    }
  }
}).start();

Seems something has gone wrong with the require optimization.
Maybe the packages option doesn't work well with the constraints

An error message sent from the server like "{0} is required" should have the name of the property interpolated in, so it ends up like "name is required". Maybe the value can be {1}

Not sure how though...

When ordnung copies script tags it does not copy the type of the script. All script tags are interpreted as JavaScript. This means knockout templates cannot be used.

In addition, a page should be able to contain templates for that page. This requires nesting though! It might work, but the template must be prefixed with the path of the current page

Currently there is no simple way to find all the invalid fields. One solution would be to attach a callback which is called whenever the executable is executed, but validation fails. The parameter passed to this callback would be a list of invalid fields

If the url passed to ajax has a queryString, then an additional question mark is added to the end. It should add an ampersand with the rest of the query string behind it

This means that bindings cannot be added to the outlet. Not sure how this will work with knockout, especially with virtual elements being used.

This shows up when you listen to the ordnung.thePageHasChanged event, where segments now contains %C3%B8 instead of ø. This can lead templates containing special characters not to load on safari (iOS and OSX).

To fix this, call decodeURIComponent on the path segments before calling the pageChanged listener from the hashNavigation class.

This needs thourogh testing, which must be run on safari!

It should use the current document if no document parameter is passed to it, but this fails. The error is in file spa.js:48

It should be true after any field has changed, and false right after the command/query has executed. This can be used to show a "Saved!" message

Knockout 3.0 has a number of fixes and performance improvements. Ordnung should use Knockout 3.0

Chrome complains about them, saying they are unsafe. They probably are...

Either the content returned by the server should be output, or a special 404 page should be loaded (from template or from the server)

This means that the validation error for the entire command/query cannot be displayed. This causes the silent error in #26.

IE caches pages, because they have no cache busting.

Instead of using hash based navigation, use pushState when navigating to a new page.

This requires that a few issues need to be solved:

• global link listener?
• global form submit
• programmatic navigation

This would be great for scenarios where throttle is used to trigger a query. If the user types slowly, triggering many queries, then subsequent executions are discarded until the request finishes.

The syntax would probably be something like this:

qvc.createQuery("Search", {query:query}).blockWhileBusy(false);

This probably requires an abort method on the executable. It could be used from within beforeExecute to create this effect.

In general there should be a better error handler here

data-loading is true after the page has loaded, but before the viewmodel has been applied. This screws up css selectors. There should instead be a data-page-status with the following states:

• Loading (the template or page is being loaded)
• Rendering (the innerHTML is updating)
• Applying ViewModels (The viewmodels are loading and running)
• Active (Loading is done, the page can be used)

Better names for these states are needed