Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
On Sun, Mar 27, 2005 at 11:48:33PM +0200, Uwe St?hr wrote: 1. The last months I teached LyX to some colleagues and they all complained that there is no button in the toolbar for view/update dvi. Therefore I designed a new toolbar with new buttons. It looks like in the attached file toolbar.png. I added two buttons for dvi, one button for export-pdf, the search and find button, and the button for depth-decrement. The latter because nobody understands why we have a button for depth-increment but not for decrement. I tested this toolbar for the last month while reworking the userguide, and I find it very ergonomic. What is your opinion? (I attached the xpm for the new buttons) Any toolbar changes need to be against current 1.4cvs (which includes, for example, both depth-decrement and depth-increment). There is no view dvi/pdf, but I'm not too happy with two buttons a piece for view/update. I've completely forgotten the mechanism and the code for how update works, but it's not really suitable to have both in a toolbar (unless we add an off-by-default 'Export' toolbar or something). 2. We should strictly separate - emphasize and italic - noun and small caps Emphasize and noun are logical attributes and every document class can define its own font for them. Work has started on this in 1.4cvs (much, much more work to do). Explicit modification of italic etc. is eventually going to go away altogether in favour of styles. 3. A minor change in the Layout-Document-Layout dialog: + paragraph separation - separation Because I noticed that newbies don't understand what to separate. Fixed in Qt frontend at least in 1.4cvs regards john
Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
John Levon wrote:
Any toolbar changes need to be against current 1.4cvs (which includes,
for example, both depth-decrement and depth-increment).
Of course against 1.4CVS, all proposals are for LyX 1.4 or 1.5.
I as stupid Win-user haven't ever seen LyX 1.4. So please be indulgent
with me if I propose stuff that is already in LyX 1.4.
Work has started on this in 1.4cvs (much, much more work to do).
Explicit modification of italic etc. is eventually going to go away
altogether in favour of styles.
I don't undertand this. What is a style and what is its advantage?
At the moment LyX uses
\newcommand{\noun}[1]{\textsc{#1}}
for the Noun style. \textsc switches to the small caps font shape,
that is part of the font family.
\textit is the analogon to \textsc for italic. So why should we drop
support for italic?
regards Uwe
Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
On Sun, Mar 27, 2005 at 11:48:33PM +0200, Uwe St?hr wrote: > 1. The last months I teached LyX to some colleagues and they all > complained that there is no button in the toolbar for "view/update dvi". > Therefore I designed a new toolbar with new buttons. It looks like in > the attached file toolbar.png. I added two buttons for dvi, one button > for export->pdf, the search and find button, and the button for > depth-decrement. > The latter because nobody understands why we have a button for > depth-increment but not for decrement. > I tested this toolbar for the last month while reworking the userguide, > and I find it very ergonomic. What is your opinion? > (I attached the xpm for the new buttons) Any toolbar changes need to be against current 1.4cvs (which includes, for example, both depth-decrement and depth-increment). There is no view dvi/pdf, but I'm not too happy with two buttons a piece for view/update. I've completely forgotten the mechanism and the code for how update works, but it's not really suitable to have both in a toolbar (unless we add an off-by-default 'Export' toolbar or something). > 2. We should strictly separate > - emphasize and italic > - noun and small caps > Emphasize and noun are logical attributes and every document class can > define its own font for them. Work has started on this in 1.4cvs (much, much more work to do). Explicit modification of italic etc. is eventually going to go away altogether in favour of styles. > 3. A minor change in the Layout->Document->Layout dialog: > + paragraph separation > - separation > Because I noticed that newbies don't understand what to separate. Fixed in Qt frontend at least in 1.4cvs regards john
Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
John Levon wrote:
Any toolbar changes need to be against current 1.4cvs (which includes,
for example, both depth-decrement and depth-increment).
Of course against 1.4CVS, all proposals are for LyX 1.4 or 1.5.
I as stupid Win-user haven't ever seen LyX 1.4. So please be indulgent
with me if I propose stuff that is already in LyX 1.4.
Work has started on this in 1.4cvs (much, much more work to do).
Explicit modification of italic etc. is eventually going to go away
altogether in favour of styles.
I don't undertand this. What is a style and what is its advantage?
At the moment LyX uses
\newcommand{\noun}[1]{\textsc{#1}}
for the "Noun style". \textsc switches to the small caps font shape,
that is part of the font family.
\textit is the analogon to \textsc for italic. So why should we drop
support for italic?
regards Uwe
Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
I'll split my proposals to mails of five proposals to keep the overview.
Here the first five, others will follow the next days.
1. The last months I teached LyX to some colleagues and they all
complained that there is no button in the toolbar for view/update dvi.
Therefore I designed a new toolbar with new buttons. It looks like in
the attached file toolbar.png. I added two buttons for dvi, one button
for export-pdf, the search and find button, and the button for
depth-decrement.
The latter because nobody understands why we have a button for
depth-increment but not for decrement.
I tested this toolbar for the last month while reworking the userguide,
and I find it very ergonomic. What is your opinion?
(I attached the xpm for the new buttons)
2. We should strictly separate
- emphasize and italic
- noun and small caps
Emphasize and noun are logical attributes and every document class can
define its own font for them.
This will help to fullfill writing style restrictions of some publisher
classes.
At the moment you can mark italic text, press the toolbar button for
emphasizing and the text becomes upright.
3. A minor change in the Layout-Document-Layout dialog:
+ paragraph separation
- separation
Because I noticed that newbies don't understand what to separate.
4. When you create a new label, LyX will start with a prefix, e.g. eq:
when you label a formula. The current prefixes are:
- cha: for chapters
- cap: for captions
I would propose to change them to:
- chap: for chapters, because this is more intuitive
- fig: for figure captions
- tab: for table captipons
- alg: for algorithm caption
The latter three would improve the searching for references in large
documents. My proposals were used in former versions of LyX, as you can
see in the current userguide. So I just want this behaviour back.
5. We should add the entries capitalized, upcase and lowcase to
the combobox misc in the the dialog Layout-Character. Because they
are implemented in LyX - there are the following well-working entries in
the file menu.bind:
\bind M-c Down word-lowcase
\bind M-c Upword-upcase
\bind M-c Right word-capitalize
But as they are not available in a menu nor documented, nobody will use
them.
Enough for today. Thanks for your patience and regards
Uwe
p.s. rework docs status: 100% of Intro.lyx, 70% of Userguide.lyx
Sorry, but the docs are huge and I didn't have much rainy afternoons ;-).
inline: toolbar.png/* XPM */
static char * buffer-view_pdf[] = {
18 20 2 1,
c red,
. c None,
..,
..,
.,
... ,
... . ,
... ,
.,
,
... . ,
... .. ..,
... ... . ..,
.. .. ,
. .. ...,
. ..,
,
.. .,
. .. .,
.. ..,
. ...,
..};
/* XPM */
static char const * view_dvi_xpm[] = {
20 20 2 1,
c None,
. c #,
,
.. ,
.. ,
.... ,
... .. ,
. . .. ,
. . .. . ,
. . .. . . ,
. . .. . ,
. . . ... . . . . ,
. . . . . . . . . ,
. . . . . . . . . ,
. . . ... . . . ,
. . .. ,
. . .. ,
. .. ,
. .. ,
.. ,
.. ,
};
/* XPM */
static char const * find_xpm[] = {
17 20 3 1,
c black,
; c none,
: c gray100,
;,
;,
;,
;;; ,
: ;;; : ,
;;; ,
;;; ; ;;;,
;;; : ; : ;;;,
;; ;;,
; : : : ;,
; : : : ;,
; : : ;,
; ; ;,
; : ; : ;,
; : ; : ;,
; ; ;,
;,
;,
;,
;};
/* XPM */
static char const * run_latex_xpm[] = {
19 20 2 1,
c None,
. c #,
,
..,
..,
..,
..,
. . .,
. . . .,
. . .,
. . . . .,
. . . . . . .,
. . . . . . .,
. . . . . . .,
. .... . .,
..,
..,
..,
..,
..,
,
};
Re: [rework docs] a new round of asking and proposing - part two: proposals 1-5
I'll split my proposals to mails of five proposals to keep the overview.
Here the first five, others will follow the next days.
1. The last months I teached LyX to some colleagues and they all
complained that there is no button in the toolbar for "view/update dvi".
Therefore I designed a new toolbar with new buttons. It looks like in
the attached file toolbar.png. I added two buttons for dvi, one button
for export->pdf, the search and find button, and the button for
depth-decrement.
The latter because nobody understands why we have a button for
depth-increment but not for decrement.
I tested this toolbar for the last month while reworking the userguide,
and I find it very ergonomic. What is your opinion?
(I attached the xpm for the new buttons)
2. We should strictly separate
- emphasize and italic
- noun and small caps
Emphasize and noun are logical attributes and every document class can
define its own font for them.
This will help to fullfill writing style restrictions of some publisher
classes.
At the moment you can mark italic text, press the toolbar button for
emphasizing and the text becomes upright.
3. A minor change in the Layout->Document->Layout dialog:
+ paragraph separation
- separation
Because I noticed that newbies don't understand what to separate.
4. When you create a new label, LyX will start with a prefix, e.g. "eq:"
when you label a formula. The current prefixes are:
- "cha:" for chapters
- "cap:" for captions
I would propose to change them to:
- "chap:" for chapters, because this is more intuitive
- "fig:" for figure captions
- "tab:" for table captipons
- "alg:" for algorithm caption
The latter three would improve the searching for references in large
documents. My proposals were used in former versions of LyX, as you can
see in the current userguide. So I just want this behaviour back.
5. We should add the entries "capitalized", "upcase" and "lowcase" to
the combobox "misc" in the the dialog Layout->Character. Because they
are implemented in LyX - there are the following well-working entries in
the file menu.bind:
\bind "M-c Down" "word-lowcase"
\bind "M-c Up""word-upcase"
\bind "M-c Right" "word-capitalize"
But as they are not available in a menu nor documented, nobody will use
them.
Enough for today. Thanks for your patience and regards
Uwe
p.s. rework docs status: 100% of Intro.lyx, 70% of Userguide.lyx
Sorry, but the docs are huge and I didn't have much rainy afternoons ;-).
<>/* XPM */
static char * buffer-view_pdf[] = {
"18 20 2 1",
" c red",
". c None",
"..",
"..",
" .",
"... ",
"... . ",
"... ",
" .",
" ",
"... . ",
"... .. ..",
"... ... . ..",
".. .. ",
". .. ...",
". ..",
" ",
".. .",
". .. .",
" .. ..",
". ...",
".."};
/* XPM */
static char const * view_dvi_xpm[] = {
"20 20 2 1",
" c None",
". c #",
"",
" .. ",
" .. ",
" .... ",
" ... .. ",
" . . .. ",
" . . .. . ",
" . . .. . . ",
" . . .. . ",
" . . . ... . . . . ",
" . . . . . . . . . ",
" . . . . . . . . . ",
" . . . ... . . . ",
" . . .. ",
" . . .. ",
" . .. ",
" . .. ",
" .. ",
" .. ",
""};
/* XPM */
static char const * find_xpm[] = {
"17 20 3 1",
" c black",
"; c none",
": c gray100",
";",
";",
";",
" ;;; ",
" : ;;; : ",
" ;;; ",
";;; ; ;;;",
";;; : ; : ;;;",
";; ;;",
"; : : : ;",
"; : : : ;",
"; : : ;",
"; ; ;",
"; : ; : ;",
"; : ; : ;",
"; ; ;",
";",
";",
";",
";"};
/* XPM */
static char const * run_latex_xpm[] = {
"19 20 2 1",
"c None",
". c #",
" ",
" ..",
" ..",
" ..",
" ..",
" . . .",
" . . . .",
" . . .",
" . . . . .",
" . . . . . . .",
" . . . . . . .",
" . . . . . . .",
" . .... . .",
" ..",
" ..",
" ..",
" ..",
" ..",
" ",
" "};
