ok, thanks for the info. unless Vincent put it in, i will do before
beta goes out.
I looked at the patch again and in the Qt Docs and I read:
{{{
void QClipboard::dataChanged () [signal]
This signal is emitted when the clipboard data is changed.
On Mac OS X and with Qt version 4.3 or
Am Sonntag, den 17.10.2010, 18:28 +0200 schrieb Pavel Sanda:
John McCabe-Dansted wrote:
the most problematic cases of our copypaste typically happen when
middle button is used for getting, or puting stuff from/into another
applications and when more lyx instances are used. dunno whether
> ok, thanks for the info. unless Vincent put it in, i will do before
> beta goes out.
>
I looked at the patch again and in the Qt Docs and I read:
{{{
void QClipboard::dataChanged () [signal]
This signal is emitted when the clipboard data is changed.
On Mac OS X and with Qt version 4.3 or
Am Sonntag, den 17.10.2010, 18:28 +0200 schrieb Pavel Sanda:
> John McCabe-Dansted wrote:
> > > the most problematic cases of our copy typically happen when
> > > middle button is used for getting, or puting stuff from/into another
> > > applications and when more lyx instances are used. dunno
Pavel Sanda wrote:
hi,
status update #1, the most urgent bug is gone.
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
- pending patch from Gregory Jefferis for CT, Vincent might have look on it.
Pavel Sanda wrote:
> hi,
status update #1, the most urgent bug is gone.
> 1) short resume for things we need before releasing beta
> - Richard has some pending work on lyx2lyx which will finish some JMarc work.
> - pending patch from Gregory Jefferis for CT, Vincent might have look on it.
John McCabe-Dansted wrote:
the most problematic cases of our copypaste typically happen when
middle button is used for getting, or puting stuff from/into another
applications and when more lyx instances are used. dunno whether
the patch affects these use cases... its very fragile stuff and
Pavel Sanda wrote:
Richard Heck wrote:
I've lost track, I'm afraid, of which patch set is which. Here's what I've
got.
i have flagged this message from JMarc in case it makes the things more clear:
I would like to have the newlineisparbreak part, which is important for
sweave support
i tried to be transparent and listed exactly 4 bugs which are in my opinion
before-beta stuff
So I missed this post from you but cannot find it in the archives. What are
these 4 bugs?
thanks and regards
Uwe
Uwe Stöhr wrote:
i tried to be transparent and listed exactly 4 bugs which are in my
opinion
before-beta stuff
So I missed this post from you but cannot find it in the archives. What are
these 4 bugs?
the first point of this thread
On 10/17/2010 12:52 PM, Pavel Sanda wrote:
Pavel Sanda wrote:
Richard Heck wrote:
I've lost track, I'm afraid, of which patch set is which. Here's what I've
got.
i have flagged this message from JMarc in case it makes the things more clear:
I would like to have the
Richard Heck wrote:
Richard, was the last movement in lyx2lyx fixing this or we wait for
something else?
No, that was JMarc's other request. I'll have a look early next week at
this bit.
thanks, give me hint once its finished ;)
pavel
to sum it up, beta is doable
at the end of October or on the very beginning of November - now for real.
Nice! But to assure that we achieve this can you close trunk for new features soon? Trunk should
only be open for bugfixes and documentation.
regards Uwe
Op 17-10-2010 20:31, Uwe Stöhr schreef:
to sum it up, beta is doable
at the end of October or on the very beginning of November - now for
real.
Nice! But to assure that we achieve this can you close trunk for new
features soon? Trunk should only be open for bugfixes and documentation.
Uwe Stöhr wrote:
Nice! But to assure that we achieve this can you close trunk for new
features soon? Trunk should only be open for bugfixes and documentation.
basically it is releasing beta which makes closure for new features. its not
such big deal if there are bugs in beta1, everybody will
Am 17.10.2010 21:57, schrieb Vincent van Ravesteijn:
Why would closing trunk for new features _assure_ getting a beta out ?
This prevents us from introducing new bugs and regressions. (An example of a newly introduced
regression is for example http://www.lyx.org/trac/ticket/6943)
At some
John McCabe-Dansted wrote:
> > the most problematic cases of our copy typically happen when
> > middle button is used for getting, or puting stuff from/into another
> > applications and when more lyx instances are used. dunno whether
> > the patch affects these use cases... its very fragile stuff
Pavel Sanda wrote:
> Richard Heck wrote:
> > I've lost track, I'm afraid, of which patch set is which. Here's what I've
> > got.
>
> i have flagged this message from JMarc in case it makes the things more clear:
>
> >I would like to have the newlineisparbreak part, which is important for
>
> i tried to be transparent and listed exactly 4 bugs which are in my opinion
> before-beta stuff
So I missed this post from you but cannot find it in the archives. What are
these 4 bugs?
thanks and regards
Uwe
Uwe Stöhr wrote:
> > i tried to be transparent and listed exactly 4 bugs which are in my
> opinion
> > before-beta stuff
>
> So I missed this post from you but cannot find it in the archives. What are
> these 4 bugs?
the first point of this thread
On 10/17/2010 12:52 PM, Pavel Sanda wrote:
Pavel Sanda wrote:
Richard Heck wrote:
I've lost track, I'm afraid, of which patch set is which. Here's what I've
got.
i have flagged this message from JMarc in case it makes the things more clear:
I would like to have the
Richard Heck wrote:
>> Richard, was the last movement in lyx2lyx fixing this or we wait for
>> something else?
>>
>>
> No, that was JMarc's other request. I'll have a look early next week at
> this bit.
thanks, give me hint once its finished ;)
pavel
> to sum it up, beta is doable
> at the end of October or on the very beginning of November - now for real.
Nice! But to assure that we achieve this can you close trunk for new features soon? Trunk should
only be open for bugfixes and documentation.
regards Uwe
Op 17-10-2010 20:31, Uwe Stöhr schreef:
> to sum it up, beta is doable
> at the end of October or on the very beginning of November - now for
real.
Nice! But to assure that we achieve this can you close trunk for new
features soon? Trunk should only be open for bugfixes and documentation.
Uwe Stöhr wrote:
> Nice! But to assure that we achieve this can you close trunk for new
> features soon? Trunk should only be open for bugfixes and documentation.
basically it is releasing beta which makes closure for new features. its not
such big deal if there are bugs in beta1, everybody will
Am 17.10.2010 21:57, schrieb Vincent van Ravesteijn:
Why would closing trunk for new features _assure_ getting a beta out ?
This prevents us from introducing new bugs and regressions. (An example of a newly introduced
regression is for example http://www.lyx.org/trac/ticket/6943)
At some
Uwe Stöhr wrote:
Uwe, I don't like the pressure you make.
Sorry. I don't want to pressurize anybody.
no problem, asked for feedback and got it :) your impulse closed many bug
yesterday so good move anyway.
i tried to be transparent and listed exactly 4 bugs which are in my opinion
On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted gma...@gmail.com wrote:
Hi, a patch for #6597 is sitting at:
http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
I'd like to get this patch in. We discussed the patch and agreed it
looked pretty reasonable, but there
BH wrote:
Would someone with MacOS X like to confirm that this patch doesn't
break pasting into LyX from other applications?
I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
Qt-4.7. Cutting and pasting both from LyX to other programs and from
other programs to LyX works
On Thu, Oct 14, 2010 at 11:53 PM, Pavel Sanda sa...@lyx.org wrote:
I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
Qt-4.7. Cutting and pasting both from LyX to other programs and from
other programs to LyX works fine from what I can see.
the most problematic cases of our
Am 14.10.2010 um 17:19 schrieb BH:
On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted gma...@gmail.com
wrote:
Hi, a patch for #6597 is sitting at:
http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
I'd like to get this patch in. We discussed the patch and agreed
Uwe Stöhr wrote:
> > Uwe, I don't like the pressure you make.
>
> Sorry. I don't want to pressurize anybody.
no problem, asked for feedback and got it :) your impulse closed many bug
yesterday so good move anyway.
i tried to be transparent and listed exactly 4 bugs which are in my opinion
On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted wrote:
> Hi, a patch for #6597 is sitting at:
> http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
>
> I'd like to get this patch in. We discussed the patch and agreed it
> looked "pretty reasonable",
BH wrote:
> > Would someone with MacOS X like to confirm that this patch doesn't
> > break pasting into LyX from other applications?
>
> I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
> Qt-4.7. Cutting and pasting both from LyX to other programs and from
> other programs to
On Thu, Oct 14, 2010 at 11:53 PM, Pavel Sanda wrote:
>> I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
>> Qt-4.7. Cutting and pasting both from LyX to other programs and from
>> other programs to LyX works fine from what I can see.
>
> the most problematic
Am 14.10.2010 um 17:19 schrieb BH:
> On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted
> wrote:
>> Hi, a patch for #6597 is sitting at:
>> http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
>>
>> I'd like to get this patch in. We discussed the patch
Uwe Stöhr wrote:
We should and cannot rely on others. Linux distribution and all together only
cover less than 10% of the whole PC market.
of course we are not anybody's slave. but we can do things in more or less
clever way as far as distros is concerned. thats why i want to have bugs solved
Hi, a patch for #6597 is sitting at:
http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
I'd like to get this patch in. We discussed the patch and agreed it
looked pretty reasonable, but there was some theoretical discussion
as to whether the patch would break cut-and-paste
Am 13.10.2010 um 15:16 schrieb Pavel Sanda:
Uwe Stöhr wrote:
We should and cannot rely on others. Linux distribution and all together only
cover less than 10% of the whole PC market.
of course we are not anybody's slave. but we can do things in more or less
clever way as far as distros is
Le 13 oct. 10 à 15:16, Pavel Sanda a écrit :
i see. so the question becomes how it is with funding from lyx
(JMarc?) and
I have no idea about the funding. Lars knows, or maybe José.
how many people would be interested in coming in nov/dec. (?)
some weekend is possible for me when i know it
Uwe Stöhr wrote:
> We should and cannot rely on others. Linux distribution and all together only
> cover less than 10% of the whole PC market.
of course we are not anybody's slave. but we can do things in more or less
clever way as far as distros is concerned. thats why i want to have bugs solved
Hi, a patch for #6597 is sitting at:
http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
I'd like to get this patch in. We discussed the patch and agreed it
looked "pretty reasonable", but there was some theoretical discussion
as to whether the patch would break
Am 13.10.2010 um 15:16 schrieb Pavel Sanda:
> Uwe Stöhr wrote:
>> We should and cannot rely on others. Linux distribution and all together only
>> cover less than 10% of the whole PC market.
>
> of course we are not anybody's slave. but we can do things in more or less
> clever way as far as
Le 13 oct. 10 à 15:16, Pavel Sanda a écrit :
i see. so the question becomes how it is with funding from lyx
(JMarc?) and
I have no idea about the funding. Lars knows, or maybe José.
how many people would be interested in coming in nov/dec. (?)
some weekend is possible for me when i know it
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
- pending patch from Gregory Jefferis for CT, Vincent might have look on it.
- dispatch fixes for #6417
- #6809 - converting to older LyX versions doesn't
Pavel Sanda wrote:
2) ideas how to deal with so many bugs we have
i was thinking that dev meeting could have this topic - to get rid at least
worst cases of bugs of 2.0svn. however there was no new message about the
freiburg party - do i understand correctly this idea is dead, right?
I really
On 10/12/2010 08:34 AM, Pavel Sanda wrote:
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
I've lost track, I'm afraid, of which patch set is which. Here's what
I've got.
One thing I remember is a
Richard Heck wrote:
I also remember there was something about passthru layouts and paragraph
breaks. I don't quite recall what that was, but it should be fairly easy,
if someone can remind me what I was supposed to do. ;-)
the original thread is here:
Jürgen Spitzmüller wrote:
Concerning the synchronouos release time: depends on what bugs show up in
branch. If we fix some critical bug in branch, we should not wait with the
release for the beta.
i was not so much concerned about _synchronous_ releases but with releasing
at least one
Richard Heck wrote:
I've lost track, I'm afraid, of which patch set is which. Here's what I've
got.
i have flagged this message from JMarc in case it makes the things more clear:
I would like to have the newlineisparbreak part, which is important for
sweave support and is a file format
Pavel Sanda wrote:
i was not so much concerned about synchronous releases but with releasing
at least one interim release before becoming more consevative...
Ah, OK. Then we are in line.
Jürgen
Uwe Stöhr wrote:
In my opinion we need the beta and feature freeze right now because
releasing beta every 2 weeks doesn't solve anything because the main problem is
not absence of bug reports but the fact that most of us have no time for fixing
them.
freezing is good idea and i already retarget
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
- pending patch from Gregory Jefferis for CT, Vincent might have look on it.
- dispatch fixes for #6417
- #6809 - converting to older LyX versions doesn't
Pavel Sanda wrote:
> 2) ideas how to deal with so many bugs we have
> i was thinking that dev meeting could have this topic - to get rid at least
> worst cases of bugs of 2.0svn. however there was no new message about the
> freiburg party - do i understand correctly this idea is dead, right?
I
On 10/12/2010 08:34 AM, Pavel Sanda wrote:
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
I've lost track, I'm afraid, of which patch set is which. Here's what
I've got.
One thing I remember is a
Richard Heck wrote:
> I also remember there was something about passthru layouts and paragraph
> breaks. I don't quite recall what that was, but it should be fairly easy,
> if someone can remind me what I was supposed to do. ;-)
the original thread is here:
Jürgen Spitzmüller wrote:
> Concerning the synchronouos release time: depends on what bugs show up in
> branch. If we fix some critical bug in branch, we should not wait with the
> release for the beta.
i was not so much concerned about _synchronous_ releases but with releasing
at least one
Richard Heck wrote:
> I've lost track, I'm afraid, of which patch set is which. Here's what I've
> got.
i have flagged this message from JMarc in case it makes the things more clear:
>I would like to have the newlineisparbreak part, which is important for
>sweave support and is a file format
Pavel Sanda wrote:
> i was not so much concerned about synchronous releases but with releasing
> at least one interim release before becoming more consevative...
Ah, OK. Then we are in line.
Jürgen
Uwe Stöhr wrote:
> In my opinion we need the beta and feature freeze right now because
releasing beta every 2 weeks doesn't solve anything because the main problem is
not absence of bug reports but the fact that most of us have no time for fixing
them.
freezing is good idea and i already
60 matches
Mail list logo