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
