Hi Jeffrey, the attached sample file works for me.
The html is only sub-optimal, though, as it just includes a link to a pdf file. Cheers, Andreas Am 21.02.2011 02:56, schrieb Erik Iverson: > Jeffrey, > >> Now, I'd like to integrate them into an org document. I'd like: >> 1) To use babel to handle the TikZ source > > This is possible. > >> 2) To wrap the resulting drawing in a figure environment for >> automatic numbering and centering > > See > http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html > and search for "tikz" for an example. I think you do need to use the > :file argument > for this to have org-mode take care of it automatically. > > Alternatively, you could just include *all* the latex you want, including > constructing your own figure environment and caption and refs, in the > latex > code block. > >> 3) To be able to refer to the figure elsewhere in the document > > Should be possible with either approach above. > >> 4) (optional) To be able to seamlessly export to both LaTeX and HTML > > So should the HTML exporter generate a PNG file then, as opposed to PDF? > This is possible, but requires some 'conditional' elisp code in your > :file > source block argument. I think I can help if that's indeed what you > want. > >> And somewhat unrelated, is ":results" now deprecated in favor of >> ":exports"? What about ":file"? I'm sufficiently new to babel that >> these all seem like they could be taken care of with a single header >> argument with many options... > > Not deprecated at all according to my understanding: > > :results determines how the results are collected from a process. So, > in R, we > might want the standard output ':results output' or we might just want > the last > value returned by the code block, ':results value'. This determines > what is > inserted into the org-mode buffer or the export stream when the code > block > is evaluated. > > :exports determines if the code and/or the results will be inserted upon > exporting. *If* the results are inserted, then :results will determine > how. > > :file is useful for code blocks that generate graphical output, such > as tikz. > This will divert the output into the named file, and exporting will > insert > that file. In the org-mode buffer, a link will be inserted. If a png > file is > generated, it can even be displayed inline in the org-mode buffer if > you turn > on that functionality. > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
#+LATEX_HEADER: \usepackage{tikz}
* Tikz Sample
In figure \ref{fig:tikz_sample} you can see something.
#+srcname: tikz_sample
#+begin_src latex :exports (if (eq backend 'latex) "none" "results") :file
tikz_sample.pdf :headers '("\\usepackage{tikz}")
\usetikzlibrary{arrows}
\tikzstyle{int}=[draw, fill=blue!20, minimum size=2em]
\tikzstyle{init} = [pin edge={to-,thin,black}]
\begin{tikzpicture}[node distance=2.5cm,auto,>=latex']
\node [int, pin={[init]above:$v_0$}] (a) {$\frac{1}{s}$};
\node (b) [left of=a,node distance=2cm, coordinate] {a};
\node [int, pin={[init]above:$p_0$}] (c) [right of=a] {$\frac{1}{s}$};
\node [coordinate] (end) [right of=c, node distance=2cm]{};
\path[->] (b) edge node {$a$} (a);
\path[->] (a) edge node {$v$} (c);
\draw[->] (c) edge node {$p$} (end) ;
\end{tikzpicture}
#+end_src
#+begin_src latex :noweb yes
\begin{figure}
\centering
<<tikz_sample>>
\caption[Tikz]{Tikz}\label{fig:tikz_sample}
\end{figure}
#+end_src
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
