Typesetting - Processing Tools Import and Export (

[GoogleCodeExporter]

(No proposed alteration to Tw applicatoin's current normal proedures on start 
load and save of Typesetting settings. Just a proposed injection of a new 
intermediatory feature))

When using Edit/Preferences/Typesetting Tab

For both the dialogues brought up by either Edit or the light blue plus button 
for new Processing tool, in those dialogues (probably the same one recycled) 
add two sets of buttons: 

1. Import and Export.
2. Paste (into) and Copy (out)

Functionality: Export/Import

Creates/Loads a named .txt file on/from disk,
transferable to other users,  and so loadable as an import when the edit or New 
dialogue is in view, populates/or exports the text boxes and list of arguments.

Possible Text file format:

Name: XeLaTeX+MakeIndex+BibTeX
Program: texify.exe
--pdf
--engine=xetex
--tex-option=-synctex=1
$fullname

First two lines, prefixed as above, then third line and above are all arguments.

Then individual "recipes" :) could be shared around.  Would help,
especially with more exotic and specialised needs, while keeping the standard 
issue Typesetting drop down box relatively uncluttered.

Functionality: Paste/Copy

Receives/Puts the same information/format as above from and to the clipboard, 
so that if a "recipe" was in a Tw wiki or issue tracker page it could be 
directly transferred (copied/Pasted in), or Copied/pasted out to a new Tw issue 
entry or email. 

If the processing tools array or collection or whatever could be marked as 
scriptable, and script could receive/write that and to each elements members  
(the Name and Program and array of typesetting arguments) it could be done 
through scripting. 

(Though perhaps if this were to be done, would it be easier/or same work to 
just do the whole thing out right  in C++ perhaps any way?) 

Paul

Original issue reported on code.google.com by paul.a.norman on 16 Jul 2011 at 1:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Or just use the tools.ini format (which allows for showPdf which I left out)

name=pdfLaTeX
program=pdflatex.exe
arguments="--extra-mem-top=2000000  ", --enable-write18, $synctexoption, 
$fullname
showPdf=true

Or scripting could just process the tools.ini file directly? Would that be ok?
Though if done there in scripting, wouldn't show until Tw was restarted?

Original comment by paul.a.norman on 16 Jul 2011 at 1:52