[GT] Writing indicators cookbook

[R P Herrold <herrold AT owlriver.com>]

On Mon, 10 Mar 2008, Robert A. Schmied wrote:

> thomas has hit that nail on the head, convenience for the user. i'm toying
> with a web site alteration to link the pdf so it can 'read' via browser.

no worries; /me thinks: tex2html

> most, if not all, of the incantations to turn tex into something a bit
> more user friendly have been wrapped in a makefile of some form. it is
> possible that the gt server has all the necessary bits and pieces to
> daily update the pdf from the tex. thomas, could you supply the
> 'latex tool chain incantations' and other info needed to re-create the .pdf
> from the .tex so i can query the admin on the availability of support.

Sure -- We do PDF generation in the Makefile, and much more 
(dot graphs, a tex to html variant), in at ~/doc/Makefile and 
below in any 'trading-shim' tarball
	( ftp://ftp.trading-shim.org/pub/local/trading-shim/ )
yielding coordinated PDF and html doco when we release:
	http://www.trading-shim.org/pdfs/manual.pdf
	http://www.trading-shim.org/doc/

It can be as simple as something like this target:

docs:                   ;
                        touch     $(LATEX).ind
                        latex     $(LATEX)
                        makeindex $(LATEX)
                        latex     $(LATEX)
                        dvips  $(LATEX).dvi -o $(LATEX).ps
                        ps2pdf $(LATEX).ps     $(LATEX).pdf

Bill (my co-developer) does it more symbolicly:

VPATH   =  tex:bib:fig
LATEX   =  /usr/bin/latex
DVIPS   =  dvips
PS2PDF  =  ps2pdf
BIBTEX  = -bibtex
RM      =  rm
PARENT  = http://www.trading-shim.org/
HEADER  = Up
L2H_CA  = -local_icons -up_url $(PARENT) -up_title $(HEADER)

%.pdf:  %.tex $(SRC)    ;       $(LATEX)    $*.tex
                                $(LATEX)    $*.tex
                                $(BIBTEX)   $*.aux
                                $(DVIPS) -z $*.dvi -o
                                $(PS2PDF)   $*.ps

online: manual          ;       latex2html -debug $(L2H_CA) manual
                                $(RM) -rf manual/TMP

We can build the PDF and HTML doco and roll the tarball, which 
is then transferred by rsync to the the html ./doc/ point, and 
ftp tarball locale, however, rather than risk carrying on a 
build process on the webserver.

> freely available provided one has 100mb plus of space 
> available. yea, even in the days of 500gb disks some of us 
> are

*nod* ... but we are dealing with large (huge) datasets here; 
one hedge fund client has been spinning up a TBy of space 
weekly with the flood of data we are facing.  I cannot imagine 
what they see at that level of detail, but ...

> still using pre-historic 9gb drives ;-)

ouch .. there cannot be a 9g made in the last 5 years, and so 
out of warranty.  It would scare me  ;(

> > ...lending a courtesy build is a different analytic case, 
> > but in terms of economic rationalism, better and free beats 
> > less featured and priced.

> > drilling in up-to-date perldoc throughout also comes to mind
>
> if a module with new pod is committed the pod will be available via
> the web site within 24 hours.

> > Who do I speak to about getting CVS commits?
>
> actually, not that it truly matters, it's subversion now ;-)

well, yes, and I vaguely remembered that, but as I tend to 
wrap 'co' pulls up into scripts, ...

> query the admin, and gt owner Raphaël Hertzog < raphael at ouaza dot com >

got it.

-- Russ herrold