The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
The package can be loaded in a code chunk within the Rmarkdown file:
library(namedropR)
As sample references we’ll use three fictional BibTeX entries stored in a file called ‘library.bib’.
@article{doe2024,
title = {When Inspiration Meets Passion: Translating Ideas into Practice},
author = {Doe, John and Sample, Anne},
year = {2024},
journal = {Journal of Unneccessary R Packages},
url = {https://nucleic-acid.github.io/namedropR/},
}
@article{active2021,
title = {Where Frustration Meets Essentiality: An Introduction to Unit Testing},
author = {Active, Alice and Boring, Bob},
year = {2021},
journal = {Journal of Unneccessary R Packages},
url = {https://nucleic-acid.github.io/namedropR/},
}
@article{fantastic1998,
title = {Why Writing Packages Matters: Sharing is Caring},
author = {Fantastic, Flora and Curious, Claire},
year = {1998},
journal = {Journal of Unneccessary R Packages},
url = {https://nucleic-acid.github.io/namedropR/},
}
The file can be read and converted to a tibble using the {bib2df} package like this:
# load required packages
library(bib2df)
library(dplyr)
# read the file
<- system.file("testdata", "library.bib", package = "namedropR")
bib_file <- bib2df::bib2df(bib_file) %>%
bib select(BIBTEXKEY, AUTHOR, YEAR, TITLE, JOURNAL, URL)
Let’s have a glimpse of the the resulting tibble:
::glimpse(bib)
dplyr#> Rows: 3
#> Columns: 6
#> $ BIBTEXKEY <chr> "doe2024", "active2021", "fantastic1998"
#> $ AUTHOR <list> <"Doe, John", "Sample, Susan">, <"Active, Alice", "Boring, B…
#> $ YEAR <dbl> 2024, 2021, 1998
#> $ TITLE <chr> "When Inspiration Meets Passion: Translating Ideas into Pra…
#> $ JOURNAL <chr> "Journal of Unneccessary R Packages", "Journal of Unneccessa…
#> $ URL <chr> "https://nucleic-acid.github.io/namedropR/", "https://nuclei…
The references are successfully read to a tibble for further usage.
Note: It is possible to directly pass the *.bib file to the drop_name() function which reads and extracts the necessary data. However, when the bibliography is large and visual citations are rendered frequently, there might be significant performance improvements by reading the bibliography only once (like above) and pass the tibble to drop_name().
drop_name()
can either create raster graphics in the
form of ‘PNG’ files or ‘HTML’ files. When ‘PNG’ is the desired output,
there are three ways to embed the rendered ‘visual citations’.
{knitr}
packageOne way of embedding visual citations as PNG is
knitr::include_graphics()
.
::include_graphics(drop_name(bib, cite_key = "doe2021", export_as = "png")) knitr
Using {knitr}
has the advantage, that it works well with
‘bulk dropping’. This means, that you can pass the entire bibliography
(or a subset thereof) to the function and knitr embeds all resulting PNG
files one after another, using one line of code:
# all entries
::include_graphics(drop_name(bib, export_as = "png"))
knitr
# some entries
::include_graphics(drop_name(bib, cite_key = c("doe2021", "fantastic1998") export_as = "png")) knitr
{htmltools}
packageAnother way to embed PNG ‘visual citations’ is
htmltools::img()
, which creates an HTML
<img>
tag that points to the PNG file:
::img(
htmltoolssrc = drop_name(bib, cite_key = "active2021", style = "classic", export_as = "png")
)
In the above example we pass the output of drop_name()
,
which is the file path to the rendered ‘visual citation’ as source
string of the <img>
tag.
With htmltools::img()
‘bulk dropping’ is not
possible, but there is another significant advantage:
It is possible to style the embedded image further using ‘CSS’ code. One
idea could be to draw a frame / border around the image, another is
drawing a tiny shadow around the ‘visual citation’, to give it the
impression of floating slightly above the document or slide.
The ‘CSS’ style needs to be applied to a <div>
tag
around the actual <img>
tag:
::div(
htmltoolsstyle = "box-shadow: 5px 5px 6px grey;border: solid;border-color: #EEEEEE; border-width: 1px;",
::img(src = drop_name(bib, cite_key = "fantastic1998", export_as = "png"))
htmltools )
The above example draws a thin light-gray border around the ‘visual citation’ and a shadow at the bottom and right edges, which gives a floating impression in the rendered document.
If you are experienced in ‘CSS’ there should be no limits in how the embedded image should be set apart from the surrounding content.
Of course, it is possible to manually write the
<img>
tag, as Rmarkdown can read and interpret raw
‘HTML’. The previous, styled example could be written as:
<div style="box-shadow: 5px 5px 6px grey;border: solid;border-color: #EEEEEE; border-width: 1px;">
<img src="path/to/fantastic1998.html.png"/>
</div>
The second format supported by namedropR
is ‘HTML’.
While this doesn’t provide raster graphics (that could be used in other
places as well), this reduces the file size of the rendered document, as
they only consist of ‘HTML’ code. Another advantage is the possibility
to apply custom ‘CSS’ to the ‘visual citation’ itself, not just the way
it is embedded. For details of custom CSS styles, please refer to the
main vignette.
Embedding a ‘visual citation’ as ‘HTML’ can be achieved like so:
::includeHTML(
htmltoolsdrop_name(bib,
cite_key = "active2021",
export_as = "html",
use_xaringan = TRUE
) )
NOTE 1: When using
htmltools::includeHTML()
, the HTML file is actually
integrated into the knitted Rmarkdown output. Hence the default function
call would break the VC, as the original VC embeds the QR via a relative
link to the QR-subfolder of the original output path.
use_xaringan = TRUE
handles this by storing the QR code
directly in a subfolder of the working directory, so the relative link
to the QR code (after integration of the ‘VC’ to the knitted output
points to the right place.
NOTE 2: This relative path management should be necessary for all Rmarkdown HTML documents, not only xaringan slides. The options name is a result of the initial focus of this package.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.