Re: [Texstudio-list] Refactoring command/tool system

[Tim H. <hof...@hi...>]

Looks good. Maybe we  could go one step further and provide a generic
command system. Basically every command txs:///someCommand could be defined
and your rules are used to determine, what should be called. In that case
the commands you listed (latex, quick, bibliography...) are just predefined
examples and users can create their own, e.g. txs:///myFancyScript or
txs:///quick-eps or txs:///myPreferredIndexTool

Advantages:
- users can choose a telling name instead of txs:///user0
- multiple quick-build configurations possible (just recently requested
again)
- ideally users can completely setup any toolchain they want and we do not
have to touch the source code to add new tools (texindy/biber/xetex...)

Things to think about:
- can the logic of more complex commands like quick-build, conditional call
of bibliography, rerun latex be correctly defined? Maybe a script could be
used as a target of the command.
- How to integrate tools to the GUI: A list in the menu is fine. Assignable
shortcuts. What about toolbars? Predefined generic icons and/or allow the
user to supply an icon. Alternatively textual representation in combobox and
run button.


Slightly off-topic:
I'm thinking of replacing the somewhat cryptic special chars in the command
definitions:
% -> [filename]
@ -> [linenumber]
?e) -> [extension]
?a) -> [path]

Also possible: [current-filename], [current-path] (the ones above may refer
to the master file).

Examples:
latex -src -interaction=nonstopmode %.tex
latex -src -interaction=nonstopmode [filename].tex

mpost -interaction=nonstopmode ?me) ->
mpost -interaction=nonstopmode "[filename].[extension]"

"AcroRd32.exe" "?am.pdf"
"AcroRd32.exe" "[path]/[filename].pdf"

What's your opinion? Does this interfere with your refactoring?

Tim