jn
/
punkshell
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
256 Commits
1 Branch
1 Tag
155 MiB
 
 
 
 
 
 
Tree: 463add24fb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '463add24fb'
${ noResults }
punkshell/src/project_layouts
Julian Noble 856fab4c88
punk::repl extra stdout flush - comments regarding stderr/stdout interleaving 		2 months ago
..
custom punk::repl extra stdout flush - comments regarding stderr/stdout interleaving 2 months ago
vendor
…
README.md
…

README.md

project_layout information

project layouts don't show as available unless referenced by an entry in a layout_ref folder within the src/decktemplates structure.

This is because some layouts may be intended for use with child projects generated from 'deck project.new' - but not directly by this parent project.

The structure of decktemplates and project_layouts is designed to avoid circular dependencies arising during creation of layouts for child projects - that may then need to in turn support the same layout if the child project creates projects.

Layouts are not included in the resource files of modules for the same reason. (modules may need to be included in layouts) Instead they are pointed to via the decktemplates custom & vendor structure.

layouts within project_layouts/vendor should generally not be customised directly The vendor layouts should be created and updated by loading the appropriate vendor modules. These are plugin modules that are providers of the punk.projectlayout capability (see punk::cap module documentation and the project_layouts/vendor/punk/sample-0.1 layout)