Databases
StackOverflow2013
Postsdbo
POReusing/sharing views & models in different projects with Durandal JS
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReusing/sharing views & models in different projects with Durandal JS
    primarykey
    data
    text
    <p>I'm building multiple applications using Durandal JS. All those applications are located on the same server under the same document root and share some common code. For example they all use the same model &amp; view for login.</p> <p>How can i reuse/share the login model &amp; view in all those applications without just copy &amp; pasting the files to the projects?</p> <p>I already tried something with the following folder structure:</p> <pre><code>ProjectsDir/Project1/app/durandal/.. /models/Shell.js, Main.js, ... /views/Shell.html, Main.html, ... /main.js /main-built.js ProjectsDir/Project2/app/durandal/.. /models/Shell.js, Main.js, ... /views/Shell.html, Main.html, ... /main.js /main-built.js ProjectsDir/ProjectsBase/app/models/Login.js /views/Login.html </code></pre> <p>This way it would be possible to reference the same login model &amp; view in my ProjectsBase from all other projects by setting the correct route to it in the respective shell.js. This route could look something like this:</p> <pre><code>router.map([ { url: 'Login', moduleId: '../../ProjectsBase/app/models/Login', name:'Login', visible: true }, { url: 'Main', moduleId: 'models/Main', name:'Main', visible: true } ]); </code></pre> <p>This works as expected during debugging but building the production version with the durandal optimizer unfortunately doesn't work. Actually building does work (it produces the main-built.js just fine) but when i launch the site with the production file referenced i get the following error:</p> <pre><code>Uncaught Error: undefined missing durandal/../../../MPBase/durandal-app/models/Login </code></pre> <p>I'd really appreciate any ideas on how I could make the built production file work with the setup I described above.</p> <p>Of course I'm also open for other ideas on how to make models &amp; views reusable/sharable between multiple projects.</p> <p>Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsuamikim
    1. USsuamikim
    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
    1. VO
      singulars
      1. POReusing/sharing views & models in different projects with Durandal JS
      1. USAlexander Preston
      1. VTFavorite
    1. COwhats your current build process? do you use grunt?
      singulars
      1. POReusing/sharing views & models in different projects with Durandal JS
      1. USEvan Larsen
    2. COI don't really have a build process right now. The projects I'm talking about are basically not too large and only for private use so the build process would be to combine/minify all files with the Durandal optimizer manually and upload them to the "production" location on my server afterwards. I've already received an answer to my question on [Durandals Google Groups](https://groups.google.com/forum/?fromgroups=#!topic/durandaljs/sYZO79Db_JM) which seems quite promising. I'm going to answer this question myself after I've successfully tried the suggestions from there...
      singulars
      1. POReusing/sharing views & models in different projects with Durandal JS
      1. USsuamikim
 

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