[Paraview-developers] ParaView User's Guide

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Thu Jan 15 17:52:16 EST 2015


That's a good idea (I agree, it's too opaque indeed). No, the LaTeX
files themselves are not an issue, size-wise, much smaller than the
code itself, in any case.

I think I like this idea. Unless there are any other opinions, maybe
we'll stick with this one.

Utkarsh


On Thu, Jan 15, 2015 at 2:46 PM, David Thompson
<david.thompson at kitware.com> wrote:
>> The ParaView User's Guide is very close to being ready for the public.
>> ... the next question is where do these [LaTeX files] live? ... the
>> source files (and high resolution images) are close to 500 MB, hence
>> not ideal for inclusion in the ParaView source. ...
>> Any other suggestions? What are people's thoughts?
>
> I think the ExternalData implementation is too opaque, but the strategy (store images and binary files outside of version control) would be useful. Are even the LaTeX files too large for the ParaView repo, or could they be stored with the source and rely on images being downloaded?
>
>         2¢,
>         David


More information about the Paraview-developers mailing list