You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Basid doc theme
* try to add font
* Put variables before main import
* work in progress, too tired for tonight!
* color changes
* link color and hovering (and try to make travis work)
* consistent main colors
* faster build [CHANGE THIS LATER!]
* try on e more time to build on travis!!!!
* try to build on travis on final time
* slightly darker header color
* make selection part white
* decrease saturation, choose less colors, select=white
* make sidebar text black
* make other package links documetner accessible
* Fix shadow
* Use mp/theming branch of Documenter
Contains updates to sidebar color handling.
* imrpove colros and shadows
* make hyperlinks darker and more bluish
* Update Documenter
$code-background can now be overridden.
* Remove right border from sidebar
* Customize code blocks
* Customize search box
* ad awesome colors everywhere
* nice correct searchbar
* make mainwhite be pure white
* use color of theme in textbox hovering
* final tweaks, make hyperlink more green and more dark
* Update Documenter
Allow sidebar font sizes to be changed.
* add possibility of different font size for sidebar
* lighter hover color
* try to use dark theme.
* Dark theme based on light
* add some customization on the dark theme
* User correct dark theme structure
* separatefiles into composable header
* a lot of progress on dark theme; admonitions left to do
* final dark+white theme + code syntax
* fix admonitions
* fix code bg in admonitions dark
* Fix docstring shadow codeblocks
* move scss files to a central repo
* use raw path
* ignore manifest
* new documenter version
* reverse testing
* allow manifest
* delete manifest
* ignore manifest
Co-authored-by: Morten Piibeleht <morten.piibeleht@gmail.com>
@@ -8,14 +8,9 @@ It helps people manage their scientific projects (or any project for that matter
8
8
Specifically, it is a Julia package created to help people "deal" with their simulations, simulation parameters, where are files saved, experimental data, scripts, existing simulations, project source code, establishing reproducibility, and in general their scientific projects.
9
9
10
10
See the [Functionality](@ref) section to get an impression of what you can do with DrWatson. To install, simply type `] add DrWatson` in your Julia session.
11
+
DrWatson is part of [JuliaDynamics](https://juliadynamics.github.io/JuliaDynamics/), check out our [website](https://juliadynamics.github.io/JuliaDynamics/) for more cool stuff!
11
12
12
-
!!! info "JuliaDynamics"
13
-
DrWatson is part of [JuliaDynamics](https://juliadynamics.github.io/JuliaDynamics/), check out our [website](https://juliadynamics.github.io/JuliaDynamics/) for more cool stuff!
14
-
15
-
!!! info "Poster for DrWatson"
16
-
If you prefer having a concise and visual summary of DrWatson we have prepared a poster for it! Check out the [Poster](@ref) section!
17
-
18
-
!!! tip "Star us on GitHub!"
13
+
!!! note "Star us on GitHub!"
19
14
If you like DrWatson the please consider starring the [GitHub repository](https://github.com/JuliaDynamics/DrWatson.jl). This gives as an accurate lower bound of the number of people the software has helped!
20
15
21
16
## Rationale
@@ -61,9 +56,6 @@ DrWatson follows these simple principles:
61
56
62
57
This is why we believe DrWatson can help you focus on the science and not worry about project code management.
Copy file name to clipboardExpand all lines: docs/src/save.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,11 @@ This page discusses numerous tools that can significantly improve process of sav
3
3
4
4
These tools are also used in the examples demonstrated in the [Real World Examples](@ref) page. After reading the proper documentation here it might be worth it to have a look there as well!
5
5
6
-
!!! info "Saving and loading files"
7
-
In DrWatson we save and load files with the functions `wsave(filename, data)` and `wload(filename)`. These functions are further used in the tools below, like e.g. [`tagsave`](@ref) and can be overloaded for your own specific datatype.
6
+
In DrWatson we save and load files with the functions `wsave(filename, data)` and `wload(filename)`. These functions are further used in the tools below, like e.g. [`tagsave`](@ref) and can be overloaded for your own specific datatype.
8
7
9
-
In addition, `wsave` **ensures** that `mkpath` is always called on the path you are trying to save your file at. We all know how unpleasant it is to run a 2-hour simulation and save no data because `FileIO.save` complains that the path you are trying to save does not exist...
8
+
In addition, `wsave`**ensures** that `mkpath` is always called on the path you are trying to save your file at. We all know how unpleasant it is to run a 2-hour simulation and save no data because `FileIO.save` complains that the path you are trying to save at does not exist...
10
9
11
-
To overload the saving part, add a new method to `DrWatson._wsave(filename, ::YourType)` (notice the `_`). By overloading `_wsave` you get all the extra functionality of [`tagsave`](@ref), [`safesave`](@ref), etc., for free for your own types (`tagsave` requires that you save your data as a dictionary).
10
+
To overload the saving part, add a new method to `DrWatson._wsave(filename, ::YourType)` (notice the `_`). By overloading `_wsave` you get all the extra functionality of [`tagsave`](@ref), [`safesave`](@ref), etc., for free for your own types (`tagsave` requires that you save your data as a dictionary).
12
11
13
12
!!! warning "Saving and loading fallback"
14
13
By default we fallback to `FileIO.save` and `FileIO.load` for and types.
0 commit comments