Project File Structure #253
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For version 0.7, the file structure of a novelWriter project is changing. The document files are now saved in one folder, instead of being split across 16 folders. Their filenames are also simply the handle + the .nwd extension.
The more complex structure was created early on when there was meant to be more meta files and other supporting file, making a single folder potentially fairly large. This is no longer the case, so that approach is being dropped. A single folder for the documents also makes it easier to use versioning tools on the project, as you only have to add one folder to the versioning tool each time you make new project files.
This causes a bump in the file version of the project file itself. Since project item meta values are now settled for the 1.0 release feature set, this is a good time to draw a line and say an break backward compatibility with older versions of novelWriter.
When a project is opened in the dev branch, or after 0.7 is released, a dialog will ask if the user wants to upgrade their project. After this, the project can only be opened with version 0.7 or later.