-
Notifications
You must be signed in to change notification settings - Fork 1
Description
As of right now, we have these files:
otsletter.cls
texMemo.cls
contract.cls
ots.sty
invoice.cls invoice.sty
otsreport.cls otsreport.sty
Commit 7fa4dff brought to my attention that we're not that clear on what kinds of things should go into which ones, and which of the above should include which other of the above.
For example, should otsreport.cls
just include ots.sty
, so that (say) a document we're writing in the otsreport
documentclass that happens to use the acronym
environment doesn't have to explicitly have \usepackage{ots}
in its header?
I think maybe the following is the state we want to get to:
- We have .cls files that just define what is necessary to distinctively define their respective classes;
- Each .cls file does
\usepackage{ots}
(this loadsots.sty
). - All the non-class-specific stuff we use, whether OTS-defined (e.g.,
\fullref
) or not (e.g., theacronym
env), goes intoots.sty
.
This implies moving any non-class-specific stuff that currently happens to be defined in .cls files into ots.sty
.
See What are .cls and .sty files? How are they different? and Classes and packages – what's the difference? for background on classes versus packages (style files).