RE: Too much options in LyX

Hi. On Wed, Apr 27, 2011 at 02:07:55PM +0200, venom00 wrote: +void GuiDocument::hideView() { + Dialog::hideView(); + // Reset the search box + this-docPS-resetSearch(); +} Style nits: { on a separate line for the function body, and this- seems superfluous. OK. + //

Re: Trunk is completely frozen for any commits

compiled and ran successfully on ubuntu. On Fri, Apr 29, 2011 at 1:23 AM, venom00 veno...@arcadiaclub.com wrote: Local control tower: giving permission to land. Over. One small step for a bunch of developers, a giant leap for mankind. venom00

Re: Maintenance release management

On 04/29/2011 07:50 AM, Jürgen Spitzmüller wrote: Dear all, as you all know meanwhile, I will step back as maintenance release manager as soon as LyX 1.6.10 is released. I'm glad to inform you that Richard accepted to take over maintenance release management. This is an excellent solution,

Re: Maintenance release management

Abdelrazak Younes you...@lyx.org wrote: Excellent solution indeed. Thanks for accepting the duty Richard! Many thanks to you; you really did an amazing work! hear, hear! ed.

Re: Development for LyX 2.1

Anyway, I don't think heavy use of branches is required or needed with git. I am currently involved with two largish projects using git, one near the branches everywhere extreme and the other close to the history should be linear end... Just out of curiosity, do you mind sharing which other

RE: #7493 and preview-latex in general

Bug #7493 is not preview-latex fault. We didn't drop preview-latex before even when it caused a bug. I can imagine dropping it eventually, but it's still useful to get automatic bounding box, isn't it?. If I'm correct that's true just for the pdflatex route. I was thinking of the other

Re: Maintenance release management

Jürgen Spitzmüller wrote: Let me take the opportunity to thank everybody for the support over the last 4 years. thanks for your good job, both 1.5 1.6 releases were pleasure to work with. pavel

Re: Maintenance release management

Le 29/04/2011 12:13, Pavel Sanda a écrit : Jürgen Spitzmüller wrote: Let me take the opportunity to thank everybody for the support over the last 4 years. thanks for your good job, both 1.5 1.6 releases were pleasure to work with. I hope that Juergen already knows what I think, but let me

Re: #7506: CopyStyle for inset layout does not work

On 2011-4-29 7:07 , LyX Ticket Tracker wrote: #7506: CopyStyle for inset layout does not work Comment(by rgheck): I'll have to check this with current trunk. But I'm guessing that the issue is just that the new layouts were not named properly, yet the layout format is beyond where lyx2lyx

RE: Too much options in LyX

Style and form comments are always welcome but please give a little attention to the content too: - Alternative ideas to highlight matching widgets? Currently they become red. - Ideas on how to make the research faster? In the next patch I'll try to add a little delay. Here's the new

Re: Maintenance release management

On 29/04/2011 6:41 AM, Jean-Marc Lasgouttes wrote: Le 29/04/2011 12:13, Pavel Sanda a écrit : Jürgen Spitzmüller wrote: Let me take the opportunity to thank everybody for the support over the last 4 years. Thanks for a job very well done Jürgen. thanks for your good job, both 1.5 1.6

Re: #7493 and preview-latex in general

On 29/04/2011 5:38 AM, venom00 wrote: Bug #7493 is not preview-latex fault. We didn't drop preview-latex before even when it caused a bug. I can imagine dropping it eventually, but it's still useful to get automatic bounding box, isn't it?. If I'm correct that's true just for the pdflatex

Re: LyX opening future versions

Il 29/04/2011 05:02, Richard Heck ha scritto: There's an even better solution: Copy current lyx2lyx from trunk. So let me ask this question: Is there any real reason not to backport lyx2lyx to branch as it changes? Well, trunk is affected by that problem as well: create the simplest LyX

Re: LyXHTML image resolution

Hi Ramin, I'm using 2.0 to export html which I can then convert to epub format with Calibre. I've been playing with the same export. So far I've been really happy. Rather than using Calibre to do the conversion, you might take a look at Sigil. It creates a much cleaner ePub (though Calibre

Re: LyX opening future versions

Il 29/04/2011 06:09, Liviu Andronic ha scritto: On Fri, Apr 29, 2011 at 5:02 AM, Richard Heckrgh...@comcast.net wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't

Re: LyX opening future versions

Le 29/04/2011 15:25, Tommaso Cucinotta a écrit : Il 29/04/2011 05:02, Richard Heck ha scritto: There's an even better solution: Copy current lyx2lyx from trunk. So let me ask this question: Is there any real reason not to backport lyx2lyx to branch as it changes? Well, trunk is affected by

Re: LyX opening future versions

Oops! message sent too fast! Next part. Le 29/04/2011 15:34, Jean-Marc Lasgouttes a écrit : Le 29/04/2011 15:25, Tommaso Cucinotta a écrit : I don't know whether lyx2lyx is designed to solely upgrade the file format, or also to downgrade it, because in the former case it wouldn't help. Of

Re: LyX opening future versions

Tommaso Cucinotta wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't see a real problem here unnoticed dataloss in your conversion step seems to me quite real

Re: Maintenance release management

On 04/29/2011 09:20 AM, Julien Rioux wrote: On 29/04/2011 6:41 AM, Jean-Marc Lasgouttes wrote: I hope that Juergen already knows what I think, but let me concur that he has been the right man for the job. And I suspect that I will be able to say the same about Richard in XX years when he'll

Re: LyX opening future versions

On 04/29/2011 09:53 AM, Pavel Sanda wrote: Tommaso Cucinotta wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't see a real problem here unnoticed dataloss in your

Re: LyX opening future versions

On 29/04/2011 10:03 AM, Richard Heck wrote: On 04/29/2011 09:53 AM, Pavel Sanda wrote: Tommaso Cucinotta wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't see a

Re: Maintenance release management

Le 29/04/2011 15:54, Richard Heck a écrit : Yes, we hope for double digits years. I was wondering about that myself. :) The goal is actually the opposite: have a short enough term for maintainers, so that they don't burn out and can do the job again later. JMarc

RE: Maintenance release management

Dear all, as you all know meanwhile, I will step back as maintenance release manager as soon as LyX 1.6.10 is released. I'm glad to inform you that Richard accepted to take over maintenance release management. This is an excellent solution, IMHO. Let me take the opportunity to

Re: LyX opening future versions

On Fri, Apr 29, 2011 at 9:11 AM, Julien Rioux jri...@physics.utoronto.ca wrote: On 29/04/2011 10:03 AM, Richard Heck wrote: couldn't you give your colleagues file exported to 1.6 on your side? A possible solution would be to imitate what Openoffice does (and perhaps Microsoft word as well, I

Re: Trunk is completely frozen for any commits

Just adding to the chorus: compiled and run successfully on Kubuntu Maverick Stefano

Re: Development for LyX 2.1

On 28.04.2011 22:49, Enrico Forestieri wrote: On Thu, Apr 28, 2011 at 11:23:29AM -0600, Rob Oakes wrote: It sounds as though consensus is emerging. Would it be possible to have the the git master branch mirrored into the existing SVN repository? This would make it easy for those of us trying

Re: Trunk is completely frozen for any commits

On 29.04.2011 17:03, stefano franchi wrote: Just adding to the chorus: compiled and run successfully on Kubuntu Maverick Stefano Also ok: - Ubuntu 11.4 - Scientific Linux 6 - openSuse 11.4, but monolithic build is broken Peter

Re: Trunk is completely frozen for any commits

Am 29.04.2011 um 03:18 schrieb Pavel Sanda: Richard Heck wrote: On 04/28/2011 08:21 PM, Pavel Sanda wrote: dear passengers, please fasten your seatbelts. Fasten Seat Belts tarballs temporarily uploaded here: ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/2.0.0/ i'm waiting for packagers to

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: - openSuse 11.4, but monolithic build is broken whats the error message? pavel

Re: Trunk is completely frozen for any commits

Original-Nachricht Datum: Fri, 29 Apr 2011 18:08:55 +0200 Von: Pavel Sanda sa...@lyx.org An: lyx-devel@lists.lyx.org Betreff: Re: Trunk is completely frozen for any commits Peter Kümmel wrote: - openSuse 11.4, but monolithic build is broken whats the error message?

Re: Trunk is completely frozen for any commits

Pavel Sanda wrote: ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/2.0.0/ other people please send me ack that you have been able to build/run lyx 2.0.0 successfully successful landing Compiled and run successfully on Ubuntu Natty thanks to all developers Best Ignacio García

Re: Trunk is completely frozen for any commits

On Fri, Apr 29, 2011 at 6:18 PM, Peter Kuemmel syntheti...@gmx.net wrote: There are no problems with GCC 4.5.2 (Ubuntu 11.4) also not with GCC 4.6.0 (Fedora 15) works. Neither with GCC 4.4.3 and Qt 4.6.2 on Xubuntu 10.04 (Lucid). Liviu

Re: LyX opening future versions

Richard Heck wrote: It shouldn't. One loses data in the sense that insets can get converted to ERT, but you shouldn't lose data in any other sense. there are features which are lost during the conversion back simply because there is nothing comparable in previous versions. secondly if we do

Re: Trunk is completely frozen for any commits

Stephan Witt wrote: 2) polish the dmg a little bit - add some readme etc. take your time. p

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: Original-Nachricht Datum: Fri, 29 Apr 2011 18:08:55 +0200 Von: Pavel Sanda sa...@lyx.org An: lyx-devel@lists.lyx.org Betreff: Re: Trunk is completely frozen for any commits Peter Kümmel wrote: - openSuse 11.4, but monolithic build is broken

Re: Trunk is completely frozen for any commits

On 29.04.2011 18:38, Pavel Sanda wrote: Peter Kümmel wrote: Original-Nachricht Datum: Fri, 29 Apr 2011 18:08:55 +0200 Von: Pavel Sandasa...@lyx.org An: lyx-devel@lists.lyx.org Betreff: Re: Trunk is completely frozen for any commits Peter Kümmel wrote: - openSuse 11.4, but

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: I also don't like the patch. I first tried docstring(btPrintNotCited) but gcc doesn't know the const char* ctor any more. huh. p

Re: LyX opening future versions

On 04/29/2011 10:11 AM, Julien Rioux wrote: Can I raise a question again? Why not always backport changes to lyx2lyx from trunk to branch? Of course branch releases will run slightly behind trunk, but not so badly that it would be useless to do this. Then, to some extent, the problem goes away,

Re: LyX opening future versions

On Fri, Apr 29, 2011 at 11:31 PM, Richard Heck rgh...@comcast.net wrote: I thought the original question was precisely about interoperability between the stable version and development versions. In that case, regularly porting lyx2lyx does help. Then again, this is probably a special case, and

RE: Too much options in LyX

> Hi. > > On Wed, Apr 27, 2011 at 02:07:55PM +0200, venom00 wrote: > > > +void GuiDocument::hideView() { > > > + Dialog::hideView(); > > > + // Reset the search box > > > + this->docPS->resetSearch(); > > > +} > > Style nits: { on a separate line for the function body, and this-> > seems

Re: Trunk is completely frozen for any commits

compiled and ran successfully on ubuntu. On Fri, Apr 29, 2011 at 1:23 AM, venom00 wrote: > > Local control tower: giving permission to land. > > Over. > > One small step for a bunch of developers, a giant leap for mankind. > > venom00 > >

Re: Maintenance release management

On 04/29/2011 07:50 AM, Jürgen Spitzmüller wrote: Dear all, as you all know meanwhile, I will step back as maintenance release manager as soon as LyX 1.6.10 is released. I'm glad to inform you that Richard accepted to take over maintenance release management. This is an excellent solution,

Re: Maintenance release management

Abdelrazak Younes wrote: > Excellent solution indeed. Thanks for accepting the duty Richard! > > Many thanks to you; you really did an amazing work! hear, hear! ed.

Re: Development for LyX 2.1

> Anyway, I don't think heavy use of branches is required or needed with > git. I am currently involved with two largish projects using git, one > near the "branches everywhere" extreme and the other close to "the > history should be linear" end... Just out of curiosity, do you mind sharing

RE: #7493 and preview-latex in general

> Bug #7493 is not preview-latex fault. We didn't drop preview-latex > before even when it caused a bug. I can imagine dropping it > eventually, > but it's still useful to get automatic bounding box, isn't it?. If I'm correct that's true just for the pdflatex route. I was thinking of the

Re: Maintenance release management

Jürgen Spitzmüller wrote: > Let me take the opportunity to thank everybody for the support over the last > 4 > years. thanks for your good job, both 1.5 & 1.6 releases were pleasure to work with. pavel

Re: Maintenance release management

Le 29/04/2011 12:13, Pavel Sanda a écrit : Jürgen Spitzmüller wrote: Let me take the opportunity to thank everybody for the support over the last 4 years. thanks for your good job, both 1.5& 1.6 releases were pleasure to work with. I hope that Juergen already knows what I think, but let me

Re: #7506: CopyStyle for inset layout does not work

On 2011-4-29 7:07 , LyX Ticket Tracker wrote: #7506: CopyStyle for inset layout does not work Comment(by rgheck): I'll have to check this with current trunk. But I'm guessing that the issue is just that the new layouts were not named properly, yet the layout format is beyond where lyx2lyx

RE: Too much options in LyX

> Style and form comments are always welcome but please give a > little attention to the content too: > - Alternative ideas to highlight matching widgets? Currently > they become red. > - Ideas on how to make the research faster? In the next patch > I'll try to add a little delay. Here's the

Re: Maintenance release management

On 29/04/2011 6:41 AM, Jean-Marc Lasgouttes wrote: Le 29/04/2011 12:13, Pavel Sanda a écrit : Jürgen Spitzmüller wrote: Let me take the opportunity to thank everybody for the support over the last 4 years. Thanks for a job very well done Jürgen. thanks for your good job, both 1.5& 1.6

Re: #7493 and preview-latex in general

On 29/04/2011 5:38 AM, venom00 wrote: Bug #7493 is not preview-latex fault. We didn't drop preview-latex before even when it caused a bug. I can imagine dropping it eventually, but it's still useful to get automatic bounding box, isn't it?. If I'm correct that's true just for the pdflatex

Re: LyX opening future versions

Il 29/04/2011 05:02, Richard Heck ha scritto: There's an even better solution: Copy current lyx2lyx from trunk. So let me ask this question: Is there any real reason not to backport lyx2lyx to branch as it changes? Well, trunk is affected by that problem as well: create the simplest LyX

Re: LyXHTML image resolution

Hi Ramin, > I'm using 2.0 to export html which I can then convert to epub format > with Calibre. I've been playing with the same export. So far I've been really happy. Rather than using Calibre to do the conversion, you might take a look at Sigil. It creates a much cleaner ePub (though Calibre

Re: LyX opening future versions

Il 29/04/2011 06:09, Liviu Andronic ha scritto: On Fri, Apr 29, 2011 at 5:02 AM, Richard Heck wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I

Re: LyX opening future versions

Le 29/04/2011 15:25, Tommaso Cucinotta a écrit : Il 29/04/2011 05:02, Richard Heck ha scritto: There's an even better solution: Copy current lyx2lyx from trunk. So let me ask this question: Is there any real reason not to backport lyx2lyx to branch as it changes? Well, trunk is affected by

Re: LyX opening future versions

Oops! message sent too fast! Next part. Le 29/04/2011 15:34, Jean-Marc Lasgouttes a écrit : Le 29/04/2011 15:25, Tommaso Cucinotta a écrit : I don't know whether lyx2lyx is designed to solely upgrade the file format, or also to downgrade it, because in the former case it wouldn't help. Of

Re: LyX opening future versions

Tommaso Cucinotta wrote: What is wrong with such an approach ? >> The data loss thingy: it's very dangerous and naive users (but even >> developers!) could suffer. > > As far as the user is notified, I can't see a real problem here unnoticed dataloss in your conversion step seems to me

Re: Maintenance release management

On 04/29/2011 09:20 AM, Julien Rioux wrote: On 29/04/2011 6:41 AM, Jean-Marc Lasgouttes wrote: I hope that Juergen already knows what I think, but let me concur that he has been the right man for the job. And I suspect that I will be able to say the same about Richard in XX years when he'll

Re: LyX opening future versions

On 04/29/2011 09:53 AM, Pavel Sanda wrote: Tommaso Cucinotta wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't see a real problem here unnoticed dataloss in your

Re: LyX opening future versions

On 29/04/2011 10:03 AM, Richard Heck wrote: On 04/29/2011 09:53 AM, Pavel Sanda wrote: Tommaso Cucinotta wrote: What is wrong with such an approach ? The data loss thingy: it's very dangerous and naive users (but even developers!) could suffer. As far as the user is notified, I can't see a

Re: Maintenance release management

Le 29/04/2011 15:54, Richard Heck a écrit : Yes, we hope for double digits years. I was wondering about that myself. :) The goal is actually the opposite: have a short enough term for maintainers, so that they don't burn out and can do the job again later. JMarc

RE: Maintenance release management

> Dear all, > > as you all know meanwhile, I will step back as maintenance > release manager as > soon as LyX 1.6.10 is released. > > I'm glad to inform you that Richard accepted to take over > maintenance release > management. This is an excellent solution, IMHO. > > Let me take the

Re: LyX opening future versions

On Fri, Apr 29, 2011 at 9:11 AM, Julien Rioux wrote: > On 29/04/2011 10:03 AM, Richard Heck wrote: >>> couldn't you give your colleagues file exported to 1.6 on your side? A possible solution would be to imitate what Openoffice does (and perhaps Microsoft word as

Re: Trunk is completely frozen for any commits

Just adding to the chorus: compiled and run successfully on Kubuntu Maverick Stefano

Re: Development for LyX 2.1

On 28.04.2011 22:49, Enrico Forestieri wrote: On Thu, Apr 28, 2011 at 11:23:29AM -0600, Rob Oakes wrote: It sounds as though consensus is emerging. Would it be possible to have the the git master branch mirrored into the existing SVN repository? This would make it easy for those of us trying

Re: Trunk is completely frozen for any commits

On 29.04.2011 17:03, stefano franchi wrote: Just adding to the chorus: compiled and run successfully on Kubuntu Maverick Stefano Also ok: - Ubuntu 11.4 - Scientific Linux 6 - openSuse 11.4, but monolithic build is broken Peter

Re: Trunk is completely frozen for any commits

Am 29.04.2011 um 03:18 schrieb Pavel Sanda: > Richard Heck wrote: >> On 04/28/2011 08:21 PM, Pavel Sanda wrote: >>> dear passengers, please fasten your seatbelts. >>> >> Fasten Seat Belts > > tarballs temporarily uploaded here: > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/2.0.0/ > > i'm waiting

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: > - openSuse 11.4, but monolithic build is broken whats the error message? pavel

Re: Trunk is completely frozen for any commits

Original-Nachricht > Datum: Fri, 29 Apr 2011 18:08:55 +0200 > Von: Pavel Sanda > An: lyx-devel@lists.lyx.org > Betreff: Re: Trunk is completely frozen for any commits > Peter Kümmel wrote: > > - openSuse 11.4, but monolithic build is broken > > whats the error

Re: Trunk is completely frozen for any commits

Pavel Sanda wrote: > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/2.0.0/ > other people please send me ack that you have been able to build/run lyx 2.0.0 successfully successful landing Compiled and run successfully on Ubuntu Natty thanks to all developers Best Ignacio García

Re: Trunk is completely frozen for any commits

On Fri, Apr 29, 2011 at 6:18 PM, Peter Kuemmel wrote: > There are no problems with GCC 4.5.2 (Ubuntu 11.4) > also not with GCC 4.6.0 (Fedora 15) works. > Neither with GCC 4.4.3 and Qt 4.6.2 on Xubuntu 10.04 (Lucid). Liviu

Re: LyX opening future versions

Richard Heck wrote: > It shouldn't. One loses data in the sense that insets can get converted to > ERT, but you shouldn't lose data in any other sense. there are features which are lost during the conversion back simply because there is nothing comparable in previous versions. secondly if we do

Re: Trunk is completely frozen for any commits

Stephan Witt wrote: > 2) polish the dmg a little bit - add some readme etc. take your time. p

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: > Original-Nachricht > > Datum: Fri, 29 Apr 2011 18:08:55 +0200 > > Von: Pavel Sanda > > An: lyx-devel@lists.lyx.org > > Betreff: Re: Trunk is completely frozen for any commits > > > Peter Kümmel wrote: > > > - openSuse 11.4, but monolithic

Re: Trunk is completely frozen for any commits

On 29.04.2011 18:38, Pavel Sanda wrote: Peter Kümmel wrote: Original-Nachricht Datum: Fri, 29 Apr 2011 18:08:55 +0200 Von: Pavel Sanda An: lyx-devel@lists.lyx.org Betreff: Re: Trunk is completely frozen for any commits Peter Kümmel wrote: - openSuse 11.4,

Re: Trunk is completely frozen for any commits

Peter Kümmel wrote: > I also don't like the patch. I first tried docstring("btPrintNotCited") but > gcc doesn't know the const char* ctor any more. huh. p

Re: LyX opening future versions

On 04/29/2011 10:11 AM, Julien Rioux wrote: Can I raise a question again? Why not always backport changes to lyx2lyx from trunk to branch? Of course branch releases will run slightly behind trunk, but not so badly that it would be useless to do this. Then, to some extent, the problem goes away,

Re: LyX opening future versions

On Fri, Apr 29, 2011 at 11:31 PM, Richard Heck wrote: > I thought the original question was precisely about interoperability between > the stable version and development versions. In that case, regularly porting > lyx2lyx does help. Then again, this is probably a special case,