Re: [PATCH] UI: matrix partitioning
Martin Vermeer wrote:
If I may summarize what I think it _should_ do:
1) If you want to swap two rows, make sure you're not on the last row.
No. If you are on the last row, it is swapped with the second to last one.
This is consistent with the tabular inset, so we should not change it.
2) If you want to swap two columns, make sure you're not in the
rightmost column.
Same as above.
3) If you want to delete a horizontal or vertical line, make sure there
is one (or more) in the place (above row, left to column) to delete.
(adding or deleting rows or columns is always possible, so no conditions
there; right?)
No. Adding is always possible, but the code depends on the fact that we have
at least one row and one column.
Disable if any of these conditions is violated, otherwise enable. All
three require cursor (cur) and rowinfo_/colinfo_ knowledge... but we
have that in getStatus, don't we?
Yes.
(Item 3 is optional; a silent fail is unelegant, however. Strictly
speaking all three are optional if one accepts silent failure)
It is not optional IMO.
In the meantime I had a look at vlines to the right and hlines at the
bottom. It turned out that both are already supported: MathGridInset stores
a dummy row and dummy column for this purpose. There were only two little
bugs:
1. The rightmost '|' was not handled correctly in MathGridInset::halign()
2. The following code
\begin{array}{|c|c|}
\hline
1 2 \\ \hline
3 4 \\ \hline
\end{array}
produced one additional empty row because of the last '\\'. I changed the
math parser to delete this line and implemented one FIXME as a side effect.
It would be nice if you could merge the attached patch with yours and commit
it, because I don't have time to work on that right now.
GeorgIndex: lib//ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.672
diff -u -p -r1.672 ChangeLog
--- lib//ChangeLog 9 Feb 2005 18:56:00 - 1.672
+++ lib//ChangeLog 10 Feb 2005 08:16:19 -
@@ -1,3 +1,8 @@
+2005-02-10 Georg Baum [EMAIL PROTECTED]
+
+ * ui/stdmenus.ui: add more facilities for drawing/deleting partition
+ lines in matrix
+
2005-02-09 Martin Vermeer [EMAIL PROTECTED]
* ui/stdmenus.ui: add facilities for drawing/deleting partition
Index: lib//ui/stdmenus.ui
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ui/stdmenus.ui,v
retrieving revision 1.40
diff -u -p -r1.40 stdmenus.ui
--- lib//ui/stdmenus.ui 9 Feb 2005 18:56:01 - 1.40
+++ lib//ui/stdmenus.ui 10 Feb 2005 08:16:21 -
@@ -159,14 +159,18 @@ Menuset
Item Copy Row tabular-feature copy-row
Item Swap Rows tabular-feature swap-row
Item Add Line Above tabular-feature add-hline-above
+ Item Add Line Below tabular-feature add-hline-below
Item Delete Line Above tabular-feature delete-hline-above
+ Item Delete Line Below tabular-feature delete-hline-below
Separator
Item Add Column|C tabular-feature append-column
Item Delete Column|e tabular-feature delete-column
Item Copy Column tabular-feature copy-column
Item Swap Columns tabular-feature swap-column
Item Add Line to Left tabular-feature add-vline-left
+ Item Add Line to Right tabular-feature add-vline-right
Item Delete Line to Left tabular-feature delete-vline-left
+ Item Delete Line to Right tabular-feature delete-vline-right
End
Menu edit_math_limits
? src/mathed/math_intertextinset.C
? src/mathed/math_intertextinset.h
Index: src/mathed/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.470
diff -u -p -r1.470 ChangeLog
--- src/mathed/ChangeLog 9 Feb 2005 18:56:00 - 1.470
+++ src/mathed/ChangeLog 10 Feb 2005 08:18:16 -
@@ -1,4 +1,15 @@
- ChangeLog
+2005-02-10 Georg Baum [EMAIL PROTECTED]
+
+ * math_gridinset.C (halign): fix '|' to the right of the last column
+ * math_gridinset.[Ch]: remove unused leftline_ and rightline_
+ * math_gridinset.C: add more facilities for adding/deleting
+ partition lines in matrix.
+ * math_gridinset.C (getStatus): implement missing LFUN_TABULAR_FEATURE
+ * math_parser.C (delEmptyLastRow): new
+ * math_parser.C (parse1): Store active environment and use it to
+ detect nonmatching \end{} and removing superflous rows with
+ delEmptyLastRow()
+
2005-02-09 Martin Vermeer [EMAIL PROTECTED]
* math_gridinset.[hC]: add facilities for drawing/deleting partition
Index: src/mathed/math_gridinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_gridinset.C,v
retrieving revision 1.155
diff -u -p -r1.155 math_gridinset.C
--- src/mathed/math_gridinset.C 9 Feb 2005 18:56:00 - 1.155
+++ src/mathed/math_gridinset.C 10 Feb 2005 08:18:17 -
@@ -124,7 +124,7 @@ int MathGridInset::RowInfo::skipPixels()
update
hi there, sorry, i'm completely new in lyx. how can i update from 1.3.3 to 1.3.4?? i downloaded everything but what shall i do then? what do i have to to with this .tar files and patches? is there any update program? greets trinae -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION Kein Einrichtungspreis nutzen: http://www.gmx.net/de/go/dsl
Re: [PATCH] UI: matrix partitioning
On Thu, 2005-02-10 at 10:34, Georg Baum wrote:
Martin Vermeer wrote:
...
It would be nice if you could merge the attached patch with yours and commit
it, because I don't have time to work on that right now.
OK.
What does this do? I don't get it.
if (!lyx::support::contains(tcb, cmd.argument[0])) {
flag.enable(false);
break;
}
flag.setOnOff(cmd.argument[0] == v_align_);
Georg
- Martin
signature.asc
Description: This is a digitally signed message part
Re: Problem writing a converter
Bernard Hurley [EMAIL PROTECTED] writes: On Sun, 2005-02-06 at 11:38 +0100, Georg Baum wrote: ... Sorry, I forgot that such a parameter exists already: $$p I can't get this to work! The value p is passed to the converter where is the PID of the shell that calls the converter. I checked the code in 140cvs and it looks as if this parameter does not get used (any more?). I think the official way to solve your problem is to use a copier. That's like a converter but copies a file from one dir to another, translating references to external files on the way. See scripts/fig_copy.sh for an example. Would this be possible for your problem or do you need the real original directory? Ciao /Andreas
Re: update
Felix == Felix Sager [EMAIL PROTECTED] writes: Felix hi there, sorry, i'm completely new in lyx. Felix how can i update from 1.3.3 to 1.3.4?? Felix i downloaded everything but what shall i do then? what do i Felix have to to with this .tar files and patches? is there any Felix update program? What is the operating system you use? JMarc
Re: [patch] fix frameless box - parbox conversion in lyx2lyx
On Monday 07 February 2005 11:39, Jean-Marc Lasgouttes wrote: This is not really for 1.3, since it is due to problems with the use of tex2lyx with newish features like parbox. We don't distribute tex2lyx with 1.3.x anyway. True. OTOH, I guess the lyx2lyx which is now on HEAD will be distributed with lyx 1.3.6 (or another one) anyway, so this code matters. True. Also this fixes a real bug. I'll follow Jose's judgment on this. As far as can see this seems to fix a real bug so I will trust Georg judgment on this. I understood Georg's argument but I didn't tried the patch. :-) I consider the retroversion as a fall back scheme, and if we can make it work better yet. :-) JMarc -- José Abílio
Re: Problem writing a converter
Andreas Vox wrote: Bernard Hurley [EMAIL PROTECTED] writes: I can't get this to work! The value p is passed to the converter where is the PID of the shell that calls the converter. Sorry again. This is only available for viewing, not for converting. I checked the code in 140cvs and it looks as if this parameter does not get used (any more?). Indeed. I don't know why. But Bernard uses 1.3, so this won't help. I think the official way to solve your problem is to use a copier. That's like a converter but copies a file from one dir to another, translating references to external files on the way. See scripts/fig_copy.sh for an example. Maybe. Maybe it is also a good idea to use $$p for converters, but we need to know why the converter needs that flag in order to decide that. Georg
What are the main problems in CVS now?
It might be that I am a bit out. But I see no bug problems in CVS currently. What must be fixed for 1.4.0? (and bugzilla is not up to snuff...) I'd like all code-cleanup, feature-fixing etc to stop now and go into hard freeze and only fix regressions and crashes. -- Lgb
Re: [patch] fix frameless box - parbox conversion in lyx2lyx
Jose' Matos wrote: As far as can see this seems to fix a real bug so I will trust Georg judgment on this. I understood Georg's argument but I didn't tried the patch. :-) Then I'll commit it. I did test it, and even if there is still a bug I am sure that it is not a principal problem. I consider the retroversion as a fall back scheme, and if we can make it work better yet. :-) I consider it quite important, because it makes it easy to try LyX 1.4 and switch back if necessary. Georg
Re: What are the main problems in CVS now?
Lars Gullik Bjønnes wrote: It might be that I am a bit out. But I see no bug problems in CVS currently. What must be fixed for 1.4.0? (and bugzilla is not up to snuff...) I'd say the important ones are targeted for MILESTONE 1.4.0 (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset [e.g., when the document has a caption outside a float], which is not yet in bugzilla). Lots of Alfredo stuff, if you ask me. Jürgen
Re: What are the main problems in CVS now?
Lars Gullik Bjnnes [EMAIL PROTECTED] writes: It might be that I am a bit out. But I see no bug problems in CVS currently. What must be fixed for 1.4.0? Currently I have problems with crashes related to fast events and previews/forked processes. For example, when I start LyX, open the user guide and keep the DOWN ley pressed, I wont reach the end of the document: Date/Time: 2005-02-10 13:55:24 +0100 OS Version: 10.3.7 (Build 7S215) Report Version: 2 Command: lyx Path:/Applications/LyX.app/Contents/MacOS/lyx Version: ??? (???) PID: 21179 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0002 Thread 0 Crashed: 0 lyx 0x006a31cc 0x1000 + 0x6a21cc 1 lyx 0x000f3ea0 lyx::support::ForkedcallsContr oller::handleCompletedProcesses() + 0x2d0 (shared_count.hpp:378) 2 lyx 0x82cc BufferView::Pimpl::cursorToggle( ) + 0x40 (BufferView_pimpl.C:660) 3 lyx 0x0062ed50 0x1000 + 0x62dd50 4 lyx 0x00633d94 0x1000 + 0x632d94 5 lyx 0x006331d0 0x1000 + 0x6321d0 6 lyx 0x00631124 0x1000 + 0x630124 7 lyx 0x000e3428 Timeout::emit() + 0x68 (Timeo ut.C:52) 8 lyx 0x001d70b8 QObject::event(QEvent*) + 0xec (ControlCommandBuffer.C:137) 9 lyx 0x001c3dd0 QApplication::internalNotify(QO bject*, QEvent*) + 0x2fc (qt_helpers.C:205) ... I surmise that's another Qt-multithreading related bug. I have some local patches related to PreviewLoader and BufferView_pimpl. If noone else can reproduce this under LyX/Qt with preview on, I can try to reproduce it with a vanilla cvs version. Another impression I got is that the positioning during scrolling is not exact with previews on. For example, I can scroll up in a long document until the scrollbar is at the top, but the part of the document which is shown isn't even near the beginning. If I click into the buffer and use PAGEUP, I can reach the top of the docuemnt. What about my PreviewLoader refactoring and the bitmap production for Docbook equations? I could make a final patch pretty fast and it mostly only affects docbook. If you are dead against it, would it be possible to have a fast 1.4.1 version including these patches? In my view Docbook support is sub-standard right now. Ciao /Andreas
Re: What are the main problems in CVS now?
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars But I see no bug problems in CVS currently. What must be fixed Lars for 1.4.0? Lars I'd like all code-cleanup, feature-fixing etc to stop now and go Lars into hard freeze and only fix regressions and crashes. One thing I see that may need big changes is that selecting with the mouse is terribly slow. Also, selection by double click is broken. We have to decide what to do about change tracking. We do not have a working bibinset. There are probably many other things, but that's all I remember from the top of my head. JMarc
Re: Bug: Flickering
Luke == Luke Simon [EMAIL PROTECTED] writes: Luke The main editor pane of Lyx flickers when scrolling up or down Luke using the scrollbar. It really destroys the visual polish of Luke this great application. I do not see this... What OS/computer are you using? JMarc
Re: [PATCH] UI: matrix partitioning
On Thu, 2005-02-10 at 10:34, Georg Baum wrote:
...
It would be nice if you could merge the attached patch with yours and commit
it, because I don't have time to work on that right now.
Georg
Done. Result attached. Works.
- Martin
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.672
diff -u -r1.672 ChangeLog
--- lib/ChangeLog 9 Feb 2005 18:56:00 - 1.672
+++ lib/ChangeLog 10 Feb 2005 13:38:07 -
@@ -1,3 +1,12 @@
+2005-02-10 Georg Baum [EMAIL PROTECTED]
+
+ * ui/stdmenus.ui: add more facilities for drawing/deleting partition
+ lines in matrix
+
+2005-02-10 Martin Vermeer [EMAIL PROTECTED]
+
+ * bind/math.bind: provide key bindings for lines in matrix
+
2005-02-09 Martin Vermeer [EMAIL PROTECTED]
* ui/stdmenus.ui: add facilities for drawing/deleting partition
Index: src/mathed/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.470
diff -u -r1.470 ChangeLog
--- src/mathed/ChangeLog 9 Feb 2005 18:56:00 - 1.470
+++ src/mathed/ChangeLog 10 Feb 2005 13:38:08 -
@@ -1,4 +1,19 @@
- ChangeLog
+2005-02-10 Georg Baum [EMAIL PROTECTED]
+
+ * math_gridinset.C (halign): fix '|' to the right of the last column
+ * math_gridinset.[Ch]: remove unused leftline_ and rightline_
+ * math_gridinset.C: add more facilities for adding/deleting
+ partition lines in matrix.
+ * math_gridinset.C (getStatus): implement missing LFUN_TABULAR_FEATURE
+ * math_parser.C (delEmptyLastRow): new
+ * math_parser.C (parse1): Store active environment and use it to
+ detect nonmatching \end{} and removing superflous rows with
+ delEmptyLastRow()
+
+2005-02-10 Martin Vermeer [EMAIL PROTECTED]
+
+ * math_gridinset.C: implement getStatus for tabular-features.
+
2005-02-09 Martin Vermeer [EMAIL PROTECTED]
* math_gridinset.[hC]: add facilities for drawing/deleting partition
Index: src/mathed/math_gridinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_gridinset.C,v
retrieving revision 1.155
diff -u -r1.155 math_gridinset.C
--- src/mathed/math_gridinset.C 9 Feb 2005 18:56:00 - 1.155
+++ src/mathed/math_gridinset.C 10 Feb 2005 13:38:08 -
@@ -22,6 +22,7 @@
#include cursor.h
#include debug.h
#include funcrequest.h
+#include gettext.h
#include undo.h
#include frontends/Painter.h
@@ -124,7 +125,7 @@
MathGridInset::ColInfo::ColInfo()
- : align_('c'), leftline_(false), rightline_(false), lines_(0)
+ : align_('c'), lines_(0)
{}
@@ -215,11 +216,12 @@
{
col_type col = 0;
for (string::const_iterator it = hh.begin(); it != hh.end(); ++it) {
- if (col = ncols())
- break;
char c = *it;
if (c == '|') {
colinfo_[col].lines_++;
+ } else if (col = ncols()) {
+ // Only '|' is allowed in the last dummy column
+ break;
} else if (c == 'c' || c == 'l' || c == 'r') {
colinfo_[col].align_ = c;
++col;
@@ -1102,8 +1104,12 @@
swapRow(cur.row());
else if (s == add-hline-above)
rowinfo_[cur.row()].lines_++;
+ else if (s == add-hline-below)
+ rowinfo_[cur.row()+1].lines_++;
else if (s == delete-hline-above)
- rowinfo_[cur.row()].lines_ = 0;
+ rowinfo_[cur.row()].lines_--;
+ else if (s == delete-hline-below)
+ rowinfo_[cur.row()+1].lines_--;
else if (s == append-column)
for (int i = 0, n = extractInt(is); i n; ++i) {
row_type r = cur.row();
@@ -1125,9 +1131,13 @@
else if (s == swap-column)
swapCol(col(cur.idx()));
else if (s == add-vline-left)
- colinfo_[col(cur.idx())].lines_++;
+ colinfo_[col(cur.idx())].lines_++;
+ else if (s == add-vline-right)
+ colinfo_[col(cur.idx())+1].lines_++;
else if (s == delete-vline-left)
- colinfo_[col(cur.idx())].lines_ = 0;
+ colinfo_[col(cur.idx())].lines_--;
+ else if (s == delete-vline-right)
+ colinfo_[col(cur.idx())+1].lines_--;
else {
cur.undispatched();
break;
@@ -1223,25 +1233,41 @@
{
bool ret = true;
switch (cmd.action) {
- case LFUN_TABULAR_FEATURE:
-#if 0
- // should be more precise
- if (v_align_ == '\0') {
- flag.enable(true);
- break;
+ case LFUN_TABULAR_FEATURE: {
+ istringstream is(cmd.argument);
+string s;
+is s;
+ if (nrows() = 1
+ (s == delete-row || s == swap-row)) {
+ flag.message(N_(Only one row));
+flag.enabled(false);
+ return true;
}
- if (cmd.argument.empty()) {
- flag.enable(false);
- break;
+ if (ncols() = 1
+ (s == delete-column || s == swap-column)) {
+ flag.message(N_(Only one column));
+flag.enabled(false);
+ return true;
}
- if (!contains(tcb, cmd.argument[0])) {
- flag.enable(false);
- break;
+ if ((colinfo_[col(cur.idx())].lines_ == 0
+ (s == delete-vline-left))
+ || ((colinfo_[col(cur.idx())
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: | Lars But I see no bug problems in CVS currently. What must be fixed | Lars for 1.4.0? | Lars I'd like all code-cleanup, feature-fixing etc to stop now and go | Lars into hard freeze and only fix regressions and crashes. | One thing I see that may need big changes is that selecting with the | mouse is terribly slow. | Also, selection by double click is broken. | We have to decide what to do about change tracking. | We do not have a working bibinset. | There are probably many other things, but that's all I remember from | the top of my head. Then we should work on fixing these regressions, but improving any other feature that we have. I'll have a look at the double click issue. -- Lgb
Re: What are the main problems in CVS now?
Juergen Spitzmueller [EMAIL PROTECTED] writes: I'd say the important ones are targeted for MILESTONE 1.4.0 (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset [e.g., when the document has a caption outside a float], which is not yet in bugzilla). When I search for open bugs with crash in the summary, I get: 220(relyx), 1119, 1384, 1395, 1466, 1474, 1589, 1595, 1598, 1604, 1735, 1753, 1750(relyx), 1771, 1785, 1788. Some of those might be gone by now, but at least 1119 and 1598(s.a.) are not. Anyway, we should check all those and the 24 open bugs of importance and either close or fix them before 1.4. You may assign half a dozen to me, if you like. Ciao /Andreas
Re: What are the main problems in CVS now?
Andreas Vox [EMAIL PROTECTED] writes: | Juergen Spitzmueller [EMAIL PROTECTED] writes: I'd say the important ones are targeted for MILESTONE 1.4.0 (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset [e.g., when the document has a caption outside a float], which is not yet in bugzilla). | When I search for open bugs with crash in the summary, I get: | 220(relyx), 1119, 1384, 1395, 1466, 1474, 1589, 1595, 1598, 1604, | 1735, 1753, 1750(relyx), 1771, 1785, 1788. If they are not marked with taget 1.4.0 then I don't see them. (and if they are not marked, they need to be verified to be present on 1.4.0) -- Lgb
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: One thing I see that may need big changes is that selecting with the mouse is terribly slow. Can't confirm that for LyX/Aqua. /Andreas
Re: What are the main problems in CVS now?
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Then we should work on fixing these regressions, but improving Lars any other feature that we have. Yes. Lars I'll have a look at the double click issue. OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not sure it is going to get used. For 1.3.0 we had Michael's bug list which was very useful. JMarc
Re: What are the main problems in CVS now?
Lars Gullik Bjnnes [EMAIL PROTECTED] writes: If they are not marked with taget 1.4.0 then I don't see them. (and if they are not marked, they need to be verified to be present on 1.4.0) ?? So open bugs which should be fixed for target 1.3.6 wont get fixed for target 1.4.0? I'm not sure if I understand the semantics of the target field. /Andreas
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes wrote: We have to decide what to do about change tracking. I think we can ship 1.4 with change tracking. The status is not worse (even a bit better) than the unofficial 1.3 version that has been distributed separately, and AFAIK people have used that for their daily work. The most annoying bug is 1277 (the crash when pasting insets). This one was also present in the 1.3 patch, until Johnathan Burchill provided a fixed patch, which has not yet ported to HEAD and also seems to need some more discussion. As I understand it, a real fix would need some major rewrite. Regards, Jürgen
Re: What are the main problems in CVS now?
Andreas Vox [EMAIL PROTECTED] writes: | Lars Gullik Bjønnes [EMAIL PROTECTED] writes: If they are not marked with taget 1.4.0 then I don't see them. (and if they are not marked, they need to be verified to be present on 1.4.0) | ?? | So open bugs which should be fixed for target 1.3.6 wont get fixed for | target 1.4.0? I'm not sure if I understand the semantics of the target | field. Me neither perhaps. We have some 250 open bugs, but no idea if they exist in 1.3.x or in HEAD. We need to be able to mark the bugs so that we know what to work on. -- Lgb
Interview with Mathias
Hi, you read it here: http://www.fosdem.org/index/interviews/interviews_ettrich There are two questions there related with LyX, that basically are due to the external perception that the LyX development is stalled... -- José Abílio
Re: What are the main problems in CVS now?
Andreas == Andreas Vox [EMAIL PROTECTED] writes: Andreas Lars Gullik Bjønnes [EMAIL PROTECTED] writes: If they are not marked with taget 1.4.0 then I don't see them. (and if they are not marked, they need to be verified to be present on 1.4.0) Andreas ?? So open bugs which should be fixed for target 1.3.6 wont Andreas get fixed for target 1.4.0? I'm not sure if I understand the Andreas semantics of the target field. Well, at this point we mainly look at regressions from 1.3.x to 1.4.0. We are not searching to fix all possible LyX bugs, but definitely want to fix new bugs. A possibility is to search for bugs reported against 1.4.0cvs. JMarc
Re: What are the main problems in CVS now?
Lars Gullik Bjnnes [EMAIL PROTECTED] writes: Me neither perhaps. We have some 250 open bugs, but no idea if they exist in 1.3.x or in HEAD. We need to be able to mark the bugs so that we know what to work on. So maybe we should use a wiki TODO list once more. My proposal: - bugs 1119, 1277, 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset - check when and why selecting with the mouse is terribly slow. - fix selection by double click is broken. - decide what to do about change tracking. - fix bibinset. - set PATH_prefix in lib/configure for Mac (Bennet complained about this. As it is now, LyX won't work out of the box on Mac) 1.4.1: - Polished Docbook support * write a bugreporting HOWTO that defines what fields are mandatory and how to choose between all those version, platform, target etc. values. Define how the status relates to the work schedule.
Re: Interview with Mathias
Jose' Matos [EMAIL PROTECTED] writes: | Hi, | you read it here: http://www.fosdem.org/index/interviews/interviews_ettrich | There are two questions there related with LyX, that basically are due to | the external perception that the LyX development is stalled... I read it as well. -- Lgb
Re: Interview with Mathias
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars | There are two questions there related with LyX, that basically Lars are due to | the external perception that the LyX development is Lars stalled... Lars I read it as well. These questions have been proposed on the linuxfr.org site: http://linuxfr.org/forums/40/6351.html JMarc
Re: What are the main problems in CVS now?
Andreas == Andreas Vox [EMAIL PROTECTED] writes: Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained Andreas about this. As it is now, LyX won't work out of the box on Andreas Mac) The other solution is to preset this in the preferences file, as is done currently for converters. Andreas 1.4.1: - Polished Docbook support Note that nothing that needs a format change will be accepted after 1.4.0. So be sure that you plan ahead. JMarc
Problems with PATH for lyx-13x on MacOS X
With recent versions of lyx-1.3.6 (but not 1.4.0), the PATH environment is not set up properly. There are two problems: 1. It looks as though /usr/bin and /usr/local/bin are not properly added, so attempting to run the configure script or view files results in errors like the following: sh: line 1: sh: No such file or directory sh: line 1: pplatex: No such file or directory sh: line 1: dvipdfm: No such file or directory sh: line 1: latex2html: No such file or directory sh: line 1: dvips: No such file or directory sh: line 1: open: No such file or directory 2. It looks like now users must manually enter the path to their TeX installation in the preference dialog. It would be nice to package LyX so that this was not necessary. So, is it possible to define a PATH and pass this to LyX without having LyX overwrite it? Thanks. Bennett
Re: [Plea] Math bitmaps for Docbook export in LyX 1.4.0, was: Directions needed: Preview and Exportdata
On Thursday 03 February 2005 17:46, Andreas Vox wrote: Jose' Matos [EMAIL PROTECTED] writes: You (we) must first convince Lars about it now. Probably a well laid out argument why this patch is important for docbook users. Hm, at least it's totally unimportant to non-Docbook users: the only common code which is touched is the refactoring of PreviewLoader, and I could replace that by CopyPaste. I would like to have this part of the code reviewed by Angus when he returns. :-) Also it's a fix to bugs #1713, #1714, #1715 and #1716 -- oh, it looks as if those are assigned to you, Jos! :-) :-o ;-) Ok, Lars, as Chris' argues on his webpage ( http://www.karakas-online.de/mySGML/ ) LyX 1.3 is not usable for serious Docbook editing. The main reason is the broken Math support: no Latex code, instead unused MathML code. We already fixed some deficiencies in 1.4.0cvs (drop MathML output for SGML, provide filenames, some escaping, other features). My last patch http://marc.theaimsgroup.com/?l=lyx-develm=110710201022468w=2 completes this in using preview.sty to produce bitmap files for all equations, thus not only providing the filenames but the files as well. Since these changes don't touch the non-Docbook users and LyX 1.2 was used by some (most?) Docbook users in favour of LyX 1.3, I think we should try to provide decent Docbook support for LyX 1.4.0. Is this convincing? It is for me. I should apologize to you as my time lately has been almost nil to look into this carefully. This will hopefully improve after the 22nd. Cheers /Andreas -- Jos Ablio
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Andreas == Andreas Vox [EMAIL PROTECTED] writes: Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained Andreas about this. As it is now, LyX won't work out of the box on Andreas Mac) The other solution is to preset this in the preferences file, as is done currently for converters. Problem is there are three likely paths: /sw/bin, /usr/local/teTeX/bin/powerpc-apple-darwin-current and /opt/local/teTeX/bin I thought of a solution where configure checks an additional list of directories when it looks for executable. Any time an executable is not found in the current opath but in one of those directories, it gets added to PATH_prefix. Could also be used on other platforms. Andreas 1.4.1: - Polished Docbook support Note that nothing that needs a format change will be accepted after 1.4.0. So be sure that you plan ahead. Just want to polish, not to re-forge :-) It's mainly the bitmap generation for equations, some tweeks to output_docbook() and improvement of the db layout files. Maybe enable the db classes even if no sgmltools or equivalent is found (output SGML/XML still works, and you can use the other classes without TeX, no?) Ciao /Andreas
Re: What are the main problems in CVS now?
On Feb 10, 2005, at 10:31 AM, Jean-Marc Lasgouttes wrote: Andreas == Andreas Vox [EMAIL PROTECTED] writes: Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained Andreas about this. As it is now, LyX won't work out of the box on Andreas Mac) The other solution is to preset this in the preferences file, as is done currently for converters. The trouble is, there are three possible locations for TeX installations on the Mac, all of which are commonly used: /usr/local/teTeX/bin/powerpc-apple-darwin-current, /opt/local/teTeX/bin, and /sw/bin. Is it possible to include all of these in the preference file? -- Simply entering /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin: /sw/bin doesn't seem to do it. The alternative would be to run a configuration script on installing LyX/Mac, but that prevents the simple drag-and-drop installation most desirable for the Mac. Bennett
Re: What are the main problems in CVS now?
Andreas Vox [EMAIL PROTECTED] writes: | Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Me neither perhaps. We have some 250 open bugs, but no idea if they exist in 1.3.x or in HEAD. We need to be able to mark the bugs so that we know what to work on. | So maybe we should use a wiki TODO list once more. My proposal: No... bugzilla should be used. If this is a bug we require to be fixed in 1.4.0 then that should be its target. If we have no idea then we remove target, if we expect it to be fixed in 1.4.1 then mark it as 1.4.1. | * write a bugreporting HOWTO that defines what fields are mandatory and |how to choose between all those version, platform, target etc. values. |Define how the status relates to the work schedule. I'd say that the reporter should only look at version and platform the rest is not his task. -- Lgb
Re: [Patch] SnippetConversion for previews and DocBook
On Monday 31 January 2005 20:58, Andreas Vox wrote: Just to simplify my work what are your doubts regarding the docbook part? Options: a) using entities for filenames or not (cf. graphicsinset) Whatever is more convenient. The option for entities was due to the need to create relative paths in the exported docbook. The latex backend uses the [EMAIL PROTECTED] trick and we use the external entities... b) putting image files in a subdirectory or not, what name to use for the subdirectory math-images (?!) ;-) c) How to align math bitmaps vertically. It's no problem to get ascent/descent from preview.sty, but how to code it in XML? Docbook defines valign=(top|center|bottom) which is not good enough, XHTML apparently also knows valign=-7px What do others use? d) What file formats should we produce? All, just PNG, just EPS or PNG+EPS ? I think that we can play here the same tricks as we do with latex. But to be simple I would say both, and not passing the extension (since some stylesheets take care of this). The other option would be to declare the different formats... e) Should we use Chris' !ENTITY % output.print.png IGNORE everywhere, just SGML or not at all? Just SGML. It is valid so why not to use it. f) Are these decisions the same for SGML and XML? Mostly, I would expect. g) What density or magnification should be used for maths? (Not knowing the final font size) Me neither. :-) My ideas: a) Do it consistently, maybe drop the entities if noone protests Now you know the problems. You don't want to have absolute paths in the exported code, it is ugly and ugh.. no portable. :-) b) Yes, something like myFile_images/ That is fair. c) Produce illegal valign attributes which can be used directly for XHTML I will close my eyes here. ;-) d) EPS + PNG, let other tools do the rest I agree. e) Only for EPS + PNG Ok. f) Yes I agree. g) No idea. That's the advantage of EPS images, they are scalable... I agree also. PS: Have you seen that it is possible for docbook 5.0 to be release without a dtd? More and more xml is becoming the default. Haven't looked at DB 5.0 yet and don't understand your statement. There will be _no_ DTD for DB 5.0? Something instead, like schema or relax NG? A Relax NG and from there the DTD will be derived. (If I understood correctly). Ciao Ciao. /Andreas -- Jos Ablio
Re: What are the main problems in CVS now?
On Thursday 10 February 2005 15:42, Andreas Vox wrote: Note that nothing that needs a format change will be accepted after 1.4.0. So be sure that you plan ahead. No file format change is needed. Just want to polish, not to re-forge :-) It's mainly the bitmap generation for equations, some tweeks to output_docbook() and improvement of the db layout files. Maybe enable the db classes even if no sgmltools or equivalent is found (output SGML/XML still works, and you can use the other classes without TeX, no?) It makes sense. We would then gray out the corresponding entries in the menus. The code shouldn't be too difficult. :-) Ciao /Andreas -- José Abílio
Re: What are the main problems in CVS now?
Bennett Helm [EMAIL PROTECTED] writes: Is it possible to include all of these in the preference file? -- Simply entering /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin: /sw/bin doesn't seem to do it. Why? I just tested adding a non-existing directory to my path_prefix and LyX still works. OTOH it might be that 1.3.6 runs configure _before_ it reads the preferences file :-( Can you check with lyx -dbg init? Ciao /Andreas
Re: Bug: Flickering
Fedora Core 3 with a Gnome desktop (why haven't I switched yet is a long story) and the RPM I got is from the site below (direct link included), using apt for RPM. http://dag.wieers.com/ http://apt.sw.be/fedora/3/en/i386/RPMS.dag/lyx-1.3.5-1.1.fc3.rf.i386.rpm None of my other applications flicker like this. Any chance you can test that binaries in that RPM, to confirm whether or not it is those specific binaries? If I get time, I will try to make my own LyX binaries, but if it still flickers, then either I am making it incorrectly or there is something wrong with another Fedora component (it wouldn't be the first time, trust me). Are you sure that you get no flickering whatsoever? I tried turning off instant preview, but it made no difference. To reproduce, simply make a large multipage document, run your desktop in a high resolution of at least 1280x960, maximize the LyX window, and use the scroll bar to scroll. Flickering is harder to notice with a very small Window. Also, I swear LyX flickers in Debian testing too. Of course, I haven't used Debian testing since last summer, so my memory of it isn't all that good. LyX is still perfectly functional and very useful in spite of the flickering, but it just looks really bad. On Thu, 2005-02-10 at 14:17 +0100, Jean-Marc Lasgouttes wrote: Luke == Luke Simon [EMAIL PROTECTED] writes: Luke The main editor pane of Lyx flickers when scrolling up or down Luke using the scrollbar. It really destroys the visual polish of Luke this great application. I do not see this... What OS/computer are you using? JMarc
Re: Bug: Flickering
On Thursday 10 February 2005 16:13, Luke Simon wrote: Fedora Core 3 with a Gnome desktop (why haven't I switched yet is a long story) and the RPM I got is from the site below (direct link included), using apt for RPM. http://dag.wieers.com/ http://apt.sw.be/fedora/3/en/i386/RPMS.dag/lyx-1.3.5-1.1.fc3.rf.i386.rpm The only difference from my setup is that I'm running KDE, and the screen resolution is 1600*1200, but I have never seen what you report... -- Jos Ablio
Re: [Patch] SnippetConversion for previews and DocBook
Jose' Matos [EMAIL PROTECTED] writes: c) How to align math bitmaps vertically. It's no problem to get ascent/descent from preview.sty, but how to code it in XML? Docbook defines valign=(top|center|bottom) which is not good enough, XHTML apparently also knows valign=-7px What do others use? What others? ... g) What density or magnification should be used for maths? (Not knowing the final font size) Me neither. c) Produce illegal valign attributes which can be used directly for XHTML I will close my eyes here. I did some research. It's in the semantics for CSS3.lines. CSS2 and CSS1 support valign without length or percentage values (which is not better than the default) So, now I think we could declare %local.common.attr to include style for all elements and use the CSS3 syntaxsemantics. For PNG: style=valign: -7px For EPS: style=valign: -5% I don't think there are any solutions yet which align inline math bitmaps properly for DocBook. If you know any, please let me know. g) No idea. That's the advantage of EPS images, they are scalable... I agree also. Let's ask Chris... PS: Have you seen that it is possible for docbook 5.0 to be release without a dtd? More and more xml is becoming the default. I had a look now. LyX support for db5 will need a major rewrite, I think :-) BTW, I have to more questions: 1. Are there any CSS stylesheets for Docbook XML? I could only find ones for XHTML. 2. I think you were the last to work on docbook.layout co. Couldn't we add environments for admonitions etc quite easily? Also I think I spotted one or two typos/mistakes related to the inclusion of counters. Ciao /Andreas
Re: [Patch] SnippetConversion for previews and DocBook
On Thursday 10 February 2005 16:35, Andreas Vox wrote: enough, XHTML apparently also knows valign=-7px What do others use? What others? db2latex g) What density or magnification should be used for maths? (Not knowing the final font size) Me neither. c) Produce illegal valign attributes which can be used directly for XHTML I will close my eyes here. There is an ;-) missing here. :-) I did some research. It's in the semantics for CSS3.lines. CSS2 and CSS1 support valign without length or percentage values (which is not better than the default) The problem as usual, it that there aren't many browsers who support the complete specification of css3, and probably some of them have bugs (hint: exploder). Been there, done that. So, now I think we could declare %local.common.attr to include style for all elements and use the CSS3 syntaxsemantics. For PNG: style=valign: -7px For EPS: style=valign: -5% I think that it is not good style to mix relative with absolute measures, but then this is just an aesthetic point, so please ignore it. ;-) I don't think there are any solutions yet which align inline math bitmaps properly for DocBook. If you know any, please let me know. Don't know either. g) No idea. That's the advantage of EPS images, they are scalable... I agree also. Let's ask Chris... OK. PS: Have you seen that it is possible for docbook 5.0 to be release without a dtd? More and more xml is becoming the default. I had a look now. LyX support for db5 will need a major rewrite, I think :-) Less than what you could expect. :-) BTW, I have to more questions: 1. Are there any CSS stylesheets for Docbook XML? I could only find ones for XHTML. I have seen some quest recently for CSS stylesheets, I don't remember where and the final result though. 2. I think you were the last to work on docbook.layout co. Couldn't we add environments for admonitions etc quite easily? Also I think I spotted one or two typos/mistakes related to the inclusion of counters. Certainly, the basics are there. :-) Also with char style support for 1.4 a lot more are possible now. Ciao /Andreas -- José Abílio
Re: What are the main problems in CVS now?
On Feb 10, 2005, at 10:59 AM, Andreas Vox wrote: Bennett Helm [EMAIL PROTECTED] writes: Is it possible to include all of these in the preference file? -- Simply entering /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/ bin: /sw/bin doesn't seem to do it. Why? I just tested adding a non-existing directory to my path_prefix and LyX still works. OTOH it might be that 1.3.6 runs configure _before_ it reads the preferences file :-( Can you check with lyx -dbg init? As far as I can tell, nothing I enter into PATH prefix has any effect. Also, as my other e-mail today indicates (Problems with PATH for lyx-13x on MacOS X), the problem seems to be more general than reading the preferences file and the configure script: it looks as though /usr/bin, /usr/local/bin, etc. are not a part of PATH when LyX is run. Bennett
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 03:51:56PM +0100, Lars Gullik Bj?nnes wrote: We have some 250 open bugs, but no idea if they exist in 1.3.x or in HEAD. We need to be able to mark the bugs so that we know what to work on. If there's not marked with 'fixedintrunk', then they're probably still there... john
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 04:24:07PM +0100, Jean-Marc Lasgouttes wrote: A possibility is to search for bugs reported against 1.4.0cvs. I used to try mark regressions with 'regression'. Whilst I don't have time to re-learn all the internals of LyX, I can certainly try to do some triage... Suffice to say there are LOTS of significant problems. john
Re: What are the main problems in CVS now?
Am Donnerstag, 10. Februar 2005 16:32 schrieb Juergen Spitzmueller: quite a bunch of them are fixedintrunk. I think we should resolve these bugs to avoid mistakes like this. Either as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as FIXED. Georg
Re: [Patch] SnippetConversion for previews and DocBook
Jose' Matos [EMAIL PROTECTED] writes:
On Thursday 10 February 2005 16:35, Andreas Vox wrote:
enough, XHTML apparently also knows valign=-7px
What do others use?
What others?
db2latex
Nothing. If it finds an ALT elem with tex code, it puts that in
\ensuremath or \begin/end{displaymath};
if there is a mediaobject it gets displayed without alignment
and otherwise the ALT text is copied verbatim.
c) Produce illegal valign attributes which can be used directly for
XHTML
I will close my eyes here.
There is an missing here.
GMane versteht keinen Spa ;-)
I did some research. It's in the semantics for CSS3.lines. CSS2 and
CSS1 support valign without length or percentage values (which is not
better than the default)
The problem as usual, it that there aren't many browsers who support the
complete specification of css3, and probably some of them have bugs (hint:
exploder). Been there, done that.
Hah! You think I think any browser will support that properly? :-P
I just want to find a way to pass the information to the XML file without
breaking too many standards. How any stylesheets interpret this is up to
them.
So, now I think we could declare %local.common.attr to include style
for all elements and use the CSS3 syntaxsemantics.
For PNG: style=valign: -7px
For EPS: style=valign: -5%
I think that it is not good style to mix relative with absolute measures,
but then this is just an aesthetic point, so please ignore it.
I think you are right here. We should use the absolute Postscript points from
the bounding box.
...
BTW, I have to more questions:
1. Are there any CSS stylesheets for Docbook XML? I could only find ones
for XHTML.
I have seen some quest recently for CSS stylesheets, I don't remember
where and the final result though.
Please tell me if you find it again!
Ciao
/Andreas
[patch] bug 1598
http://bugzilla.lyx.org/show_bug.cgi?id=1598 With the following patch (calling cur.normalize() in LFUN_UP and LFUN_DOWN of math_nestinset), I cannot reproduce the crash anymore. The problem is clearly that cur.idx() and cur.pos() need update after an empty scriptinset has been removed. I am not sure, however, if this is the best solution (although I obviously didn't find a better one). André, please have a look. Regards, Jürgen Index: math_nestinset.C === RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_nestinset.C,v retrieving revision 1.144 diff -u -r1.144 math_nestinset.C --- math_nestinset.C 31 Jan 2005 16:29:48 - 1.144 +++ math_nestinset.C 10 Feb 2005 18:02:40 - @@ -509,6 +509,8 @@ cur.selHandle(cmd.action == LFUN_UPSEL); if (!cur.up()) cmd = FuncRequest(LFUN_FINISHED_UP); + // fixes bug 1598. Please check! + cur.normalize(); break; case LFUN_DOWNSEL: @@ -516,6 +518,8 @@ cur.selHandle(cmd.action == LFUN_DOWNSEL); if (!cur.down()) cmd = FuncRequest(LFUN_FINISHED_DOWN); + // fixes bug 1598. Please check! + cur.normalize(); break; case LFUN_MOUSE_DOUBLE:
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 06:12:06PM +0100, Georg Baum wrote: I think we should resolve these bugs to avoid mistakes like this. Either as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as FIXED. I don't think we should mark fixed bugs as WONTFIX, that's just too unclear. But I don't know of a decent way to search for 1.4-fixed bugs that are still in 1.3.x otherwise... john
Re: What are the main problems in CVS now?
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not sure it is going to get used. For 1.3.0 we had Michael's bug list which was very useful. And this Michael is still alive and waits for a sign to start testing now that LyX can be used on the Windows platform... :-) Michael
Re: What are the main problems in CVS now?
I think we can ship 1.4 with change tracking. The status is not worse (even a bit better) than the unofficial 1.3 version that has been distributed separately, and AFAIK people have used that for their daily work. I would also like to see change tracking in LyX 1.4. Actually, this feature alone would justify increasing the version number from 1.3 straight to 2.0! What I am most concerned about is: Will there be any fundamental code changes right after the release of LyX 1.4? Or in other words: Can we guarantee that the remaining open bugs can be fixed (easily) in the stable 1.4.X branch? Maybe Alfredo and Andre can share their feelings about this issue with us...? Regards, Michael
Re: [Patch] SnippetConversion for previews and DocBook
Am Donnerstag, 10. Februar 2005 16:55 schrieb Jose' Matos: My ideas: a) Do it consistently, maybe drop the entities if noone protests Now you know the problems. You don't want to have absolute paths in the exported code, it is ugly and ugh.. no portable. :-) We tried hard to preserve the absoluteness of filenames for the LaTeX backend, because users may have reasons to use absolute paths or relative ones. The docbook backend should behave the same IMO. Georg
Re: What are the main problems in CVS now?
Am Donnerstag, 10. Februar 2005 13:06 schrieb Lars Gullik Bjønnes:
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
I have some changes to tex2lyx that are basically finished but need some
testing that I would like to see in 1.4. They enable tex2lyx to parse
table column definitions with b{}, p{}, m{}, {}, *{}, @{} and !{}.
Especially @{} and !{} are important IMO. There are still some table
features missing, but these fixes ensure that the number of columns is
parsed correctly. I believe that tex2lyx is then better than reLyX in 99%
of the cases.
(and bugzilla is not up to snuff...)
I'd like all code-cleanup, feature-fixing etc to stop now and go into
hard freeze and only fix regressions and crashes.
But the math table fixes by Martin and me are ok with you (since already
done)? My problem is that I am not able to do Alfredo stuff (or at
least it requires a lot of time to understand the concepts).
Georg
[patch] fix inInset crash
Wether we'll get rid of this or not, this fixes a crash in the meantime.
Committing now.
Georg
diff -p -r -U 3 -X excl.tmp lyx-1.4-clean/src/ChangeLog lyx-1.4-cvs/src/ChangeLog
--- lyx-1.4-clean/src/ChangeLog 2005-02-09 21:02:13.0 +0100
+++ lyx-1.4-cvs/src/ChangeLog 2005-02-09 21:10:45.0 +0100
@@ -1,3 +1,7 @@
+2005-02-10 Georg Baum [EMAIL PROTECTED]
+
+ * text2.C (setCounter): check for inInset() == 0
+
2005-02-09 Jean-Marc Lasgouttes [EMAIL PROTECTED]
* BufferView_pimpl.C (dispatch): handle LFUN_GOTO_PARAGRAPH here,
diff -p -r -U 3 -X excl.tmp lyx-1.4-clean/src/text2.C lyx-1.4-cvs/src/text2.C
--- lyx-1.4-clean/src/text2.C 2005-02-08 20:28:44.0 +0100
+++ lyx-1.4-cvs/src/text2.C 2005-02-10 21:06:28.0 +0100
@@ -791,8 +793,9 @@ void LyXText::setCounter(Buffer const
bool isOK = false;
while (tmppit != end) {
in = pars_[tmppit].inInset();
-if (in-lyxCode() == InsetBase::FLOAT_CODE ||
-in-lyxCode() == InsetBase::WRAP_CODE) {
+if (in
+(in-lyxCode() == InsetBase::FLOAT_CODE ||
+ in-lyxCode() == InsetBase::WRAP_CODE)) {
isOK = true;
break;
}
Re: What are the main problems in CVS now?
Michael == Michael Schmitt [EMAIL PROTECTED] writes: Michael What I am most concerned about is: Will there be any Michael fundamental code changes right after the release of LyX 1.4? Michael Or in other words: Can we guarantee that the remaining open Michael bugs can be fixed (easily) in the stable 1.4.X branch? Maybe Michael Alfredo and Andre can share their feelings about this issue Michael with us...? We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I hope this still holds... JMarc
Re: What are the main problems in CVS now?
Michael == Michael Schmitt [EMAIL PROTECTED] writes: OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not sure it is going to get used. For 1.3.0 we had Michael's bug list which was very useful. Michael And this Michael is still alive and waits for a sign to start Michael testing now that LyX can be used on the Windows platform... Michael :-) You mean you are alive _and_ you have time to help on LyX? Excellent ! JMarc
Re: [patch] fix inInset crash
Georg Baum wrote: Wether we'll get rid of this or not, this fixes a crash in the meantime. Committing now. Note that this breaks the display of caption labels _inside_ floats! Regards, Jürgen
[patch] fix qref dialog
It was not possible to insert a reference when there was only one label
(because the refSelected slot immediately closed the dialog without applying
the selected entry; this was only possible with refHighlighted, which only
works with more than one entry).
The fix is crystal clear, so I gonna commit this now.
Jürgen
? ui/IndexModuleBase.ui
Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/qt2/ChangeLog,v
retrieving revision 1.756
diff -u -r1.756 ChangeLog
--- ChangeLog 31 Jan 2005 15:26:39 - 1.756
+++ ChangeLog 10 Feb 2005 21:39:59 -
@@ -1,3 +1,9 @@
+2005-02-10 Jrgen Spitzmller [EMAIL PROTECTED]
+
+ * QRefDialog.C (refSelected): insert selected ref to
+ text widget (this was not possible if there was only
+ one entry, an empty inset was generated).
+
2005-01-31 Asger Ottar Alstrup [EMAIL PROTECTED]
* QDialogView.h (form): add cast for MSVC.
Index: QRefDialog.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/qt2/QRefDialog.C,v
retrieving revision 1.17
diff -u -r1.17 QRefDialog.C
--- QRefDialog.C 2 Jun 2004 20:13:18 - 1.17
+++ QRefDialog.C 10 Feb 2005 21:40:00 -
@@ -70,8 +70,12 @@
}
-void QRefDialog::refSelected(const QString )
+void QRefDialog::refSelected(const QString sel)
{
+ if (form_-readOnly())
+ return;
+
+ referenceED-setText(sel);
// enter or double click, inserts ref and closes dialog
form_-slotOK();
}
Bug 1790: crashes due to pseudo-multithreading
Hi all! I did some research about the crash in handleCompletedProcesses(); see Bugzilla for complete results. I think the culprit is the call to sync_events() in LyXView::showCursor(). The comment says that it is needed for hiding the cursor correctly, but I commented this line out and I couldn't see any difference, except that there were no crashes any more. John? /Andreas
Bugzilla help!
I can't do anything with Bugzilla because of this: 00:44:05.548897 lambent.51199 aussie.lyx.org.http: P 1449:2567(1118) ack 1 win 46 nop,nop,timestamp 3916868232 926092508 (DF) 00:44:05.684180 knoll.linpro.no lambent: icmp: aussie.lyx.org unreachable - need to frag (mtu 1496) 00:44:05.684335 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916868368 926092508 (DF) 00:44:05.965938 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916868650 926092508 (DF) 00:44:06.529858 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916869214 926092508 (DF) 00:44:07.657677 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916870342 926092508 (DF) 00:44:09.913352 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916872598 926092508 (DF) 00:44:14.424638 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916877110 926092508 (DF) 00:44:23.447274 lambent.51199 aussie.lyx.org.http: . 1:1445(1444) ack 1 win 46 nop,nop,timestamp 3916886134 926092508 (DF) The first bit looks like normal MTU discovery, but then I don't hear anything back again! Anybody else? Very occassionally bugzilla responds OK, but most of the time it's unusable. I don't have these problems on any other site (including lyx ones), nor any other bugzilla. Lars, any ideas? john
Re: Bug 1790: crashes due to pseudo-multithreading
On Fri, Feb 11, 2005 at 12:56:26AM +0100, Andreas Vox wrote: I think the culprit is the call to sync_events() in LyXView::showCursor(). The comment says that it is needed for hiding the cursor correctly, but I commented this line out and I couldn't see any difference, except that there were no crashes any more. John? The core has changed so much that that comment might well be irrelevant. Please check overlapping windows with your WM, and flickling back and forward with a blinking LyX cursor, using Page up/down etc. I did a *lot* of work to fix cursor drawing, so it would be a shame if it broke again. john
[patch] Bug 1119: race condition in Dialogs::show()
Hi all! I added some debug output at the start and end of the Dialogs::show() method. This is what I got before, with the testfile from the bugreport: Dialogs::show(citation Dialogs::show(citation Dialogs::show(citation Dialogs::show citation) Dialogs::show citation) Dialogs::show citation) Dialogs::show(citation CRASH The attached patch just ignores subsequent calls to show if the old one isn't finished yet. As long as we stay single-threaded the logic should be save. Output after: Dialogs::show(citation - 0 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show(citation - 1 Dialogs::show citation) Dialogs::show(citation - 0 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show(citation - 1 Dialogs::show citation) ... and no crash :-) Cheers /Andreas dialog-sync.diff Description: Binary data
Some bugs
Since I can't access bugzilla. I only tried for about 10 minutes so please don't think this is exhaustive. On the whole, the current CVS isn't too bad. A couple of bad assertions, but after a few of these are fixed, I think we can let Michael S loose. Massive improvement on last time... what have you lot been doing? :) 1. crash by new doc, insert comment, then repeatedly click on the button to open and close the inset, until you get: Assertion triggered in void LyXText::dispatch(LCursor, FuncRequest) by failing check cur.text() == this in file text3.C:361 2. the cursor is placed outside inset's red boundaries, this looks very confusing. I think we need to add a buffer to inset's dimensions 3. Button insets are still not centred. I think someone closed this bug. It needs re-opening. 4. control-X on selected text in a table cell cuts the whole cell instead of just the selection 5. Any text cut from a table cell is gone forever 6. I have to click exactly in the middle of an empty table to cell in order to place the cursor there. 7. selection progression in table cells is broken. After selecting all text in a cell, another 'Right' should select the cell itself, and only then the next cell to the right. There's no way to select a table cell with the keyboard right now. 8. (usability issue) - minipage is just way too hard to find. We might consider a submenu for 'Box' that has Minipage, Parbox, Framed Box etc. 9. A new ERT inset has a width of zero, this is near impossible to use. 10. Pasting a paragraph about 50 times (lots of control-Vs) gives: Assertion triggered in Point::Point(int, int) by failing check y -3000 in file coordcache.h:27 During this, the scrollbar is completely wrong. 11. Creating a new figure float, the 'Figure #:' of the caption is only seen on pressing return 12. Lars's on-screen translated things like 'Part' etc. are broken. I get 'Teil' in the DVI and not on screen. 13. Undo is missing out lots of edits. Try entering 1,2,3,4 in a table (one on each row of the table) then try to undo them. Generally broken in fact. 14. The footnote in the User Guide (first one) is inheriting the font from its containing paragraph. Not good ... 15. Right Address is (predictably enough) broken john
Re: [patch] Bug 1119: race condition in Dialogs::show()
On Fri, Feb 11, 2005 at 01:55:34AM +0100, Andreas Vox wrote: The attached patch just ignores subsequent calls to show if the old one isn't finished yet. I think this is pretty much the right thing to do. In the general sense we can be half-initialised during show, so if we enter the event loop for whatever reason we can be screwed. Note that we do this in Qt via the -processEvents() in QDialogView.h (and we need to do this to ensure updating the dialog doesn't screw up our button controller) So, I'm OK with this patch, at least. regards john
Re: Problem writing a converter
On Thu, 2005-02-10 at 13:03 +0100, Georg Baum wrote:
Maybe. Maybe it is also a good idea to use $$p for converters, but we need
to know why the converter needs that flag in order to decide that.
O.K. Let me explain what I am doing. I use Lilypond to typeset music.
It is a program that turns lilypond source code into LaTeX code which is
then run through LaTeX to generate the typeset music. It generates
extremely high quality output but access to normal LaTeX functionality
is extremely limited. So for instance if you can't generate things like
contents pages. A _very_ _simple_ Lilypond score song.ly for a Song
might look like:
+ .. +
+ \include voicepart.ly +
+ .. +
+ \include pianopart.ly +
+ .. +
+ \include lyrics.txt+
+ .. +
+ .. +
song.ly
One reason for structuring it like this, apart form keeping myself sane,
is that I can then extract the piano part or the voice part
independently.
In order to avail yourself of full LaTeX functionality, Lilypond comes
with a utility called lilypond-book that (among other things) allows you
to put Lilypond code inside a LaTeX document.
The Lilypond manual says:
=== start of quote =
For LaTeX, music is entered using
\begin[options,go,here]{lilypond}
YOUR LILYPOND CODE
\end{lilypond}
\lilypondfile[options,go,here]{filename}
or
\lilypond{ YOUR LILYPOND CODE }
Running lilypond-book yields a file that can be processed with LaTeX.
= end of quote =
It is possible to use \begin -- \end {lilypond} or \lilypond within ERT,
and it works but is only suitable if you have a couple of bars of music.
So if I were putting my song in a LyX document I would use:
\lilypondfile{path to song.ly}
I don't want to use an absolute path because I work on this stuff on
more than one computer and use CVS. I also sometimes check it out into a
different directory when I want to see what changes are needed for a new
version of Lilypond. A book on music might reference 80 or 90 Lilypond
scores I would not want to change them all just because I had checked it
out in a different directory!
When I first started doing this I would export the LyX file to LaTeX and
then run lilypond-book and dvips by hand. But this is an awful pain
especially if you make a lot of small changes and want to look at the
results after every one. Using a converter makes much more sense because
it allows you to generate the postscript from within LyX. Unfortunately
copying the LyX file to a temporary file messes up all the references.
Copying the Lilypond file doesn't solve the problem because to do this I
would need a song-wrapper.ly in the same directory as the LyX file,
but song-wrapper.ly would have to reference song.ly using an absolute
path.
My present solution is that I have a script exports an environmental
variable MYDIR=`pwd` and then calls LyX. This variable is then picked up
by the converter. But of course converter will only work for LyX files
in one directory so I might need several instances of LyX running! If
LyX passed the directory of the LyX file as a parameter it would make
life much easier for me! But it would also mean that anyone else who
wanted the converter could use it without hassle.
Thanks,
Bernard
Re: [PATCH] UI: matrix partitioning
Martin Vermeer wrote:
> If I may summarize what I think it _should_ do:
>
> 1) If you want to swap two rows, make sure you're not on the last row.
No. If you are on the last row, it is swapped with the second to last one.
This is consistent with the tabular inset, so we should not change it.
> 2) If you want to swap two columns, make sure you're not in the
> rightmost column.
Same as above.
> 3) If you want to delete a horizontal or vertical line, make sure there
> is one (or more) in the place (above row, left to column) to delete.
> (adding or deleting rows or columns is always possible, so no conditions
> there; right?)
No. Adding is always possible, but the code depends on the fact that we have
at least one row and one column.
> Disable if any of these conditions is violated, otherwise enable. All
> three require cursor (cur) and rowinfo_/colinfo_ knowledge... but we
> have that in getStatus, don't we?
Yes.
> (Item 3 is optional; a silent fail is unelegant, however. Strictly
> speaking all three are optional if one accepts silent failure)
It is not optional IMO.
In the meantime I had a look at vlines to the right and hlines at the
bottom. It turned out that both are already supported: MathGridInset stores
a dummy row and dummy column for this purpose. There were only two little
bugs:
1. The rightmost '|' was not handled correctly in MathGridInset::halign()
2. The following code
\begin{array}{|c|c|}
\hline
1 & 2 \\ \hline
3 & 4 \\ \hline
\end{array}
produced one additional empty row because of the last '\\'. I changed the
math parser to delete this line and implemented one FIXME as a side effect.
It would be nice if you could merge the attached patch with yours and commit
it, because I don't have time to work on that right now.
GeorgIndex: lib//ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.672
diff -u -p -r1.672 ChangeLog
--- lib//ChangeLog 9 Feb 2005 18:56:00 - 1.672
+++ lib//ChangeLog 10 Feb 2005 08:16:19 -
@@ -1,3 +1,8 @@
+2005-02-10 Georg Baum <[EMAIL PROTECTED]>
+
+ * ui/stdmenus.ui: add more facilities for drawing/deleting partition
+ lines in matrix
+
2005-02-09 Martin Vermeer <[EMAIL PROTECTED]>
* ui/stdmenus.ui: add facilities for drawing/deleting partition
Index: lib//ui/stdmenus.ui
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ui/stdmenus.ui,v
retrieving revision 1.40
diff -u -p -r1.40 stdmenus.ui
--- lib//ui/stdmenus.ui 9 Feb 2005 18:56:01 - 1.40
+++ lib//ui/stdmenus.ui 10 Feb 2005 08:16:21 -
@@ -159,14 +159,18 @@ Menuset
Item "Copy Row" "tabular-feature copy-row"
Item "Swap Rows" "tabular-feature swap-row"
Item "Add Line Above" "tabular-feature add-hline-above"
+ Item "Add Line Below" "tabular-feature add-hline-below"
Item "Delete Line Above" "tabular-feature delete-hline-above"
+ Item "Delete Line Below" "tabular-feature delete-hline-below"
Separator
Item "Add Column|C" "tabular-feature append-column"
Item "Delete Column|e" "tabular-feature delete-column"
Item "Copy Column" "tabular-feature copy-column"
Item "Swap Columns" "tabular-feature swap-column"
Item "Add Line to Left" "tabular-feature add-vline-left"
+ Item "Add Line to Right" "tabular-feature add-vline-right"
Item "Delete Line to Left" "tabular-feature delete-vline-left"
+ Item "Delete Line to Right" "tabular-feature delete-vline-right"
End
Menu "edit_math_limits"
? src/mathed/math_intertextinset.C
? src/mathed/math_intertextinset.h
Index: src/mathed/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.470
diff -u -p -r1.470 ChangeLog
--- src/mathed/ChangeLog 9 Feb 2005 18:56:00 - 1.470
+++ src/mathed/ChangeLog 10 Feb 2005 08:18:16 -
@@ -1,4 +1,15 @@
-<<< ChangeLog
+2005-02-10 Georg Baum <[EMAIL PROTECTED]>
+
+ * math_gridinset.C (halign): fix '|' to the right of the last column
+ * math_gridinset.[Ch]: remove unused leftline_ and rightline_
+ * math_gridinset.C: add more facilities for adding/deleting
+ partition lines in matrix.
+ * math_gridinset.C (getStatus): implement missing LFUN_TABULAR_FEATURE
+ * math_parser.C (delEmptyLastRow): new
+ * math_parser.C (parse1): Store active environment and use it to
+ detect nonmatching \end{} and removing superflous rows with
+ delEmptyLastRow()
+
2005-02-09 Martin Vermeer <[EMAIL PROTECTED]>
* math_gridinset.[hC]: add facilities for drawing/deleting partition
Index: src/mathed/math_gridinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_gridinset.C,v
retrieving revision 1.155
diff -u -p -r1.155 math_gridinset.C
--- src/mathed/math_gridinset.C 9 Feb 2005 18:56:00 - 1.155
+++ src/mathed/math_gridinset.C 10
update
hi there, sorry, i'm completely new in lyx. how can i update from 1.3.3 to 1.3.4?? i downloaded everything but what shall i do then? what do i have to to with this .tar files and patches? is there any update program? greets trinae -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
Re: [PATCH] UI: matrix partitioning
On Thu, 2005-02-10 at 10:34, Georg Baum wrote:
> Martin Vermeer wrote:
...
> It would be nice if you could merge the attached patch with yours and commit
> it, because I don't have time to work on that right now.
OK.
What does this do? I don't get it.
if (!lyx::support::contains("tcb", cmd.argument[0])) {
flag.enable(false);
break;
}
flag.setOnOff(cmd.argument[0] == v_align_);
> Georg
- Martin
signature.asc
Description: This is a digitally signed message part
Re: Problem writing a converter
Bernard Hurley <[EMAIL PROTECTED]> writes: > > On Sun, 2005-02-06 at 11:38 +0100, Georg Baum wrote: ... > > Sorry, I forgot that such a parameter exists already: $$p > > > > I can't get this to work! The value p is passed to the converter > where is the PID of the shell that calls the converter. I checked the code in 140cvs and it looks as if this parameter does not get used (any more?). I think the official way to solve your problem is to use a "copier". That's like a converter but copies a file from one dir to another, translating references to external files on the way. See "scripts/fig_copy.sh" for an example. Would this be possible for your problem or do you need the real original directory? Ciao /Andreas
Re: update
> "Felix" == Felix Sager <[EMAIL PROTECTED]> writes: Felix> hi there, sorry, i'm completely new in lyx. Felix> how can i update from 1.3.3 to 1.3.4?? Felix> i downloaded everything but what shall i do then? what do i Felix> have to to with this .tar files and patches? is there any Felix> update program? What is the operating system you use? JMarc
Re: [patch] fix frameless box -> parbox conversion in lyx2lyx
On Monday 07 February 2005 11:39, Jean-Marc Lasgouttes wrote: > > This is not really for 1.3, since it is due to problems with the use > of tex2lyx with newish features like parbox. We don't distribute > tex2lyx with 1.3.x anyway. True. > OTOH, I guess the lyx2lyx which is now on HEAD will be distributed > with lyx 1.3.6 (or another one) anyway, so this code matters. True. Also this fixes a real bug. > I'll follow Jose's judgment on this. As far as can see this seems to fix a real bug so I will trust Georg judgment on this. I understood Georg's argument but I didn't tried the patch. :-) I consider the retroversion as a fall back scheme, and if we can make it work better yet. :-) > JMarc -- José Abílio
Re: Problem writing a converter
Andreas Vox wrote: > Bernard Hurley <[EMAIL PROTECTED]> writes: > >> I can't get this to work! The value p is passed to the converter >> where is the PID of the shell that calls the converter. Sorry again. This is only available for viewing, not for converting. > I checked the code in 140cvs and it looks as if this parameter does > not get used (any more?). Indeed. I don't know why. But Bernard uses 1.3, so this won't help. > I think the official way to solve your problem is to use a "copier". > That's like a converter but copies a file from one dir to another, > translating references to external files on the way. > See "scripts/fig_copy.sh" for an example. Maybe. Maybe it is also a good idea to use $$p for converters, but we need to know why the converter needs that flag in order to decide that. Georg
What are the main problems in CVS now?
It might be that I am a bit "out". But I see no bug problems in CVS currently. What must be fixed for 1.4.0? (and bugzilla is not up to snuff...) I'd like all code-cleanup, feature-fixing etc to stop now and go into hard freeze and only fix regressions and crashes. -- Lgb
Re: [patch] fix frameless box -> parbox conversion in lyx2lyx
Jose' Matos wrote: > As far as can see this seems to fix a real bug so I will trust Georg > judgment on this. I understood Georg's argument but I didn't tried the > patch. :-) Then I'll commit it. I did test it, and even if there is still a bug I am sure that it is not a principal problem. > I consider the retroversion as a fall back scheme, and if we can make it > work better yet. :-) I consider it quite important, because it makes it easy to try LyX 1.4 and switch back if necessary. Georg
Re: What are the main problems in CVS now?
Lars Gullik Bjønnes wrote: > It might be that I am a bit "out". > > But I see no bug problems in CVS currently. > What must be fixed for 1.4.0? > > (and bugzilla is not up to snuff...) I'd say the important ones are targeted for MILESTONE 1.4.0 (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset [e.g., when the document has a caption outside a float], which is not yet in bugzilla). Lots of Alfredo stuff, if you ask me. Jürgen
Re: What are the main problems in CVS now?
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes: > > It might be that I am a bit "out". > > But I see no bug problems in CVS currently. > What must be fixed for 1.4.0? Currently I have problems with crashes related to fast events and previews/forked processes. For example, when I start LyX, open the user guide and keep the DOWN ley pressed, I wont reach the end of the document: Date/Time: 2005-02-10 13:55:24 +0100 OS Version: 10.3.7 (Build 7S215) Report Version: 2 Command: lyx Path:/Applications/LyX.app/Contents/MacOS/lyx Version: ??? (???) PID: 21179 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0002 Thread 0 Crashed: 0 lyx 0x006a31cc 0x1000 + 0x6a21cc 1 lyx 0x000f3ea0 lyx::support::ForkedcallsContr oller::handleCompletedProcesses() + 0x2d0 (shared_count.hpp:378) 2 lyx 0x82cc BufferView::Pimpl::cursorToggle( ) + 0x40 (BufferView_pimpl.C:660) 3 lyx 0x0062ed50 0x1000 + 0x62dd50 4 lyx 0x00633d94 0x1000 + 0x632d94 5 lyx 0x006331d0 0x1000 + 0x6321d0 6 lyx 0x00631124 0x1000 + 0x630124 7 lyx 0x000e3428 Timeout::emit() + 0x68 (Timeo ut.C:52) 8 lyx 0x001d70b8 QObject::event(QEvent*) + 0xec (ControlCommandBuffer.C:137) 9 lyx 0x001c3dd0 QApplication::internalNotify(QO bject*, QEvent*) + 0x2fc (qt_helpers.C:205) ... I surmise that's another Qt-multithreading related bug. I have some local patches related to PreviewLoader and BufferView_pimpl. If noone else can reproduce this under LyX/Qt with preview on, I can try to reproduce it with a vanilla cvs version. Another impression I got is that the positioning during scrolling is not exact with previews on. For example, I can scroll up in a long document until the scrollbar is at the top, but the part of the document which is shown isn't even near the beginning. If I click into the buffer and use PAGEUP, I can reach the top of the docuemnt. What about my PreviewLoader refactoring and the bitmap production for Docbook equations? I could make a final patch pretty fast and it mostly only affects docbook. If you are dead against it, would it be possible to have a fast 1.4.1 version including these patches? In my view Docbook support is sub-standard right now. Ciao /Andreas
Re: What are the main problems in CVS now?
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> But I see no bug problems in CVS currently. What must be fixed Lars> for 1.4.0? Lars> I'd like all code-cleanup, feature-fixing etc to stop now and go Lars> into hard freeze and only fix regressions and crashes. One thing I see that may need big changes is that selecting with the mouse is terribly slow. Also, selection by double click is broken. We have to decide what to do about change tracking. We do not have a working bibinset. There are probably many other things, but that's all I remember from the top of my head. JMarc
Re: Bug: Flickering
> "Luke" == Luke Simon <[EMAIL PROTECTED]> writes: Luke> The main editor pane of Lyx flickers when scrolling up or down Luke> using the scrollbar. It really destroys the visual "polish" of Luke> this great application. I do not see this... What OS/computer are you using? JMarc
Re: [PATCH] UI: matrix partitioning
On Thu, 2005-02-10 at 10:34, Georg Baum wrote:
...
> It would be nice if you could merge the attached patch with yours and commit
> it, because I don't have time to work on that right now.
>
>
> Georg
Done. Result attached. Works.
- Martin
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.672
diff -u -r1.672 ChangeLog
--- lib/ChangeLog 9 Feb 2005 18:56:00 - 1.672
+++ lib/ChangeLog 10 Feb 2005 13:38:07 -
@@ -1,3 +1,12 @@
+2005-02-10 Georg Baum <[EMAIL PROTECTED]>
+
+ * ui/stdmenus.ui: add more facilities for drawing/deleting partition
+ lines in matrix
+
+2005-02-10 Martin Vermeer <[EMAIL PROTECTED]>
+
+ * bind/math.bind: provide key bindings for lines in matrix
+
2005-02-09 Martin Vermeer <[EMAIL PROTECTED]>
* ui/stdmenus.ui: add facilities for drawing/deleting partition
Index: src/mathed/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.470
diff -u -r1.470 ChangeLog
--- src/mathed/ChangeLog 9 Feb 2005 18:56:00 - 1.470
+++ src/mathed/ChangeLog 10 Feb 2005 13:38:08 -
@@ -1,4 +1,19 @@
-<<< ChangeLog
+2005-02-10 Georg Baum <[EMAIL PROTECTED]>
+
+ * math_gridinset.C (halign): fix '|' to the right of the last column
+ * math_gridinset.[Ch]: remove unused leftline_ and rightline_
+ * math_gridinset.C: add more facilities for adding/deleting
+ partition lines in matrix.
+ * math_gridinset.C (getStatus): implement missing LFUN_TABULAR_FEATURE
+ * math_parser.C (delEmptyLastRow): new
+ * math_parser.C (parse1): Store active environment and use it to
+ detect nonmatching \end{} and removing superflous rows with
+ delEmptyLastRow()
+
+2005-02-10 Martin Vermeer <[EMAIL PROTECTED]>
+
+ * math_gridinset.C: implement getStatus for tabular-features.
+
2005-02-09 Martin Vermeer <[EMAIL PROTECTED]>
* math_gridinset.[hC]: add facilities for drawing/deleting partition
Index: src/mathed/math_gridinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_gridinset.C,v
retrieving revision 1.155
diff -u -r1.155 math_gridinset.C
--- src/mathed/math_gridinset.C 9 Feb 2005 18:56:00 - 1.155
+++ src/mathed/math_gridinset.C 10 Feb 2005 13:38:08 -
@@ -22,6 +22,7 @@
#include "cursor.h"
#include "debug.h"
#include "funcrequest.h"
+#include "gettext.h"
#include "undo.h"
#include "frontends/Painter.h"
@@ -124,7 +125,7 @@
MathGridInset::ColInfo::ColInfo()
- : align_('c'), leftline_(false), rightline_(false), lines_(0)
+ : align_('c'), lines_(0)
{}
@@ -215,11 +216,12 @@
{
col_type col = 0;
for (string::const_iterator it = hh.begin(); it != hh.end(); ++it) {
- if (col >= ncols())
- break;
char c = *it;
if (c == '|') {
colinfo_[col].lines_++;
+ } else if (col >= ncols()) {
+ // Only '|' is allowed in the last dummy column
+ break;
} else if (c == 'c' || c == 'l' || c == 'r') {
colinfo_[col].align_ = c;
++col;
@@ -1102,8 +1104,12 @@
swapRow(cur.row());
else if (s == "add-hline-above")
rowinfo_[cur.row()].lines_++;
+ else if (s == "add-hline-below")
+ rowinfo_[cur.row()+1].lines_++;
else if (s == "delete-hline-above")
- rowinfo_[cur.row()].lines_ = 0;
+ rowinfo_[cur.row()].lines_--;
+ else if (s == "delete-hline-below")
+ rowinfo_[cur.row()+1].lines_--;
else if (s == "append-column")
for (int i = 0, n = extractInt(is); i < n; ++i) {
row_type r = cur.row();
@@ -1125,9 +1131,13 @@
else if (s == "swap-column")
swapCol(col(cur.idx()));
else if (s == "add-vline-left")
- colinfo_[col(cur.idx())].lines_++;
+ colinfo_[col(cur.idx())].lines_++;
+ else if (s == "add-vline-right")
+ colinfo_[col(cur.idx())+1].lines_++;
else if (s == "delete-vline-left")
- colinfo_[col(cur.idx())].lines_ = 0;
+ colinfo_[col(cur.idx())].lines_--;
+ else if (s == "delete-vline-right")
+ colinfo_[col(cur.idx())+1].lines_--;
else {
cur.undispatched();
break;
@@ -1223,25 +1233,41 @@
{
bool ret = true;
switch (cmd.action) {
- case LFUN_TABULAR_FEATURE:
-#if 0
- // should be more precise
- if (v_align_ == '\0') {
- flag.enable(true);
- break;
+ case LFUN_TABULAR_FEATURE: {
+ istringstream is(cmd.argument);
+string s;
+is >> s;
+ if (nrows() <= 1
+ && (s == "delete-row" || s == "swap-row")) {
+ flag.message(N_("Only one row"));
+flag.enabled(false);
+ return true;
}
- if (cmd.argument.empty()) {
- flag.enable(false);
- break;
+ if (ncols() <= 1
+ && (s == "delete-column" || s == "swap-column")) {
+ flag.message(N_("Only one column"));
+flag.enabled(false);
+ return true;
}
- if (!contains("tcb", cmd.argument[0])) {
- flag.enable(false);
- break;
+ if
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: >> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > | Lars> But I see no bug problems in CVS currently. What must be fixed | Lars> for 1.4.0? > | Lars> I'd like all code-cleanup, feature-fixing etc to stop now and go | Lars> into hard freeze and only fix regressions and crashes. > | One thing I see that may need big changes is that selecting with the | mouse is terribly slow. > | Also, selection by double click is broken. > | We have to decide what to do about change tracking. > | We do not have a working bibinset. > | There are probably many other things, but that's all I remember from | the top of my head. Then we should work on fixing these regressions, but improving any other feature that we have. I'll have a look at the double click issue. -- Lgb
Re: What are the main problems in CVS now?
Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > I'd say the important ones are targeted for MILESTONE 1.4.0 > (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with > inInset [e.g., when the document has a caption outside a float], which is not > yet in bugzilla). When I search for open bugs with "crash" in the summary, I get: 220(relyx), 1119, 1384, 1395, 1466, 1474, 1589, 1595, 1598, 1604, 1735, 1753, 1750(relyx), 1771, 1785, 1788. Some of those might be gone by now, but at least 1119 and 1598(s.a.) are not. Anyway, we should check all those and the 24 open bugs of importance and either close or fix them before 1.4. You may assign half a dozen to me, if you like. Ciao /Andreas
Re: What are the main problems in CVS now?
Andreas Vox <[EMAIL PROTECTED]> writes: | Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > > >> I'd say the important ones are targeted for MILESTONE 1.4.0 >> (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with >> inInset [e.g., when the document has a caption outside a float], which is >> not >> yet in bugzilla). > | When I search for open bugs with "crash" in the summary, I get: | 220(relyx), 1119, 1384, 1395, 1466, 1474, 1589, 1595, 1598, 1604, | 1735, 1753, 1750(relyx), 1771, 1785, 1788. If they are not marked with taget 1.4.0 then I don't see them. (and if they are not marked, they need to be verified to be present on 1.4.0) -- Lgb
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > One thing I see that may need big changes is that selecting with the > mouse is terribly slow. Can't confirm that for LyX/Aqua. /Andreas
Re: What are the main problems in CVS now?
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Then we should work on fixing these regressions, but improving Lars> any other feature that we have. Yes. Lars> I'll have a look at the double click issue. OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not sure it is going to get used. For 1.3.0 we had Michael's bug list which was very useful. JMarc
Re: What are the main problems in CVS now?
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes: > If they are not marked with taget 1.4.0 then I don't see them. > (and if they are not marked, they need to be verified to be present on > 1.4.0) ?? So open bugs which should be fixed for target 1.3.6 wont get fixed for target 1.4.0? I'm not sure if I understand the semantics of the "target" field. /Andreas
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes wrote: > We have to decide what to do about change tracking. I think we can ship 1.4 with change tracking. The status is not worse (even a bit better) than the unofficial 1.3 version that has been distributed separately, and AFAIK people have used that for their daily work. The most annoying bug is 1277 (the crash when pasting insets). This one was also present in the 1.3 patch, until Johnathan Burchill provided a fixed patch, which has not yet ported to HEAD and also seems to need some more discussion. As I understand it, a real fix would need some major rewrite. Regards, Jürgen
Re: What are the main problems in CVS now?
Andreas Vox <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > >> If they are not marked with taget 1.4.0 then I don't see them. >> (and if they are not marked, they need to be verified to be present on >> 1.4.0) > | ?? | So open bugs which should be fixed for target 1.3.6 wont get fixed for | target 1.4.0? I'm not sure if I understand the semantics of the "target" | field. Me neither perhaps. We have some 250 open bugs, but no idea if they exist in 1.3.x or in HEAD. We need to be able to mark the bugs so that we know what to work on. -- Lgb
Interview with Mathias
Hi, you read it here: http://www.fosdem.org/index/interviews/interviews_ettrich There are two questions there related with LyX, that basically are due to the external perception that the LyX development is stalled... -- José Abílio
Re: What are the main problems in CVS now?
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes: Andreas> Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: >> If they are not marked with taget 1.4.0 then I don't see them. (and >> if they are not marked, they need to be verified to be present on >> 1.4.0) Andreas> ?? So open bugs which should be fixed for target 1.3.6 wont Andreas> get fixed for target 1.4.0? I'm not sure if I understand the Andreas> semantics of the "target" field. Well, at this point we mainly look at regressions from 1.3.x to 1.4.0. We are not searching to fix all possible LyX bugs, but definitely want to fix new bugs. A possibility is to search for bugs reported against 1.4.0cvs. JMarc
Re: What are the main problems in CVS now?
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes: > Me neither perhaps. > > We have some 250 open bugs, but no idea if they exist in 1.3.x or in > HEAD. We need to be able to mark the bugs so that we know what to work > on. > So maybe we should use a wiki TODO list once more. My proposal: - bugs 1119, 1277, 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with inInset - check when and why selecting with the mouse is terribly slow. - fix selection by double click is broken. - decide what to do about change tracking. - fix bibinset. - set PATH_prefix in lib/configure for Mac (Bennet complained about this. As it is now, LyX won't work out of the box on Mac) 1.4.1: - Polished Docbook support * write a bugreporting HOWTO that defines what fields are mandatory and how to choose between all those version, platform, target etc. values. Define how the status relates to the work schedule.
Re: Interview with Mathias
"Jose' Matos" <[EMAIL PROTECTED]> writes: | Hi, > | you read it here: http://www.fosdem.org/index/interviews/interviews_ettrich > | There are two questions there related with LyX, that basically are due to | the external perception that the LyX development is stalled... I read it as well. -- Lgb
Re: Interview with Mathias
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> | There are two questions there related with LyX, that basically Lars> are due to | the external perception that the LyX development is Lars> stalled... Lars> I read it as well. These questions have been proposed on the linuxfr.org site: http://linuxfr.org/forums/40/6351.html JMarc
Re: What are the main problems in CVS now?
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes: Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained Andreas> about this. As it is now, LyX won't work out of the box on Andreas> Mac) The other solution is to preset this in the preferences file, as is done currently for converters. Andreas> 1.4.1: - Polished Docbook support Note that nothing that needs a format change will be accepted after 1.4.0. So be sure that you plan ahead. JMarc
Problems with PATH for lyx-13x on MacOS X
With recent versions of lyx-1.3.6 (but not 1.4.0), the PATH environment is not set up properly. There are two problems: 1. It looks as though /usr/bin and /usr/local/bin are not properly added, so attempting to run the configure script or view files results in errors like the following: sh: line 1: sh: No such file or directory sh: line 1: pplatex: No such file or directory sh: line 1: dvipdfm: No such file or directory sh: line 1: latex2html: No such file or directory sh: line 1: dvips: No such file or directory sh: line 1: open: No such file or directory 2. It looks like now users must manually enter the path to their TeX installation in the preference dialog. It would be nice to package LyX so that this was not necessary. So, is it possible to define a PATH and pass this to LyX without having LyX overwrite it? Thanks. Bennett
Re: [Plea] Math bitmaps for Docbook export in LyX 1.4.0, was: Directions needed: Preview and Exportdata
On Thursday 03 February 2005 17:46, Andreas Vox wrote: > Jose' Matos <[EMAIL PROTECTED]> writes: > > You (we) must first convince Lars about it now. > > > > Probably a well laid out argument why this patch is important for > > docbook users. > > Hm, at least it's totally unimportant to non-Docbook users: the only > common code which is touched is the refactoring of PreviewLoader, and I > could replace that by Copy I would like to have this part of the code reviewed by Angus when he returns. :-) > Also it's a fix to bugs #1713, #1714, #1715 and #1716 -- oh, it looks as > if those are assigned to you, JosÃ! :-) :-o ;-) > Ok, Lars, > as Chris' argues on his webpage ( http://www.karakas-online.de/mySGML/ ) > LyX 1.3 is not usable for serious Docbook editing. The main reason is the > broken Math support: no Latex code, instead unused MathML code. > We already fixed some deficiencies in 1.4.0cvs (drop MathML output for > SGML, provide filenames, some escaping, other features). My last patch > http://marc.theaimsgroup.com/?l=lyx-devel=110710201022468=2 > completes this in using preview.sty to produce bitmap files for all > equations, thus not only providing the filenames but the files as well. > > Since these changes don't touch the non-Docbook users and LyX 1.2 was > used by some (most?) Docbook users in favour of LyX 1.3, I think we > should try to provide decent Docbook support for LyX 1.4.0. > > Is this convincing? It is for me. I should apologize to you as my time lately has been almost nil to look into this carefully. This will hopefully improve after the 22nd. > Cheers > /Andreas -- Josà AbÃlio
Re: What are the main problems in CVS now?
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > > > "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes: > > Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained > Andreas> about this. As it is now, LyX won't work out of the box on > Andreas> Mac) > > The other solution is to preset this in the preferences file, as is > done currently for converters. Problem is there are three likely paths: /sw/bin, /usr/local/teTeX/bin/powerpc-apple-darwin-current and /opt/local/teTeX/bin> I thought of a solution where configure checks an additional list of directories when it looks for executable. Any time an executable is not found in the current opath but in one of those directories, it gets added to PATH_prefix. Could also be used on other platforms. > Andreas> 1.4.1: - Polished Docbook support > > Note that nothing that needs a format change will be accepted after > 1.4.0. So be sure that you plan ahead. Just want to polish, not to re-forge :-) It's mainly the bitmap generation for equations, some tweeks to output_docbook() and improvement of the db layout files. Maybe enable the db classes even if no sgmltools or equivalent is found (output SGML/XML still works, and you can use the other classes without TeX, no?) Ciao /Andreas
Re: What are the main problems in CVS now?
On Feb 10, 2005, at 10:31 AM, Jean-Marc Lasgouttes wrote: "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes: Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained Andreas> about this. As it is now, LyX won't work out of the box on Andreas> Mac) The other solution is to preset this in the preferences file, as is done currently for converters. The trouble is, there are three possible locations for TeX installations on the Mac, all of which are commonly used: /usr/local/teTeX/bin/powerpc-apple-darwin-current, /opt/local/teTeX/bin, and /sw/bin. Is it possible to include all of these in the preference file? -- Simply entering /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin: /sw/bin doesn't seem to do it. The alternative would be to run a configuration script on installing LyX/Mac, but that prevents the simple drag-and-drop installation most desirable for the Mac. Bennett
Re: What are the main problems in CVS now?
Andreas Vox <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > >> Me neither perhaps. >> >> We have some 250 open bugs, but no idea if they exist in 1.3.x or in >> HEAD. We need to be able to mark the bugs so that we know what to work >> on. >> > | So maybe we should use a wiki TODO list once more. My proposal: No... bugzilla should be used. If this is a bug we require to be fixed in 1.4.0 then that should be its target. If we have no idea then we remove target, if we expect it to be fixed in 1.4.1 then mark it as 1.4.1. | * write a bugreporting HOWTO that defines what fields are mandatory and |how to choose between all those version, platform, target etc. values. |Define how the status relates to the work schedule. I'd say that the reporter should only look at version and platform the rest is not his task. -- Lgb
Re: [Patch] SnippetConversion for previews and DocBook
On Monday 31 January 2005 20:58, Andreas Vox wrote: > > > Just to simplify my work what are your doubts regarding the docbook > > part? > > Options: > a) using entities for filenames or not (cf. graphicsinset) Whatever is more convenient. The option for entities was due to the need to create relative paths in the exported docbook. The latex backend uses the [EMAIL PROTECTED] trick and we use the external entities... > b) putting image files in a subdirectory or not, what name to use for the > subdirectory math-images (?!) ;-) > c) How to align math bitmaps vertically. It's no problem to get > ascent/descent from preview.sty, but how to code it in XML? > Docbook defines valign=(top|center|bottom) which is not good enough, > XHTML apparently also knows "valign=-7px" What do others use? > d) What file formats should we produce? All, just PNG, just EPS or > PNG+EPS ? I think that we can play here the same tricks as we do with latex. But to be simple I would say both, and not passing the extension (since some stylesheets take care of this). The other option would be to declare the different formats... > e) Should we use Chris' > everywhere, just SGML or not at all? Just SGML. It is valid so why not to use it. > f) Are these decisions the same for SGML and XML? Mostly, I would expect. > g) What "density" or magnification should be used for maths? > (Not knowing the final font size) Me neither. :-) > My ideas: > a) Do it consistently, maybe drop the entities if noone protests Now you know the problems. You don't want to have absolute paths in the exported code, it is ugly and ugh.. no portable. :-) > b) Yes, something like myFile_images/ That is fair. > c) Produce illegal valign attributes which can be used directly for XHTML I will close my eyes here. ;-) > d) EPS + PNG, let other tools do the rest I agree. > e) Only for EPS + PNG Ok. > f) Yes I agree. > g) No idea. That's the advantage of EPS images, they are scalable... I agree also. > > PS: Have you seen that it is possible for docbook 5.0 to be release > > without a dtd? More and more xml is becoming the default. > > Haven't looked at DB 5.0 yet and don't understand your statement. There > will be _no_ DTD for DB 5.0? Something instead, like schema or relax NG? A Relax NG and from there the DTD will be derived. (If I understood correctly). > Ciao Ciao. > /Andreas -- Josà AbÃlio
Re: What are the main problems in CVS now?
On Thursday 10 February 2005 15:42, Andreas Vox wrote: > > Note that nothing that needs a format change will be accepted after > > 1.4.0. So be sure that you plan ahead. No file format change is needed. > Just want to polish, not to re-forge :-) It's mainly the bitmap > generation for equations, some tweeks to output_docbook() and improvement > of the db layout files. Maybe enable the db classes even if no sgmltools > or equivalent is found (output SGML/XML still works, and you can use the > other classes without TeX, no?) It makes sense. We would then gray out the corresponding entries in the menus. The code shouldn't be too difficult. :-) > Ciao > /Andreas -- José Abílio
Re: What are the main problems in CVS now?
Bennett Helm <[EMAIL PROTECTED]> writes: > > Is it possible to include all of these in the preference file? -- > Simply entering > /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin: > /sw/bin doesn't seem to do it. Why? I just tested adding a non-existing directory to my path_prefix and LyX still works. OTOH it might be that 1.3.6 runs configure _before_ it reads the preferences file :-( Can you check with lyx -dbg init? Ciao /Andreas
Re: Bug: Flickering
Fedora Core 3 with a Gnome desktop (why haven't I switched yet is a long story) and the RPM I got is from the site below (direct link included), using apt for RPM. http://dag.wieers.com/ http://apt.sw.be/fedora/3/en/i386/RPMS.dag/lyx-1.3.5-1.1.fc3.rf.i386.rpm None of my other applications flicker like this. Any chance you can test that binaries in that RPM, to confirm whether or not it is those specific binaries? If I get time, I will try to make my own LyX binaries, but if it still flickers, then either I am making it incorrectly or there is something wrong with another Fedora component (it wouldn't be the first time, trust me). Are you sure that you get no flickering whatsoever? I tried turning off instant preview, but it made no difference. To reproduce, simply make a large multipage document, run your desktop in a high resolution of at least 1280x960, maximize the LyX window, and use the scroll bar to scroll. Flickering is harder to notice with a very small Window. Also, I swear LyX flickers in Debian testing too. Of course, I haven't used Debian testing since last summer, so my memory of it isn't all that good. LyX is still perfectly functional and very useful in spite of the flickering, but it just looks really bad. On Thu, 2005-02-10 at 14:17 +0100, Jean-Marc Lasgouttes wrote: > > "Luke" == Luke Simon <[EMAIL PROTECTED]> writes: > > Luke> The main editor pane of Lyx flickers when scrolling up or down > Luke> using the scrollbar. It really destroys the visual "polish" of > Luke> this great application. > > I do not see this... What OS/computer are you using? > > JMarc
