Re: Lyx and beamer again.
Liviu Andronic wrote: > I guess that most Beamer hacks could be dropped once #6753 [1] gets > addressed. Liviu > > [1] http://www.lyx.org/trac/ticket/6753 Indeed, a sane argument UI is a major prerequisite (next to features such as "NextNested" which automatically nests following paragraphs). However, the argument interface needs to be flexible. The beamer case shows that there's not one "perfect" UI for all argument-type entries. While many optional and required arguments are best handled via a dialog (as proposed by me in that report) -- for instance the optional and overlay arguments of frame --, arguments such as the frame title should best be inserted directly to the workarea (as the current UI does). For other use cases, even the current clumsy collapsable inset might be the best approach. So we need a broad macro and environment argument abstraction and several user interfaces on top of that. Jürgen
Re: Lyx and beamer again.
On Sat, Nov 5, 2011 at 2:07 PM, Jürgen Spitzmüller wrote: > The problem at the moment is that LyX does not yet support beamer's overlay > arguments (<...>). At the time when the beamer layout was written (by the > beamer author himself, BTW), we also did not yet support mandatory environment > arguments. We do now, although the InsetArgument framework is not really > suitable for submitting a frame title. > I guess that most Beamer hacks could be dropped once #6753 [1] gets addressed. Liviu [1] http://www.lyx.org/trac/ticket/6753 > \lyxframe works around these shortcomings by scanning for the diverse > arguments. > > Jürgen > -- Do you know how to read? http://www.alienetworks.com/srtest.cfm http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
Re: Lyx and beamer again.
Bert Lloyd wrote: > Are these issues somewhat reduced by the incremental lists modules? > http://wiki.lyx.org/Layouts/Modules#toc9 > Perhaps these could be included in "stock" LyX in the future and make > the \lyxframe workaround unnecessary? Not really. These modules just hardcode some common overlay use cases (which are also achieveable without the modules). Jürgen
Re: Lyx and beamer again.
On Sat, Nov 5, 2011 at 9:07 AM, Jürgen Spitzmüller wrote: > The problem at the moment is that LyX does not yet support beamer's overlay > arguments (<...>). At the time when the beamer layout was written (by the > beamer author himself, BTW), we also did not yet support mandatory environment > arguments. We do now, although the InsetArgument framework is not really > suitable for submitting a frame title. > > \lyxframe works around these shortcomings by scanning for the diverse > arguments. > > Jürgen > Thanks for the explanation. Are these issues somewhat reduced by the incremental lists modules? http://wiki.lyx.org/Layouts/Modules#toc9 Perhaps these could be included in "stock" LyX in the future and make the \lyxframe workaround unnecessary?
Re: Lyx and beamer again.
Bert Lloyd wrote:
> I have never understood the purpose of \lyxframe and \lyxframeend when
> the standard \begin{frame} and \end{frame} are available.
>
> Conceding my almost complete ignorance on this topic, wouldn't it be
> better to for LyX to use standard Beamer / LaTeX commands whenever
> possible? This would seem to improve interoperability with users of
> "pure" latex, as well as to adhere to the general principle of keeping
> things simple and not introducing complications that are not needed.
The problem at the moment is that LyX does not yet support beamer's overlay
arguments (<...>). At the time when the beamer layout was written (by the
beamer author himself, BTW), we also did not yet support mandatory environment
arguments. We do now, although the InsetArgument framework is not really
suitable for submitting a frame title.
\lyxframe works around these shortcomings by scanning for the diverse
arguments.
Jürgen
Re: Lyx and beamer again.
I have never understood the purpose of \lyxframe and \lyxframeend when
the standard \begin{frame} and \end{frame} are available.
Conceding my almost complete ignorance on this topic, wouldn't it be
better to for LyX to use standard Beamer / LaTeX commands whenever
possible? This would seem to improve interoperability with users of
"pure" latex, as well as to adhere to the general principle of keeping
things simple and not introducing complications that are not needed.
Re: Lyx and beamer again.
I was ignorant of this mechanism (inserting hte definition only if the last
\lyxframeend{} is manually inserted. Since the part of my document that has
not been reconverted to the beamer format was just flowing text,I can
compile my document once exported to Latex. But since I have only inserted
Start Frame insets froms the menu box, it is strange inf fact that the
latex file was able to compile, without the last manual \lyxframeend{},
no?
Have I been lucky at least on this point? :-) (I have always read on this
list the you need this last fram end, other wise you are doomed ;-) - that
is what Rich was suggesting, by the way)
Anyway, I have added it now, by precaution. I won't forget this trick.
Thanks a lot Jürgen and Rich.
Murat
2011/11/4 Jürgen Spitzmüller
> Rich Shepard wrote:
> > I concur. I've found that each frame needs a \endframe and that also
> needs
> > to be the last line in the presentation.
>
> This is probably a misunderstanding. I meant that LyX is supposed to
> \lyxframeend definition to the auto-generated preamble whenever this macro
> is
> used (which is the case in many paragraph styles such as section etc.).
>
> Having said that, you should not need to insert a FrameEnd
> normally.It'sonly
> needed in very specific cases.
>
> Jürgen
>
--
Prof. Murat Yildizoglu
Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France
yi...@u-bordeaux4.fr
http://yildizoglu.info
http://www.twitter.com/yildizoglu
Re: Lyx and beamer again.
Rich Shepard wrote: > I concur. I've found that each frame needs a \endframe and that also needs > to be the last line in the presentation. This is probably a misunderstanding. I meant that LyX is supposed to \lyxframeend definition to the auto-generated preamble whenever this macro is used (which is the case in many paragraph styles such as section etc.). Having said that, you should not need to insert a FrameEnd normally.It'sonly needed in very specific cases. Jürgen
Re: Lyx and beamer again.
On Fri, 4 Nov 2011, Jürgen Spitzmüller wrote: It is defined once you insert an "EndFrame" in the document. In my experience, it is generally advisable to insert such and EndFrame at the end of a presentation. But of course the \lyxframeend definition should be inserted in all cases where this macro is used. This is a bug. Jürgen, I concur. I've found that each frame needs a \endframe and that also needs to be the last line in the presentation. Rich
Re: Lyx and beamer again.
Murat Yildizoglu wrote: > - I have spent some time before observing that, when I have set the > document class to Presentation(beamer) in Lyx; it has introduced the > definition of \lyxframe, but not the one of the \lyxframeend. Once I have > introduced it in the preamble, I have been able to compile the document > when I export to latex. It is defined once you insert an "EndFrame" in the document. In my experience, it is generally advisable to insert such and EndFrame at the end of a presentation. But of course the \lyxframeend definition should be inserted in all cases where this macro is used. This is a bug. HTH, Jürgen
Lyx and beamer again.
Hi, Contrary to what I have announced in my preceding post, I continue to try to import my latex beamers, following the schema to which I have arrived after the remarks of Guenter : convert first the document to article; neutralize the frame commands; import in Lyx; set the document class to beamer; reintroduce frame commands by hand. This works better than trying to import the beamer document directly. But, I have other problems to solve: - I have spent some time before observing that, when I have set the document class to Presentation(beamer) in Lyx; it has introduced the definition of \lyxframe, but not the one of the \lyxframeend. Once I have introduced it in the preamble, I have been able to compile the document when I export to latex. - Compiling from Lyx poses problem, since I have an animated diagram with multi-include, introduced in an ERT. When I want to preview the pdf, Lyx cannot find the pdf files in the temp folder and complains about it. I have given the path to the pdf files in the Texinputs box , by completing it like: .:/Users/me/myyfolderpath but this does not seem to help enough Lyx and it continues to not to find the pdf graphics and complain that they do have a bounding box (I can perfectly compile running pdflatex on the exported version, in the original folder (myfolderpath). Any idea why pdflatex run by Lyx cannot find my graphics? We had questions about this problem, but I have thought that this texinputs box in the prefs was there for exactly this problem. By the way : it would be better to be able to set the Texinputs variable in the document properties, since it is in general document dependent, if one groups all files together for each document. Regards, Murat -- Prof. Murat Yildizoglu Université Montesquieu Bordeaux IV GREThA (UMR CNRS 5113) Avenue Léon Duguit 33608 Pessac cedex France yi...@u-bordeaux4.fr http://yildizoglu.info http://www.twitter.com/yildizoglu
