On Fri, Apr 15, 2011 at 8:36 AM, Auré Gourrier
<aur...@ya...>wrote:
> Good Idea !
> I'm also using mpl for other publications than ieee and it sounds like a
> small mplrc data base with targeted journal specifications would be
> worthwhile doing ! I would be ready to contribute.
> Cheers,
> Auré
>
>
Is there any reason this needs to done with rc files? I prefer to put
document-specific configuration into modules. For example, you could have a
module that looks like:
mplrc/
__init__.py
aps_fullpage.py
aps_twocolumn.py
ieee.py
...
(`aps` could even be directory). And each module would set rc parameters
using function calls; for example, aps_twocolumn.py might look like:
import matplotlib.pyplot as plt
plt.rc('axes', labelsize=10)
plt.rc('text', fontsize=10)
plt.rc('legend', fontsize=10)
plt.rc('xtick', labelsize=8)
plt.rc('ytick', labelsize=8)
plt.rc('text', usetex=False)
plt.rc('figure', figsize=(3.4039, 2.1037))
(Alternatively, you could create a separate rc file and just have the module
load that rc file). The advantage of this module-based approach is that you
could simply import the module whenever you need it (e.g., just add `import
mplrc.aps_twocolumn` at the top of your script). If I used an rc file
instead, I'd have to copy the rc file to my working directory each time, or
somehow, manually load the rc file from a path.
Just a suggestion.
-Tony