Vignette for pacman
Would a vignette be something we would want to make at some point? I'm thinking it would be a good idea but I'm too lazy to make one right now.
I'm assigning this to Milestone 2.0
I figure once we feel we can release the package to the general public either via advertising or a release on CRAN we'll turn the version number to 1.0. Once we've cleaned it up more and added a vignette we'll turn to 2.0.
I agree. I know I need to make a vignette for the qdap package but pacman should be pretty intuitive. I think we could get away without a vignette on the first release.
Hold off as R 3.0 and knitr 1.1 will play together to make vignettes: https://github.com/yihui/knitr/blob/master/NEWS.md
And officially...
http://yihui.name/knitr/demo/vignette/
I'd love to write this in markdown
I started an Introduction to pacman vignette,
We need to make the following decisions:
- [ ] pdf or html (which)?
- [ ] if html css choice including (could use default)
- [ ] outline (what to put in there) that will/could be used as a table of contents
Thinking on the Outline
I think we're want this to be pretty light weight and include the most useful functions in that order. I think we may want to include a base equivalent if there exists (not sure on this) as a table; so for example:
| pacman function | base equivalent | description |
|---|---|---|
p_load |
install.packages + library |
loads and optionally installs packages |
p_install |
install.packages |
installs packages from CRAN |
Here's where I've done this for the dplyr package: https://github.com/trinker/dplyr_in_a_nutshell#relating-the-functions
My list of most useful function In order of usefulness
-
p_load -
p_funs -
p_data -
p_unload -
p_temp -
p_cite -
p_delete -
p_vign -
p_ver - ...
As I make this list I'm not sure order of importance is the best way to go. I'm going to look at hadley's vignettes and steal...
Maybe a better approach is to categorize/group functions. This would help for making a staticdocs page anyway and force us to organize our thinking.
Here is my categorization:
-
Installing, Loading, Unloading, Updating, & Deleting
-
_Installing and Loading_
-
p_load -
p_install/p_get -
p_temp
-
-
_Unloading_
-
p_unload
-
-
_Updating_
-
p_up/p_update
-
-
_Deleting_
-
p_del/p_delete
-
-
_Installing and Loading_
- Session Information
-
p_loaded
-
- Local Package Information
-
p_author -
p_cite/p_citation -
p_data -
p_exists -
p_funs/p_functions -
p_help -
p_info/p_information -
p_inter/p_interactive -
p_isloaded -
p_news -
p_ver/p_version -
p_vign/p_vignette
-
- Internet Based Package Information
-
p_cran -
p_search_any/p_sa
-
- Library Information
-
p_base -
p_lib/p_library -
p_path -
p_sl/p_search_library -
p_unlock
-
- pacman Tools
-
p_detectOS -
p_isglobal -
p_opendir
-
I think the table would only be for the first group and would be as follows:
| pacman Function | Base Equivalent | Description |
|---|---|---|
p_load |
install.packages + library |
Loads and Install Packages |
p_install |
install.packages |
Install Packages from CRAN |
p_temp |
NONE | Install a Package Temporarily |
p_unload |
detach |
Unloads Packages from the Search Path |
p_update |
update.packages |
Update Out-of-Date Packages |
Bur maybe this wouldn't be too hard to do for each section as a quick reference?
I added a skeletal to the vignette per these comments so we can try it on. See:
http://htmlpreview.github.io/?https://github.com/trinker/pacman/blob/master/vignettes/Introduction_to_pacman.html
We will want:
- Better styling of the table (more like GitHub's)
- ...
We will want to think about styling here.
I added a second vignette that's a quick reference of categorized functions. This uses the same tables as the intro vignette and they share the tables found in vignettes/tables for easier maintainability. Here are the two vignettes:
We have no References for the Intro vignette. Do we want to:
- Remove references
- Figure out appropriate references to put in there