start splitting BondsTable notebook into separate files #17
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.
This PR starts splitting the big notebook defining the StructBond into multiple julia files.
Initially the idea was to split this into smaller notebooks that are joined together using the new
@fromparent
macro from PlutoDevMacros.Eventually this will be done as part of normal julia files, and
@fromparent
is probably just gonna be used to test the functionality within a notebook.It's cool to have all the functionality in a single notebook but it can be quite heavy to load for doing changes, and it can also be quite daunting to look at the huge source file of the notebook, especially with the huge additions (in terms of line numbers) due to cell delimiters, cell order and most importantly Manifest file inclusion
Splitting is done.
Added also a notebook internal to the structbond folder for testing the specific functionality and live changes exploiting the
@fromparent
macro