Edwin Leuven wrote:
Edwin Leuven wrote:
Edwin Leuven wrote:
updated patch attached.
the attached is going in now (i also remove some unused code)
http://www.lyx.org/trac/changeset/15526
(love talking of myself, just like home ;-)
Less talk more action... Some other bugs are still waiting
Edwin Leuven wrote:
Edwin Leuven wrote:
updated patch attached.
the attached is going in now (i also remove some unused code)
http://www.lyx.org/trac/changeset/15526
(love talking of myself, just like home ;-)
Edwin Leuven wrote:
Asger Ottar Alstrup wrote:
- The preferences dialog has the wrong size initially
updated patch attached.
the attached is going in now (i also remove some unused code)
Index: panelstack.C
===
--- panelstack.C
Edwin Leuven wrote:
Asger Ottar Alstrup wrote:
- The preferences dialog has the wrong size initially
updated patch attached.
works for me, so will commit soon unless someone doesn't like it...
Index: panelstack.C
===
--- panelsta
Asger Ottar Alstrup wrote:
- The preferences dialog has the wrong size initially
the attached patch makes things better on my side
can others confirm?
(the treewidget is too wide though...)
Index: panelstack.C
===
--- panelstack.
Lars Gullik Bjønnes wrote:
> Remember though that those fixes was mostly just to get things
> compiling. Everything else, including segfault on startup, was left
> for interested parties to fix.
In gtk yes, but not in qt3. I remember one segfault in qt3 I did not fix
immediately, but IIRC I did i
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> He did but there's a difference: he cared a bit about qt3.
Abdelrazak> I didn't care one bit but I still did some maintainance
Abdelrazak> work reluctantly.
You should probably not have done that... This got you grump
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> The deal was not clear at all to me. Anytime I broke qt3
Abdelrazak> and/or gtk someone complained. So I felt forced to do the
Abdelrazak> maintaining work because I am such a good guy...
It s
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
|
| Abdelrazak> The deal was not clear at all to me. Anytime I broke qt3
| Abdelrazak> and/or gtk someone complained. So I felt forced to do the
| Abdelrazak> maintaining work be
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes wrote:
| >> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >
| >>> Quite a few bugs in the qt4 frontend though.
| > Abdelrazak> Man, that's an entirely new frontend. Dialogs bugs
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> The deal was not clear at all to me. Anytime I broke qt3
Abdelrazak> and/or gtk someone complained. So I felt forced to do the
Abdelrazak> maintaining work because I am such a good guy...
It seemed to me that Georg di
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Abdelrazak Younes wrote:
>>
>>> It was pseudo-friday JMarc.
>>
>> I did not understand that as a friday-post either.
>
> My sincere excuse then.
Taken.
Georg
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> It is difficult to check now, but at the time it seems it was
>> qt4-only. I do not want to point all qt4 bugs in order to blame
>> you.
Abdelrazak> But that's how it looks from the exterior.
Then I am sorry. The fact is, th
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
If it was not ready, it was not wise to push it.
Abdelrazak> I _never_ advocate to remove qt3. I always said that it's
Abdelrazak> fine if somebody tries to maintain it. Nethertheless,
Abdelrazak> Georg
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Sure, but unicode was the only new feature on the table for 1.5.
So it is authorized to introduce bugs.
Abdelrazak> So revert qt3 and delete qt4.
Did I _ever_ ask to remove qt4? I always emphasized di
Georg Baum wrote:
Abdelrazak Younes wrote:
It was pseudo-friday JMarc.
I did not understand that as a friday-post either.
My sincere excuse then.
Abdel.
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> Sure, but unicode was the only new feature on the table for 1.5.
>> So it is authorized to introduce bugs.
Abdelrazak> So revert qt3 and delete qt4.
Did I _ever_ ask to remove qt4? I always emphasized diversity vs
winning wa
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes wrote:
| >> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >
| >>> Quite a few bugs in the qt4 frontend though.
| > Abdelrazak> Man, that's an entirely new frontend. Dialogs bugs are
| > Abdelrazak> easy to s
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> If it was not ready, it was not wise to push it.
Abdelrazak> I _never_ advocate to remove qt3. I always said that it's
Abdelrazak> fine if somebody tries to maintain it. Nethertheless,
Abdelrazak> Georg and *me* were the prime
Abdelrazak Younes wrote:
And I repeat myself: dialog bugs are far far far easier to solve than
core bugs. So it's not like we are in such hurry with regard to qt4.
Could you fix these, which are the only bugs I know of in the front-end?
- The preferences dialog has the wrong size initially
- T
Abdelrazak Younes wrote:
> It was pseudo-friday JMarc.
I did not understand that as a friday-post either.
Georg
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Quite a few bugs in the qt4 frontend though.
Abdelrazak> Man, that's an entirely new frontend. Dialogs bugs are
Abdelrazak> easy to solve. Dialog bugs have almost nothing to do with
Abdelrazak> my clean
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> And yours also. You have introduced a number of big
Abdelrazak> changes in the code. Personally I think your InsetParams
Abdelrazak> changes did introduce more hidden bugs than my cleanups.
I
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> Quite a few bugs in the qt4 frontend though.
Abdelrazak> Man, that's an entirely new frontend. Dialogs bugs are
Abdelrazak> easy to solve. Dialog bugs have almost nothing to do with
Abdelrazak> my cleanups. You could even help
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> And yours also. You have introduced a number of big
Abdelrazak> changes in the code. Personally I think your InsetParams
Abdelrazak> changes did introduce more hidden bugs than my cleanups.
I do not see how the insetp
Georg Baum wrote:
Am Sonntag, 22. Oktober 2006 10:46 schrieb Abdelrazak Younes:
Georg Baum wrote:
But you are. If drastic measures are needed, then I expect that the
first
thing that is forbidden is new stuff that touches the core. And
multiple
views (although I agree it is nice to have) is
Am Sonntag, 22. Oktober 2006 10:46 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > But you are. If drastic measures are needed, then I expect that the
first
> > thing that is forbidden is new stuff that touches the core. And
multiple
> > views (although I agree it is nice to have) is such st
Am Sonntag, 22. Oktober 2006 10:39 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > Am Samstag, 21. Oktober 2006 17:50 schrieb Abdelrazak Younes:
> >> Georg Baum wrote:
> >>> Am Samstag, 21. Oktober 2006 16:43 schrieb Asger Ottar Alstrup:
> >>>
> >>>
> >>> Maybe you should also talk about why the
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Georg Baum <[EMAIL PROTECTED]> writes:
| > | > | No. But this announcement came too suddenly after a pe
On Sat, 21 Oct 2006, Asger Ottar Alstrup wrote:
> Regards,
> Asger & Jürgen
> P.S. On meetings, every day is a Friday!
I was wondering about that...
cheers
/Christian
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
On Sunday 22 October 2006 10:20, Michael Gerz wrote:
> Georg Baum wrote:
> >If you look what I did during the last months you will see that most of it
> >was bug fixing. Now I know that this was wrong and I should have done some
> >other stuff instead.
>
> Georg, please continue your great work! (T
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Georg Baum <[EMAIL PROTECTED]> writes:
| > | > | No. But this announcement came too suddenly after a period where
| > | > everything
Georg Baum wrote:
If you look what I did during the last months you will see that most of it
was bug fixing. Now I know that this was wrong and I should have done some
other stuff instead.
Georg, please continue your great work! (This also counts for Abdel,
Jürgen, ...)
I think the overal
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Georg Baum <[EMAIL PROTECTED]> writes:
| > | No. But this announcement came too suddenly after a period where
| > everything | was allowed.
| > Everything was allowed because none of you cou
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Georg Baum <[EMAIL PROTECTED]> writes:
| > | No. But this announcement came too suddenly after a period where
| > everything | was allowed.
| > Everything was allowed because none of you could restrain yourselves.
| > (
Lars Gullik Bjønnes wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
| No. But this announcement came too suddenly after a period where everything
| was allowed.
Everything was allowed because none of you could restrain yourselves.
(And everything I open my mouth I get into a flamewar, so I let
Georg Baum wrote:
Am Samstag, 21. Oktober 2006 18:01 schrieb Asger Ottar Alstrup:
Georg Baum wrote:
** NO NEW FEATURES ARE ALLOWED FROM RIGHT NOW **
I do not agree with this one if it means all new features, not just
those
that require changes to the core.
The sooner we fix the basic th
Lars Gullik Bjønnes wrote:
> | You should know both Jürgen and me well enough to understand that we are
> | not going to simply demand solutions without helping to find it.
>
> So far no solutions has been proposed.
> (Except the one below and the one that we put in.)
I admit that this is true, an
Georg Baum wrote:
Am Samstag, 21. Oktober 2006 17:50 schrieb Abdelrazak Younes:
Georg Baum wrote:
Am Samstag, 21. Oktober 2006 16:43 schrieb Asger Ottar Alstrup:
Maybe you should also talk about why the current state is like it is.
Just for clarification, I hope you don't mean that it is my f
Am Sonntag, 22. Oktober 2006 10:17 schrieb Lars Gullik Bjønnes:
> Georg Baum <[EMAIL PROTECTED]> writes:
>
> | Am Samstag, 21. Oktober 2006 19:36 schrieb Lars Gullik Bjønnes:
> | > Discussions are made and concluded in the kitchen, those not able to
> | > get out of the living room get no say.
> |
Am Sonntag, 22. Oktober 2006 10:02 schrieb Asger Ottar Alstrup:
> The patch looks great! Please apply it.
Not in that state, because it will not be possible anymore to output utf8,
and it will silently break multiple encodings. If anybody wants to use
this as a start, feel free to do so. I won't
Georg Baum <[EMAIL PROTECTED]> writes:
| > We just have to draw a
| > line somewhere, because we feel that something has to change compared to
| > how things are going now. The sooner people use their energy on fixing
| > things, the sooner new features can come in again.
|
| If you look what
Georg Baum <[EMAIL PROTECTED]> writes:
| Am Samstag, 21. Oktober 2006 19:36 schrieb Lars Gullik Bjønnes:
| > Discussions are made and concluded in the kitchen, those not able to
| > get out of the living room get no say.
| > Espeically not if they does not help with providing solutions instead
| >
Am Samstag, 21. Oktober 2006 18:01 schrieb Asger Ottar Alstrup:
> Georg Baum wrote:
> >> ** NO NEW FEATURES ARE ALLOWED FROM RIGHT NOW **
> >
> > I do not agree with this one if it means all new features, not just
those
> > that require changes to the core.
>
> The sooner we fix the basic
Georg Baum wrote:
For information I attach here the patch I was working on yesterday before
the freeze announcement. It already works for the case where you have only
one encoding in the document. I also had an idea how to treat multiple
encodings that would need a similar amount of changes. Th
Am Samstag, 21. Oktober 2006 17:50 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > Am Samstag, 21. Oktober 2006 16:43 schrieb Asger Ottar Alstrup:
> >
> >
> > Maybe you should also talk about why the current state is like it is.
>
> Just for clarification, I hope you don't mean that it is my
Am Samstag, 21. Oktober 2006 19:36 schrieb Lars Gullik Bjønnes:
> Discussions are made and concluded in the kitchen, those not able to
> get out of the living room get no say.
> Espeically not if they does not help with providing solutions instead
> of problems.
Why should we provide a solution wh
Juergen Spitzmueller wrote:
Lars Gullik Bjønnes wrote:
Discussions are made and concluded in the kitchen, those not able to
get out of the living room get no say.
Espeically not if they does not help with providing solutions instead
of problems.
I see.
I'll shut up, then.
Just remember that
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Discussions are made and concluded in the kitchen, those not able to
| > get out of the living room get no say.
| > Espeically not if they does not help with providing solutions instead
| > of problems.
|
| I see.
|
Lars Gullik Bjønnes wrote:
> Discussions are made and concluded in the kitchen, those not able to
> get out of the living room get no say.
> Espeically not if they does not help with providing solutions instead
> of problems.
I see.
I'll shut up, then.
Jürgen
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Asger Ottar Alstrup wrote:
| > Georg, the last few commits have resurrected LyX back from the dead. You
| > are therefore allowed to do a few of your pet features outside the
| > kernel, just because you are such a nice guy. Hope that will keep yo
Asger Ottar Alstrup wrote:
> Georg, the last few commits have resurrected LyX back from the dead. You
> are therefore allowed to do a few of your pet features outside the
> kernel, just because you are such a nice guy. Hope that will keep you
> motivated.
You are trying to clean up the kitchen? Th
Georg, the last few commits have resurrected LyX back from the dead. You
are therefore allowed to do a few of your pet features outside the
kernel, just because you are such a nice guy. Hope that will keep you
motivated.
Regards,
Asger & Jürgen
P.S. On meetings, every day is a Friday!
Georg Baum wrote:
** NO NEW FEATURES ARE ALLOWED FROM RIGHT NOW **
I do not agree with this one if it means all new features, not just those
that require changes to the core.
The sooner we fix the basic things, the sooner we can introduce new and
small features. The fact is that right
Georg Baum wrote:
Am Samstag, 21. Oktober 2006 16:43 schrieb Asger Ottar Alstrup:
Maybe you should also talk about why the current state is like it is.
Just for clarification, I hope you don't mean that it is my fault. My
cleanup work have always been pretty careful and the general Cut&Paste
Michael Gerz wrote:
Does Denmark agree that bug fixes are welcome at all times?
We are just starting organizing a national election to decide this.
So far the polls say yes, but you know what happened with the Euro.
Regards,
Denmark
Abdelrazak Younes wrote:
> In your case Juergen, I think we just need a simple script that will
> convert the lyx file from utf8 to latin1 and modify a bit the preamble.
> This script would be of course be called automatically from lyx and
> would come with 1.5.1 if everything goes well.
Well that
Am Samstag, 21. Oktober 2006 16:43 schrieb Asger Ottar Alstrup:
> We decide the following rules to bring things back on track:
>
>
> ** NO NEW FEATURES ARE ALLOWED FROM RIGHT NOW **
I do not agree with this one if it means all new features, not just those
that require changes to the core.
Juergen Spitzmueller wrote:
Lars Gullik Bjønnes wrote:
You of course mean limitations of latex...
The limitations of the current utf8 encoding with inputenc, of course. Or the
limitations of some packages (on which I rely) that don't work with utf8, for
that matter. I think I tried to explai
Asger Ottar Alstrup wrote:
** NO NEW FEATURES ARE ALLOWED FROM RIGHT NOW **
Fine. We already have enough features in LyX.
So ongoing work like unicode, change tracking, and multiple windows
can continue. Other work has to wait, including performance work.
Will 1.5.0's performance be at
Asger Ottar Alstrup wrote:
Hi,
We have discussed the state of SVN, and concluded the following:
*** Trunk is very broken right now
Basic things like editing, cut, copy & paste, navigation, undo/redo and
so on are broken. Everytime a bug is fixed, 10 new ones are discovered.
Lars Gullik Bjønnes wrote:
> You of course mean limitations of latex...
The limitations of the current utf8 encoding with inputenc, of course. Or the
limitations of some packages (on which I rely) that don't work with utf8, for
that matter. I think I tried to explain the problems earlier.
> Tha
Martin Vermeer wrote:
However, I would spend a few weeks on further debugging a nominally
working 1.5 branch before the first official release. Of course
pre-releases or rc's would be OK. And I also think performance should be
at least non-painful for 1.5.0.
I fully agree. We published 1.4.0
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Asger Ottar Alstrup wrote:
| > Once things are back to working, 1.5 should be released. It might be a
| > slow release, it might not support the encodings people want, but at
| > least it will be useful for most people that use LyX now. Those that
Asger Ottar Alstrup wrote:
> Once things are back to working, 1.5 should be released. It might be a
> slow release, it might not support the encodings people want, but at
> least it will be useful for most people that use LyX now. Those that are
> unhappy about the release will have to settle with
On Sat, Oct 21, 2006 at 04:43:13PM +0200, Asger Ottar Alstrup wrote:
> Hi,
>
> We have discussed the state of SVN, and concluded the following:
>
>
>*** Trunk is very broken right now
>
>
> Basic things like editing, cut, copy & paste, navigation, undo/redo and
> so on are br
Hi,
We have discussed the state of SVN, and concluded the following:
*** Trunk is very broken right now
Basic things like editing, cut, copy & paste, navigation, undo/redo and
so on are broken. Everytime a bug is fixed, 10 new ones are discovered.
Everytime a fix is committe
67 matches
Mail list logo
