Improvement for the "developer workflow". We better structure the repository so developer-only file that mix with "user files".
Changed
dev directory renamed to .dev
removed DCC scenes/prefs/launchers from .dev
move "sources" files of various implementations to .dev
Notes
The correct way to do this would be to:
remove all "user files" from the main branch
store sources files int he main branch
have a build process that convert source files to "user files".
publish the result of the build process in the github releases
But this solution was not adopted cause it would break "backward compatibility" of the repo structure and its URLs. It would also increase complexity.
The other solution was to develop an alternate git branching workflow like this (similar to git flow):
But it would be too complex so I ended up on this simple solution which is having everything in the main branch, but isolating source files in the .dev directory.
Changelog
Improvement for the "developer workflow". We better structure the repository so developer-only file that mix with "user files".
Changed
devdirectory renamed to.dev.dev.devNotes
The correct way to do this would be to:
The other solution was to develop an alternate git branching workflow like this (similar to git flow):
But it would be too complex so I ended up on this simple solution which is having everything in the main branch, but isolating source files in the
.devdirectory.