Re: Lyx and beamer again.

[Bert Lloyd]

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.

[Jürgen Spitzmüller]

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.

[Bert Lloyd]

On Sat, Nov 5, 2011 at 9:07 AM, Jürgen Spitzmüller sp...@lyx.org 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.

[Jürgen Spitzmüller]

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.

[Liviu Andronic]

On Sat, Nov 5, 2011 at 2:07 PM, Jürgen Spitzmüller sp...@lyx.org 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.

[Jürgen Spitzmüller]

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

Package varioref Sweave error

[Graham Smith]

I have unsuccessfully been trying to get some latex code to (make a table)
run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
However, now the document won't compile with the error message below.
 Nothing has changed other than the stuff I added and then deleted, but I
assume the aborted attempts to compile have broken something. I am on a Mac
with Lyx 2.0.0

Error
Package varioref \vref at page boundary 18-19 (may loop)


Description

terms. }

 Please check the pages in question. You might need to replace the \vref

or \vpageref by a normal \(page)ref to stop LaTeX running forever.


Is there an obvious solution to this,




many thanks,


Graham

Re: Package varioref Sweave error

[Xu Wang]

Hi Graham,

Could you send a minimum working example (WME) of your .lyx file? My guess
is that you might be able to generate the same error by deleting most or
all of your document.

My only suggestion for now is to start a new LyX document, and then copy
from your old to your new. This will copy all of the content but will not
copy some of the underlying things in the .lyx file. This would be easy to
try and could solve your problem.

Best,

Xu

On Sat, Nov 5, 2011 at 2:25 PM, Graham Smith myotis...@gmail.com wrote:

 I have unsuccessfully been trying to get some latex code to (make a table)
 run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
 However, now the document won't compile with the error message below.
  Nothing has changed other than the stuff I added and then deleted, but I
 assume the aborted attempts to compile have broken something. I am on a Mac
 with Lyx 2.0.0

 Error
 Package varioref \vref at page boundary 18-19 (may loop)


 Description

 terms. }

  Please check the pages in question. You might need to replace the \vref

 or \vpageref by a normal \(page)ref to stop LaTeX running forever.


 Is there an obvious solution to this,




 many thanks,


 Graham

Re: Package varioref Sweave error

[Graham Smith]

Hello Xu

Could you send a minimum working example (WME) of your .lyx file? My guess
 is that you might be able to generate the same error by deleting most or
 all of your document.

 My only suggestion for now is to start a new LyX document, and then copy
 from your old to your new. This will copy all of the content but will not
 copy some of the underlying things in the .lyx file. This would be easy to
 try and could solve your problem.


I have copied all the text into a new document and it all seems to be
working again. Which is great relief as I am very short of time trying to
get this document finished for Tuesday.

Thanks,

Graham

Re: Package varioref Sweave error

[Xu Wang]

Graham, I'm glad that worked for you!

I don't mean to be parental, but this should be a good reminder to you that
it's always good to save frequently and to save many different versions.
Ideally you should look into a version control system (which LyX actually
supports!), but at the least, make multiple backups, and not just one one
machine.

I hope you get everything done by Tuesday!

Xu

On Sat, Nov 5, 2011 at 6:06 PM, Graham Smith myotis...@gmail.com wrote:

 Hello Xu

 Could you send a minimum working example (WME) of your .lyx file? My guess
 is that you might be able to generate the same error by deleting most or
 all of your document.

 My only suggestion for now is to start a new LyX document, and then copy
 from your old to your new. This will copy all of the content but will not
 copy some of the underlying things in the .lyx file. This would be easy to
 try and could solve your problem.


 I have copied all the text into a new document and it all seems to be
 working again. Which is great relief as I am very short of time trying to
 get this document finished for Tuesday.

 Thanks,

 Graham

Re: Lyx and beamer again.

[Bert Lloyd]

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.

[Jürgen Spitzmüller]

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.

[Bert Lloyd]

On Sat, Nov 5, 2011 at 9:07 AM, Jürgen Spitzmüller sp...@lyx.org 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.

[Jürgen Spitzmüller]

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.

[Liviu Andronic]

On Sat, Nov 5, 2011 at 2:07 PM, Jürgen Spitzmüller sp...@lyx.org 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.

[Jürgen Spitzmüller]

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

Package varioref Sweave error

[Graham Smith]

I have unsuccessfully been trying to get some latex code to (make a table)
run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
However, now the document won't compile with the error message below.
 Nothing has changed other than the stuff I added and then deleted, but I
assume the aborted attempts to compile have broken something. I am on a Mac
with Lyx 2.0.0

Error
Package varioref \vref at page boundary 18-19 (may loop)


Description

terms. }

 Please check the pages in question. You might need to replace the \vref

or \vpageref by a normal \(page)ref to stop LaTeX running forever.


Is there an obvious solution to this,




many thanks,


Graham

Re: Package varioref Sweave error

[Xu Wang]

Hi Graham,

Could you send a minimum working example (WME) of your .lyx file? My guess
is that you might be able to generate the same error by deleting most or
all of your document.

My only suggestion for now is to start a new LyX document, and then copy
from your old to your new. This will copy all of the content but will not
copy some of the underlying things in the .lyx file. This would be easy to
try and could solve your problem.

Best,

Xu

On Sat, Nov 5, 2011 at 2:25 PM, Graham Smith myotis...@gmail.com wrote:

 I have unsuccessfully been trying to get some latex code to (make a table)
 run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
 However, now the document won't compile with the error message below.
  Nothing has changed other than the stuff I added and then deleted, but I
 assume the aborted attempts to compile have broken something. I am on a Mac
 with Lyx 2.0.0

 Error
 Package varioref \vref at page boundary 18-19 (may loop)


 Description

 terms. }

  Please check the pages in question. You might need to replace the \vref

 or \vpageref by a normal \(page)ref to stop LaTeX running forever.


 Is there an obvious solution to this,




 many thanks,


 Graham

Re: Package varioref Sweave error

[Graham Smith]

Hello Xu

Could you send a minimum working example (WME) of your .lyx file? My guess
 is that you might be able to generate the same error by deleting most or
 all of your document.

 My only suggestion for now is to start a new LyX document, and then copy
 from your old to your new. This will copy all of the content but will not
 copy some of the underlying things in the .lyx file. This would be easy to
 try and could solve your problem.


I have copied all the text into a new document and it all seems to be
working again. Which is great relief as I am very short of time trying to
get this document finished for Tuesday.

Thanks,

Graham

Re: Package varioref Sweave error

[Xu Wang]

Graham, I'm glad that worked for you!

I don't mean to be parental, but this should be a good reminder to you that
it's always good to save frequently and to save many different versions.
Ideally you should look into a version control system (which LyX actually
supports!), but at the least, make multiple backups, and not just one one
machine.

I hope you get everything done by Tuesday!

Xu

On Sat, Nov 5, 2011 at 6:06 PM, Graham Smith myotis...@gmail.com wrote:

 Hello Xu

 Could you send a minimum working example (WME) of your .lyx file? My guess
 is that you might be able to generate the same error by deleting most or
 all of your document.

 My only suggestion for now is to start a new LyX document, and then copy
 from your old to your new. This will copy all of the content but will not
 copy some of the underlying things in the .lyx file. This would be easy to
 try and could solve your problem.


 I have copied all the text into a new document and it all seems to be
 working again. Which is great relief as I am very short of time trying to
 get this document finished for Tuesday.

 Thanks,

 Graham

Re: Lyx and beamer again.

[Bert Lloyd]

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.

[Jürgen Spitzmüller]

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.

[Bert Lloyd]

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.

[Jürgen Spitzmüller]

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.

[Liviu Andronic]

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.

[Jürgen Spitzmüller]

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

Package varioref Sweave error

[Graham Smith]

I have unsuccessfully been trying to get some latex code to (make a table)
run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
However, now the document won't compile with the error message below.
 Nothing has changed other than the stuff I added and then deleted, but I
assume the aborted attempts to compile have broken something. I am on a Mac
with Lyx 2.0.0

Error
Package varioref \vref at page boundary 18-19 (may loop)


Description

terms. }

 Please check the pages in question. You might need to replace the \vref

or \vpageref by a normal \(page)ref to stop LaTeX running forever.


Is there an obvious solution to this,




many thanks,


Graham

Re: Package varioref Sweave error

[Xu Wang]

Hi Graham,

Could you send a minimum working example (WME) of your .lyx file? My guess
is that you might be able to generate the same error by deleting most or
all of your document.

My only suggestion for now is to start a new LyX document, and then copy
from your old to your new. This will copy all of the content but will not
copy some of the underlying things in the .lyx file. This would be easy to
try and could solve your problem.

Best,

Xu

On Sat, Nov 5, 2011 at 2:25 PM, Graham Smith  wrote:

> I have unsuccessfully been trying to get some latex code to (make a table)
> run in an ERT box in Lyx. In the end I gave up and deleted my attempts.
> However, now the document won't compile with the error message below.
>  Nothing has changed other than the stuff I added and then deleted, but I
> assume the aborted attempts to compile have broken something. I am on a Mac
> with Lyx 2.0.0
>
> Error
> Package varioref \vref at page boundary 18-19 (may loop)
>
>
> Description
>
> terms. }
>
>  Please check the pages in question. You might need to replace the \vref
>
> or \vpageref by a normal \(page)ref to stop LaTeX running forever.
>
>
> Is there an obvious solution to this,
>
>
>
>
> many thanks,
>
>
> Graham
>
>

Re: Package varioref Sweave error

[Graham Smith]

Hello Xu

Could you send a minimum working example (WME) of your .lyx file? My guess
> is that you might be able to generate the same error by deleting most or
> all of your document.
>
> My only suggestion for now is to start a new LyX document, and then copy
> from your old to your new. This will copy all of the content but will not
> copy some of the underlying things in the .lyx file. This would be easy to
> try and could solve your problem.
>

I have copied all the text into a new document and it all seems to be
working again. Which is great relief as I am very short of time trying to
get this document finished for Tuesday.

Thanks,

Graham

Re: Package varioref Sweave error

[Xu Wang]

Graham, I'm glad that worked for you!

I don't mean to be parental, but this should be a good reminder to you that
it's always good to save frequently and to save many different versions.
Ideally you should look into a version control system (which LyX actually
supports!), but at the least, make multiple backups, and not just one one
machine.

I hope you get everything done by Tuesday!

Xu

On Sat, Nov 5, 2011 at 6:06 PM, Graham Smith  wrote:

> Hello Xu
>
> Could you send a minimum working example (WME) of your .lyx file? My guess
>> is that you might be able to generate the same error by deleting most or
>> all of your document.
>>
>> My only suggestion for now is to start a new LyX document, and then copy
>> from your old to your new. This will copy all of the content but will not
>> copy some of the underlying things in the .lyx file. This would be easy to
>> try and could solve your problem.
>>
>
> I have copied all the text into a new document and it all seems to be
> working again. Which is great relief as I am very short of time trying to
> get this document finished for Tuesday.
>
> Thanks,
>
> Graham
>