Corrected a problem with relative path resolution

I was getting console errors of the following form when attempting to access views in a subfolder ("views/subcontent") that refer to the layout with a relative path (i.e. {>"../layout"/}):

`Error: ENOENT, open '/usr/noderoot/angular-example-projects/angular-socket-io-minimal/layout.dust'`

Above the 'views' folder was being lost altogether.  In other test cases dust was looking for layout.dust in the same folder as the sub-view file iteself despite of the relative reference.  On the client side the affected pages would fail to display correctly.  

I traced the problem to **this.getFullPath** function where pathlib.resolve params were incorrect; you can merge this pull request as-is, or use it as a starting point for a fix (I may not have considered all the edge cases it might impact).