On Tue, Jan 31, 2012 at 1:46 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> Il 28/01/2012 20:08, Liviu Andronic ha scritto:
>
>> The reason I ask is that I'm currently working on providing LyX
>> support for 'makebeamerinfo' [2], a programme that improves the
>> experience of displaying Beamer presentations in Impressive. The
>> script has several switches, but as far as I know a converter cannot
>> easily be modified from one run to another. So one solution would be
>> to modify the environment in which the script is run. Does LyX support
>> this?
>
>
> If these environment variable assignments are static, then why don't
> you set them before launching LyX itself ?
>
> If, on the other hand, they're dynamic, then explain what exactly
> you would need, please.
>
When you define a converter in LyX it's all pretty static. In my case,
# FORMATS SECTION ##########################
\format "beamer.info" "pdf.info" "Info (Beamer)" "" "leafpad"
"leafpad" "document,menu=export"
# CONVERTERS SECTION ##########################
\converter "pdf2" "beamer.info" "makebeamerinfo -p $$i" ""

However, 'makebeamerinfo' [1] supports several presets via cli
switches and via an ENV var [2]. For example, teh user can
 -t clean           makebeamerinfo's default, pageturn and wiperight
     default         that is, Impressive's default selection
     sane            selections which make sense for a Beamer presentation

or use the (exported) environment variable $MAKEBEAMERINFO_TRANSITIONS
to control this, prior to running the script.

The catch is that the user may reasonably expect/want to be able to
change this setting from one run to the other. I'm not very familiar
with this part of LyX, but I can see only two readily available ways
to achieve that:
- define three different converters, each using a different '-t'
setting. This is overkill, and would never be accepted in base LyX in
such a state.
- modify the converter prior to each run. Another overkill.

So we're at a loss as to how to elegantly allow users to modify this
setting between two subsequent runs. We hoped that an ENV var could
solve the issue. Ideas?

Regards
Liviu

[1] https://github.com/jberger/MakeBeamerInfo
[2] http://search.cpan.org/~jberger/App-makebeamerinfo-2.001/bin/makebeamerinfo

Reply via email to