Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO Items #1

Closed
2 of 14 tasks
eddelbuettel opened this issue Sep 2, 2017 · 3 comments
Closed
2 of 14 tasks

TODO Items #1

eddelbuettel opened this issue Sep 2, 2017 · 3 comments

Comments

@eddelbuettel
Copy link
Owner

eddelbuettel commented Sep 2, 2017

  • Add proper README.md possibly with png of a page or two, could use new Rcpp Intro
  • Rewrite or add lead to skeleton.Rmd to refer to rticles::pnas_article for help
  • Add markdown example for two-column figure
  • Add table example
  • Expand bib file adding PeerJ
  • Give proper credit to PNAS and rticles packages,
    • GPL-3 copyright from rticles carried over,
    • unclear what PNAS / Overleaf copyright terms are besides standard (liberal) TeX / TUG licensing
  • Ideally make all useful features accessible from yaml with fallbacks:
    • Watermark yes/no
    • doi entry, can be used as CRAN package URL
    • Package name used in footer left and right (currently Rcpp hardcoded)
  • A few PNAS sillynesses have been removed such as which author matters more, which conflicts of interest arose, what significance the paper has etc. This could be revisited but as a template for vignettes / paper drafts seems fine
  • Could possibly relax use of the two-col template from PNAS (but 'KISS' rules: simpler as is)
@coatless
Copy link
Collaborator

coatless commented Sep 3, 2017

1. Are you okay with using the tint README as a shell with a few modifications?
2. There probably should be a rewrite of the skeleton.Rmd to cut down on the PNAS specific lingo (after all Pinp Is Not PNAS)
3. Not sure about the approach for this one outside of creating a specific latex macro for it. (See the safe columns hack in uiucthemes::beamer_illinois.)
4. I'll add that in. Are you okay with a contingency table? (e.g. 3 x 3 with numbers being in the inner 2x2?
5. I'll toss in the PeerJ citation for Extending... Or, this could wait until TAS goes live?
6. LaTeX header, README, roxygen2 documentation, anything else?
- PNAS' main style is covered by LaTeX Project Public License >= version 1.3
7. Let me think about that...
8. Agreed. I don't really feel like that is needed at this point.
9. Two-col first and then enable one-col. The change-over is straightforward according to the rticles::pnas_article()

@eddelbuettel
Copy link
Owner Author

eddelbuettel commented Sep 3, 2017

1. README: Yes, I'll do that, and link to our PeerJ piece and show a page or two.
2. Skeleton: Probably.
3. Two-col Figure: Do we need a new macro? For PeerJ we just use figure*.
4. Table: Knitr can probably do it. See the commented-out PNAS example in skeleton. Possible Pandoc issue?
5. PeerJ cite: I'll add it when I do a first README. We can switch to TAS / add it once live.
6. Credits. Yep. In README too.
7. YAML: That is the only actual work. We also need to look at pnas_article again and pnas-new.cls
8. Simpler: Good.
9. Two and One Col: Ok

This format sucketh. New tickets for detailed discussion?

@coatless
Copy link
Collaborator

coatless commented Sep 7, 2017

Okay. I'm splitting up the issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants