spoonx / aurelia-view-manager Goto Github PK

I cannot build my project using aurelia-view-manager and typescript with errors in dist/aurelia-view-manager.d.ts:

Cannot find name 'ViewEngine'
Cannot find name 'ViewCompileInstructions'
Cannot find name 'ResourceLoadContext'
Cannot find name 'ViewFactory'

The problem is fixed when I add these missing types to import statement on line 3:

import {viewStrategy,useViewStrategy,ViewEngine,ViewCompileInstruction,ResourceLoadContext,ViewFactory} from 'aurelia-templating';

Views are created by a ViewFactory, so they don’t go through DI directly, but their internal components are created by DI. If you create a custom ViewStrategy, you can control whether or not the view is relative to the view model or not. The strategies implement a method “makeRelativeTo”. You can implement that but just ignore the file path it provides.

We could say that defaults from plugins are relative to the plugin. Anything user-provided is relative to the project.

I'm trying to figure out if Aurelia supports fully dynamic views and view models?

I'd like to have a blank slate (canvas), where the user can drag and drop elements to update an underlying model (schema) and where the canvas then responds by rendering the corresponding views (elements/components) to reflect this model.

Does view-manager (or Aurelia) currently support this or what would be need for this to be possible? Thanks!

@bas080 @RWOverdijk

import {Container} from 'aurelia-dependency-injection';
import {ViewManager} from './../view-manager';
import {RelativeViewStrategy, useViewStrategy} from 'aurelia-templating';

export function resolvedView(namespace, view) {
  let viewManager = Container.instance.get(ViewManager);
  let path        = viewManager.resolve(namespace, view);

  return useViewStrategy(new RelativeViewStrategy(path));
}

that's not a good idea. That's only likely to be the same container as used in a SPA. My guess is that it's not when using aurelia-testing. hence to make it proper the code from @Inject would need to be borrowed so that the right container instance will be used

see aurelia/dependency-injection#57

Allow configuring of view configs via aurelia-config.

In the README.md you have:

Run npm i aurelia-view-manager--save from your project root.

it needs to be

Run npm i aurelia-view-manager --save from your project root.

add space before --save

We should be able to just do .plugin('view-manager')

At the moment we have to provide a callback: .plugin('view-manager', function() {})