END-OF-FRAME, once again..

[Scott Kostyshak]

On Thu, Nov 18, 2021 at 12:04:56AM -0500, Scott Kostyshak wrote:
> On Tue, Oct 19, 2021 at 10:29:05AM -0400, Scott Kostyshak wrote:
> > On Thu, Oct 14, 2021 at 03:14:48PM +0200, Daniel wrote:
> > > On 13/10/2021 16:50, Scott Kostyshak wrote:
> > > > On Wed, Oct 13, 2021 at 12:13:30PM +0200, Daniel wrote:
> > > > > Something that I thought while using beamer with LyX was that it seems that
> > > > > it would be easier if Frames would not "hang together". I mean: right now,
> > > > > if you press enter at the end or beginning of a frame, you get a new line
> > > > > that is extending the same frame. Wouldn't it be easier if you get a new
> > > > > frame this way and instead would just nest stuff in order to get it onto a
> > > > > specific frame? So, no need for separators either. There may be issues with
> > > > > this suggestion that I have not thought careful enough about but on the face
> > > > > of it, it seems like a good idea to me and to solve the issues you
> > > > > mentioned. What do you think?
> > > > 
> > > > I think the workflow you're suggesting makes the not-always-true assumption that the user does not use the "frame" layout for the *content* of the frame, and only uses nested layouts (e.g., itemize or standard). Did I understand right?
> > > 
> > > Yes. It is not a conservative approach. It suggest to not use the frame
> > > layout for the content because, if I see it correctly, this can be equally
> > > achieved by using a nested standard layout. So, why not have just one way of
> > > doing things. And it seems to me more consistent in that, say, itemized
> > > lists have to be nested as well within a frame which makes them appear at
> > > another level than the content of the frame when not nested but they are
> > > not. Isn't that a bit strange or misleading?
> > > 
> > > Instead, everything will have to be nested if it should go on a frame. (Of
> > > course there must be a lyx2lyx mechanism to transfer old beamer documents to
> > > the new "nesting-style".)
> > > 
> > > The workflow would in the new style would be like this:
> > > 
> > > 1. Select the Frame layout to create a new frame.
> > > 2. Press enter which creates a nested Standard paragraph to add content.
> > > 3. Press enter twice to un-nest and get a Frame layout which starts a new
> > > frame.
> > > 
> > > Doesn't this appear more simple and intuitive?
> > 
> > It does. I think it is a reasonable proposal. I'm just not sure
> > everyone will agree. For example, our own beamer example uses the
> > frame layout for content.
> 
> One use case that would benefit from your suggested interface:
> 
> It's currently annoying to change a "Frame" to a "Fragile Frame" or
> "Plain Frame". Consider the following pseudo code:
> 
>   [frame content...]
>   [more frame content...]
>   [nested itemize]
>   [frame content...]
> 
> You can't just select all paragraphs and change to the new
> (Fragile/Plain) Frame. With your workflow, I think it would be
> sufficient to change the first paragraph.

I've been thinking more about your proposal. As I work more with Beamer,
I think your proposal makes a lot of sense and would simplify things.
The first thing we would need to ask is if there's any functionality
that can be achieved with allowing the "frame" environment, as opposed
to requiring a nested standard enviornment.

Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-users/attachments/20220316/e2b4d576/attachment.asc>