Re: What are the main problems in CVS now?
Andre Poenitz <[EMAIL PROTECTED]> writes: | [BTW, do we have still have Intra-EU regulations on the amount of beer | one is allowed to transport from one country to another?] Yes, but is now somtehing like 150 litres -- Lgb
Re: What are the main problems in CVS now?
On Tue, Feb 15, 2005 at 11:08:45AM +0100, Lars Gullik Bjønnes wrote: > Asger Alstrup <[EMAIL PROTECTED]> writes: > > | Andre Poenitz wrote: > >> On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote: > >>>If there is interest and if things evolve positively, I may be able to > >>> propose Paris > >> Both sound nice. [And in case it matters: I am a bit biased towards > >> France outside Paris...] > > > | Paris sounds great! > > Except for the beer... but I can settle for some wine as well. Well, first of all, French beer isn't really bad. You can certainly get drunk enough to fall off a sleigh if you intend to do so. Secondly, Paris is close enough to go there by car if necessary. And in a car there should be enough room for an amount of beer that will you keep happy for a few days. [BTW, do we have still have Intra-EU regulations on the amount of beer one is allowed to transport from one country to another?] Andre'
Re: What are the main problems in CVS now?
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: | Paris sounds great! Lars> Except for the beer... but I can settle for some wine as well. Sure, beer is not a big selling point. Lars> I think you just got selected by acclamation, Jean-Marc. Hmm, well, let's see what I can do. JMarc
Re: What are the main problems in CVS now?
Asger Alstrup <[EMAIL PROTECTED]> writes: | Andre Poenitz wrote: >> On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote: >>>If there is interest and if things evolve positively, I may be able to >>> propose Paris >> Both sound nice. [And in case it matters: I am a bit biased towards >> France outside Paris...] > | Paris sounds great! Except for the beer... but I can settle for some wine as well. I think you just got selected by acclamation, Jean-Marc. -- Lgb
Re: What are the main problems in CVS now?
On Monday 14 February 2005 16:17, Jean-Marc Lasgouttes wrote: > Interested? Certainly. :-) > JMarc -- José Abílio
Re: What are the main problems in CVS now?
Andre Poenitz wrote: On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote: If there is interest and if things evolve positively, I may be able to propose Paris Both sound nice. [And in case it matters: I am a bit biased towards France outside Paris...] Paris sounds great! Regards, Asger
Re: What are the main problems in CVS now?
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote: > > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: > > Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes > Andre> wrote: > >> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I > >> hope this still holds... > > Andre> Apropos Chemnitz. Where do we go this year? > > If there is interest and if things evolve positively, I may be able to > propose Paris (the flat where I am about to move) or its suburb (my > parent can probably be persuaded to lend their house, which is quite > nice, but it's not really Paris...). Both sound nice. [And in case it matters: I am a bit biased towards France outside Paris...] > I would have to find some computers, and there would be some adsl > connection. I'd bring a laptop and that largish hub we used in Chemnitz if needed. > Interested? Sure. Andre'
Re: What are the main problems in CVS now?
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes Andre> wrote: >> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I >> hope this still holds... Andre> Apropos Chemnitz. Where do we go this year? If there is interest and if things evolve positively, I may be able to propose Paris (the flat where I am about to move) or its suburb (my parent can probably be persuaded to lend their house, which is quite nice, but it's not really Paris...). I would have to find some computers, and there would be some adsl connection. Interested? JMarc
Re: What are the main problems in CVS now?
On Fri, Feb 11, 2005 at 10:18:25PM +0100, Andre Poenitz wrote: > > What I am most concerned about is: Will there be any fundamental code > > changes right after the release of LyX 1.4? > > I would guess people will have a shot at XML file format which will > probably change (and hopefully simplify) most of the export and import > code. I'd really want to work on the character style stuff. john
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 08:01:55PM +0100, Michael Schmitt wrote: > What I am most concerned about is: Will there be any fundamental code > changes right after the release of LyX 1.4? I would guess people will have a shot at XML file format which will probably change (and hopefully simplify) most of the export and import code. > 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...? No easier than now, I am afraid. On my side the hardware situation has improved yet the time constraints continue to exist. Andre'
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes wrote: > We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I > hope this still holds... Apropos Chemnitz. Where do we go this year? Andre'
Re: What are the main problems in CVS now?
On Thu, Feb 10, 2005 at 01:06:45PM +0100, 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 like all code-cleanup, feature-fixing etc to stop now and go into > hard freeze and only fix regressions and crashes. Mouse selection in math seemed to be broken last weekend. Andre'
Re: What are the main problems in CVS now?
Johnathan Burchill wrote: > Change-tracking itself probably does not need a major rewrite. It's the > cut-and-paste code that needs to be thought-out. Yes, that's what I meant. > I will look into HEAD this weekend, and report back to the list. That'd be great. Thanks, Jürgen
Re: What are the main problems in CVS now?
Jürgen wrote: >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, > Change-tracking itself probably does not need a major rewrite. It's the cut-and-paste code that needs to be thought-out. I will look into HEAD this weekend, and report back to the list. JB -- Johnathan K. Burchill, Ph.D. [EMAIL PROTECTED] pgp1YDGPP5RaS.pgp Description: PGP signature
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: 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?
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
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: 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?
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?
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: 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?
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 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?
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: 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?
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: 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?
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?
> "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
Re: What are the main problems in CVS now?
Andreas Vox wrote: > 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. quite a bunch of them are fixedintrunk. Jürgen
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: 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?
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
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?
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 <[EMAIL PROTECTED]> writes: >> "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. I am only looking at bugzilla and bugs marked for 1.4.0cvs. We should use that (bugzilla). -- Lgb
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?
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?
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?
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?
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?
> "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: 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 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
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
