Skip to content

Latest commit

 

History

History
104 lines (92 loc) · 3.98 KB

TODO.org

File metadata and controls

104 lines (92 loc) · 3.98 KB

TASK LIST

Start adding pandoc syntax to files.

I need to figure out how to move combine DocItOut with md syntax

Move one macro from macros.sas into its own file

  • State “DONE” from “TODO” [2014-11-21 Fri 17:59]
  • State “DONE” from “TODO” [2014-11-10 Mon 13:11]
  • State “DONE” from “TODO” [2014-11-10 Mon 13:11]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:06]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:05]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:05]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:03]
  • State “DONE” from “TODO” [2014-10-26 Sun 19:39]
  • State “DONE” from “TODO” [2014-10-26 Sun 13:53]
  • State “DONE” from “TODO” [2014-10-22 Wed 21:23]
  • State “DONE” from “TODO” [2014-10-14 Tue 23:00]
  • State “DONE” from “TODO” [2014-10-11 Sat 18:44]
  • State “DONE” from “TODO” [2014-10-08 Wed 13:32]

Use StatRep pacakge for making pdf files of doc

Didn’t end up using StatRep, used a “hack” with DocItOut and pandoc

Update the README

  • [X] Include an installation and usage section
  • [X] Update the folders section
  • [X] Develop the style guide section
  • [X] Develop and describe a versioning system
  • [X] Point the style guide to my bin with the quickSASTags script

Make the SAS macros into an autocall library

Create tool to convert SAS comments into md or pdf

  • State “DONE” from “TODO” [2014-11-21 Fri 18:00]
  • State “DONE” from “TODO” [2014-11-10 Mon 13:21]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:04]
  • State “DONE” from “TODO” [2014-11-05 Wed 16:02]
It will need to also run through several files in the macro directory. Include a TOC. Didn’t end up using StatRep.

Develop a version numbering system

e.g. with each change to a macro = to 0.01 and a new macro as 0.1, while major changes = 1 (maybe?) Or, better yet, how about + 1.0.0 for major changes, + 0.1.0 for new macros, and + 0.0.1 for edits to existing macros from past release points.

Include the DocItOut pdf with the repo

Create a script to cut away quick tags (“) to real tags (<code>)

Create way to produce example documentation like in roxygen

Use a development branch vs a master branch

To have it more stable over time.

Add command in output_data to create a output dir