One-Window Design of a Texpad Project Workspace
This article concerns the
iOS
app.
See other variants:
macOS
Windows

Texpad follows a one-window design for its workspaces. A workspace is an instance of a Texpad window created when you open a root .tex file. For documents written in LaTeX, Texpad defines a root .tex file to be one that contains a block of the kind

\documentclass{article}
\begin{document}
...
\end{document}

A root file would be expected to generate a single PDF file upon a successful typeset. A Texpad window rooted on such a root file contains all you need to work on a document that may contain multiple files but produce a single output PDF file.

  • An text editor with source code which may be in LaTeX, TeX (carrying a .tex extension for their files) or markdown (a .md file) formats: apps/workspace/editor
  • A PDF viewer presenting the output of typesetting all the source .tex and image files: apps/workspace/pdf-viewer
  • A sidebar with the key data parsed from the source files:
  • A toolbar containing various useful controls for the project window
  • A typeset bar placed on the toolbar with:
    • A typeset button: the cogs that animate during a typeset operation.
    • A summary of what tools are being used to typeset the project.
    • A settings’ button that will bring up a typeset configuration window to fine-tune how the project is compiled into a PDF.
    • The typeset status: either a green tick when the typeset is successful, or an error/warnings count.

A single workspace window is therefore designed to hold all files that lead to a single publishable output PDF. A Texpad window on macOS may contain multiple tabs, but in order to maintain clarity Texpad allows a single root file per workspace window, and the tabs may only be used the open files from the project governed by that root file. Different files of the same project may be opened in different tabs at different locations, but all must be under the a single project with a single root file and a single output PDF.

The one-window design also avoids confusion when typesetting a root file. A spinning set of cogs on the toolbar indicate the typesetting process of the entire project in the window beneath. The error count in the typeset bar represents the errors in the entire project regardless of what subfile they emanate from or what subfile is currently being viewed and edited in the editor.

The one-window design reflects how TeX and LaTeX work: a single blob of input is processed to produce a single output file. Multiple file that constitute a project are treated as a single blob of input when being typeset.

For a Markdown document, all files are root files. A single window design has a clearer notion in markdown.

Following sections go into further detail of each part of the project workspace.

docs/apps/workspace/jd-thesis-sawtooth_ios.png