# [OS X TeX] iOS apps

"M. Tamer Özsu" ozsut at mac.com
Tue Sep 4 17:17:50 CEST 2012

I downloaded and played around with it a bit. Unfortunately, in the demo model, all typesetting functions are disabled, so what you can try out is restricted. To address your specific questions:

1) It does have auto-completion of latex commands and also matches \begin with \end
2) It does not seem to have any means of defining your macros as one can do in TeXShop
3) It does not have anything for specialized engines (none of the editors I have tried other than TexShop have that). It does have the options of "Normal" typesetting, "Bibtex"ing, "Makeindex", and "Bibtex+Makeindex". Since I cannot typeset anything, it is hard to know what "Normal" typesetting means.

However, I like the clean three pane scheme that it uses. Unfortunately, it has no support for tabs it seems and new files are opened as new windows. In this regard, I think Latexian does a better job.

I just wish TeXShop supported three-pane view and tabs. It would be very helpful; right now I am fighting over many open windows when I work on a large document with many \includes.

==Tamer
--
M. Tamer Özsu
University of Waterloo
Cheriton School of Computer Science

On 2012-09-04, at 9:18 AM, Herbert Schulz <herbs at wideopenwest.com> wrote:

>
>> I don't really like the multi-document windowing model of TeXShop that much, it's sometimes too easy to lose windows in the background if you've got a lot of files open. Also if you do that and open a file with only a Latex fragment in it, then you have to get back to the original, top level file (in some background window that you may have to now locate) to press "Typeset" and see your changes. Because Texpad sees the set of files as all-one-document (if, of course, you opened it from the top level document), you can 'sync' to a subsidiary file, fix the issue and press "Typeset" and it re-typesets the whole thing. Additionally on the left you've got little navigator / file hierarchy thing that shows you the files included from the top level one, and you can click around that too.
>>
>
> Cmd-Click in the preview (pdf) and the correct source file opens for editing.
>
> Put the line
>
> % !TEX root = path/to/root.tex
>
> (path/to/root.tex is the absolute or relative path to the root file) at the top of the included/input file and then Typesetting will typeset the root file. Not only that, Cmd-Click in the include/input file will go to the correct location in the preview window.
>
>> The editor is not as powerful though. It was worth the twenty buck spend though to have a good look at it. I'm still considering what exactly I will do for an editor ... bear in mind my main writing tool is still MMD format in Scrivener.
>>
>> Scot.
>
> Does it have command completion? What about creating or using specialized engines for typesetting (latex [via dvi], pdflatex, xelatex, lualatex, how about the latexmk engines that take care of all the necessary indexing/bibliography/cross-referencing runs)?
>
> Good Luck,
>
> Herb Schulz
> (herbs at wideopenwest dot com)