Am 13.01.2013 09:58, schrieb Jürgen Spitzmüller:
I'm
reluctant to touch this again at the moment (even more so since the period
where I had extra spare time for Lyx has ended).
OK.
You already did a lot for LyX the last weeks.
regards Uwe
Uwe Stöhr wrote:
> One further annotation: some arguments contain TeX code, like sizes,
> commands etc. it would therefore be helpful if one could use Passthru for
> certain arguments so that the user can there e.g. directly insert things
> like "\subWandt{0.4\linewidth}"
PassThru is tricky, due
Am 28.12.2012 11:21, schrieb Jürgen Spitzmüller:
I have implemented now the possibility to place (inset-inserted) arguments
after the main (workarea-inserted) argument for commands.
Such arguments have the prefix "post:", i.e.
Argument post:1
Hello Jürgen,
as I promised I had a look and test
Am 01.01.2013 10:16, schrieb Jürgen Spitzmüller:
2. We have the "LaTeXType" named "Bib_Environment". But this type is nothing
more than adding \begin{bibliography}{99}
Thanks to your work we can get rid of the hardcoded "99" because we could
redefine it using a required argument for the biblio
Uwe Stöhr wrote:
> 2. We have the "LaTeXType" named "Bib_Environment". But this type is nothing
> more than adding \begin{bibliography}{99}
> Thanks to your work we can get rid of the hardcoded "99" because we could
> redefine it using a required argument for the bibliography environment
> instea
Am 28.12.2012 19:09, schrieb Uwe Stöhr:
Thank you. I'll test it next year.
As I promised I will do so. But while revising chapter 5 of the Customization manual I noticed the
following 3 issues that could be improved:
1. Currently the "LabelType" Itemize and Enumerate are hardcoded, meaning
Am 28.12.2012 11:21, schrieb Jürgen Spitzmüller:
I have implemented now the possibility to place (inset-inserted) arguments
after the main (workarea-inserted) argument for commands.
Such arguments have the prefix "post:", i.e.
Argument post:1
Thank you. I'll test it next year.
best regards
U
Uwe Stöhr wrote:
> But how can i force that argument 3 is output after the text the users
> enters in LyX?
>
> I could alternatively setup 4 arguments but then the user has to input
> everything via InsetArguments. This is OK in my opinion, but what do you
> think?
I have implemented now the pos
Am 01.12.2012 12:13, schrieb Jürgen Spitzmüller:
I btw. have the feeling
that ParbreakIsNewline does nothing. I cannot see a change.
What am I dong wrong?
Apparently, you also need to set PassThru. The following seems to work (but
PassThru might not be what you want):
Correct. What I need is
Uwe Stöhr wrote:
> But I already did this and it doesn't work for me. Take for example the
> ACM-siggraph.lyx file in trunk. The problem is that I still get an empty
> line between the 2 \categories. I also tried to add
>
> ParbreakIsNewline 1
>
> for Style "CR categories" and also for the
Am 29.11.2012 06:28, schrieb Richard Heck:
For now, I'd think you could use the sort of trick we use to make beamer work:
Define your own command that switches the order of the arguments, and make LyX
use that.
That is not possible for journal submissions. Many publishers use a code checking
Am 29.11.2012 07:40, schrieb Jürgen Spitzmüller:
Besides this, how should I implement this?:
\category{B.2.4}{Arithmetic and Logic Structures}{High-Speed Arithmetic}
\category{B.7.1}{Integrated Circuits}{Types and Design Styles}[algorithms
implemented into hardware]
If I would set up an inset
2012/11/29 Uwe Stöhr :
> But our layouts are not all paragraphs. Many of them behave like a normal
> command in a line, especially the frontmatter things for scientific papers.
They still are paragraphs.
> Besides this, how should I implement this?:
>
> \category{B.2.4}{Arithmetic and Logic Struc
2012/11/29 Uwe Stöhr :
> Is it technically possible to support such cases/do you plan support for
> this?
No.
Jürgen
On 11/28/2012 06:21 PM, Uwe Stöhr wrote:
Am 27.11.2012 09:56, schrieb Jürgen Spitzmüller:
But how can i force that argument 3 is output after the text the users
enters in LyX?
Currently not possible. All command options are put before the
paragraph, all
environment options after the environ
Am 27.11.2012 09:56, schrieb Jürgen Spitzmüller:
But how can i force that argument 3 is output after the text the users
enters in LyX?
Currently not possible. All command options are put before the paragraph, all
environment options after the environment name.
Is it technically possible to s
Am 27.11.2012 09:32, schrieb Jean-Marc Lasgouttes:
If they must belong to a same paragraph, then these should be insets. I do not
think it makes sense
to implement paragraph layouts that do not behave as paragraphs.
But our layouts are not all paragraphs. Many of them behave like a normal com
Uwe Stöhr wrote:
> But how can i force that argument 3 is output after the text the users
> enters in LyX?
Currently not possible. All command options are put before the paragraph, all
environment options after the environment name.
> I could alternatively setup 4 arguments but then the user has
Le 27/11/2012 00:08, Uwe Stöhr a écrit :
Is there a way to suppress the empty lines? This problem appears for
several document classes so that a solution would save a lot of ERT.
If they must belong to a same paragraph, then these should be insets. I
do not think it makes sense to implement pa
Am 26.11.2012 23:56, schrieb Uwe Stöhr:
But there is a case I still cannot handle:
for sigplanconf I have this command
\category{CR-number}{subcategory}{third-level}[additional description]
...
It gets even worse.
Consecutive categories must also appear in LaTeX consecutively:
-
Am 26.11.2012 15:53, schrieb Uwe Stöhr:
Thank you, I'll give it a try the next days.
I couldn't resist and I can report that it works fine.
But there is a case I still cannot handle:
for sigplanconf I have this command
\category{CR-number}{subcategory}{third-level}[additional description]
Uwe Stöhr wrote:
> But isn't
>
> http://www.lyx.org/trac/changeset/e0f392e075e8e99732f4e2966700158185b5fb95/l
> yxgit
>
> a fileformat change?
No. Not even a layout format change proper, since nothing needs to be
converted and the new tags will be simply ignored by olde versions.
Jürgen
Am 26.11.2012 09:14, schrieb Jürgen Spitzmüller:
Uwe Stöhr wrote:
Argument 1
Mandatory 1
LabelString "Company name"
Tooltip "company name"
Font
Series Bold
Shape
Uwe Stöhr wrote:
> But this would look ugly. For example when I have
>
> LabelString "Left item summary"
>
> Its size is OK for the insert menu entry, but for the label of the
> collapsible, this would make some documents quite unreadable. (in my
> particular case a command has 4 man
Uwe Stöhr wrote:
> - Some commands output the arguments in a different font style, especially
> mandatory arguments. For example for modernCV I would need this:
>
> Style Recipient
> LatexType Command
> LatexName recipient
> Argument 1
>
Uwe Stöhr wrote:
> OK, but then one has to keep the label short and the tooltip has to be
> different than the label. I first tried to keep them identic to save
> translation work.
But then it would not make sense to have two strings. We should use the
tooltips to give the users some hints. Have
Am 24.11.2012 16:39, schrieb Jürgen Spitzmüller:
"Opt" and "Req" are too vague. This is what my work is all about.
Find strings that are suitable for both the menu and the button.
OK, but then one has to keep the label short and the tooltip has to be different than the label. I
first tried t
Jürgen Spitzmüller wrote:
> Uwe Stöhr wrote:
> > - if I have a mandatory argument, the label of the collapsible inset still
> > has the name "opt". This is confusing and I fear that users think they
> > can
> > omit it. I therefore propose to change it to "required" or "req"
>
> This is a bug. It
Uwe Stöhr wrote:
> And I thought that is why we have the tooltip so that the user can always
> see what an argument is for.
No, the tooltip is the place to giv e some short usage explanation.
Jürgen
Uwe Stöhr wrote:
> But this would look ugly. For example when I have
>
> LabelString "Left item summary"
>
> Its size is OK for the insert menu entry, but for the label of the
> collapsible, this would make some documents quite unreadable. (in my
> particular case a command has 4 man
Am 24.11.2012 16:20, schrieb Uwe Stöhr:
Its size is OK for the insert menu entry, but for the label of the collapsible,
this would make some
documents quite unreadable. (in my particular case a command has 4 mandatory
arguments, thus also a
"Left item text" and "Right item summary". (modernCV)
Am 24.11.2012 16:00, schrieb Jürgen Spitzmüller:
This is a bug. It should neither display "opt" nor "req", but the labelstring.
I'll have a look.
But this would look ugly. For example when I have
LabelString "Left item summary"
Its size is OK for the insert menu entry, but for th
Uwe Stöhr wrote:
> - if I have a mandatory argument, the label of the collapsible inset still
> has the name "opt". This is confusing and I fear that users think they can
> omit it. I therefore propose to change it to "required" or "req"
This is a bug. It should neither display "opt" nor "req", b
33 matches
Mail list logo
