Le 15/10/15 01:06, Scott Kostyshak a écrit :
LyX 2.2.0 and the following 2.2.x releases will still continue to work
well with Qt 4.8.6 but will also support Qt 5.6, which brings some
advantages most notably for users with HiDPI displays. Note that if you
compile LyX with a Qt 5 release before 5.6
On Fri, Dec 19, 2014 at 11:26:35AM -0500, Scott Kostyshak wrote:
> On Fri, Dec 19, 2014 at 4:40 AM, Benjamin Piwowarski wrote:
> > Hi to all,
> >
> > sorry for the long delay - I started to clean up python scripts to make them
> > compatible with both python 2 and 3 so there are no more issues wit
On Tue, Oct 13, 2015 at 07:37:58AM +0200, Stephan Witt wrote:
>
> Am 13.10.2015 um 02:56 schrieb Scott Kostyshak :
> > Stephan and Uwe do you forsee any packaging problems with using Qt 5.6
> > beta as opposed to Qt 5.5 ?
>
> No. I need only the required disk space and cpu resources to compile an
On Mon, Oct 12, 2015 at 10:38:02PM +0200, Vincent van Ravesteijn wrote:
> I guess that the release notes for 2.2 needs to be reconsidered anyhow.
> This excerpt was just copied from the 2.1 release notes. IIRC
Thanks for pointing this out. I cleaned the release notes after the 2.1
release but I k
On Wed, Oct 14, 2015 at 09:13:12PM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
> > Any other opinions?
OK sounds like there is enough of a consensus. From what I understand,
after explanations Liviu is now OK with this as well.
> No, I agree completely. In addition, if our alpha release fi
On Wed, Oct 14, 2015 at 07:50:54AM +0100, Guillaume Munch wrote:
> Scott asked not long ago what could be done to make it easier for
> newcomers.
Yes I am interested in this.
> It is now clear to me that having a clearer bug tracker
> is an aspect that can be improved.
Agreed.
> Taking into acc
On Wed, Oct 14, 2015 at 10:38:27PM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > Many export ctests are failing after this commit. One example is if you
> > open up the Additional.lyx manual and export to XHTML. I get a "LyX has
> > caught an exception" message. Or if you do it on the co
Le 14/10/15 22:35, Georg Baum a écrit :
*#2: Add a unique id to math insets.
Please measure memory consumption. I am a bit afraid that this increases
memory usage a lot, since math insets contain very tiny bits of information,
and you may need _lots_ of them even for simple formula.
I agree w
Scott Kostyshak wrote:
> Many export ctests are failing after this commit. One example is if you
> open up the Additional.lyx manual and export to XHTML. I get a "LyX has
> caught an exception" message. Or if you do it on the command line I get:
>
> $ lyx -e xhtml Additional.lyx
> Error 2
Guillaume Munch wrote:
> I submit it on the list to get your agreement on several fundamental
> changes which I kept, as you will see, as little intrusive as possible.
Wow, these are lots of changes. I am running out of time and will only
comment on some.
> The sensitive changes (i.e. where I h
David Hyde wrote:
> I'm interested in looking into this at least a bit (may become deterred
> if some dependency nightmare occurs!). I've looked at the current MSVC
> dependencies that are in the archive on sourceforge. Which of these
> are things that should actually be downloaded and compiled
Scott Kostyshak wrote:
> On Tue, Oct 13, 2015 at 06:31:04PM +, Guenter Milde wrote:
>> On 2015-10-12, Jean-Marc Lasgouttes wrote:
>>
>> > We can live with a few missing messages on lyx-cvs, as long as this
>> > gets sorted out eventually.
>>
>> > I propose that you commit your patches yourse
Vincent van Ravesteijn wrote:
> Op 12-10-2015 om 4:17 schreef Scott Kostyshak:
>> On Sun, Oct 11, 2015 at 11:20:15AM +0200, Georg Baum wrote:
>>> commit cea2d71e641e6a4023128a367d1cd5a593ed1706
>>> Author: Georg Baum
>>> Date: Sun Oct 11 11:16:09 2015 +0200
>>>
>>> Comply with rule-of-thre
Scott Kostyshak wrote:
> On Tue, Oct 13, 2015 at 09:20:49AM +0900, Cyrille Artho wrote:
>>
>> In that case it's a good opportunity to test Qt 5.6 with the next alpha
>> release.
>
> Sounds good. Do note though that it would be Qt 5.6 *beta*. I still
> think it makes sense to test our alpha with t
Jean-Marc Lasgouttes wrote:
> Le 11/10/2015 12:43, Guillaume Munch a écrit :
>>> Qt 5.6.0 will probably be released before LyX 2.2.0. Therefore the most
>>> simple solution would be to disable IBus if an older qt is detected (at
>>> runtime) and mention in the release notes that korean users need
Le 14/10/2015 07:27, David Hyde a écrit :
Which of these
are things that should actually be downloaded and compiled on the fly?
For example, do you think that Python and ghostscript should be
compiled from source, or do you think it suffices to just include up-to
-date Windows binaries? Same q
Hi guys,
I'm toying with the idea of making a (basic) card-based (one paragraph per
card) LaTeX editor with Qt Quick for my Bachelors thesis and using Lyx as a
basis. I'm in my third year of studying IT, but have basically no real-world
experience when it comes to coding.
Do you think this is a
Am 14.10.2015 um 10:31 schrieb Jean-Marc Lasgouttes :
> Le 14/10/2015 10:16, Stephan Witt a écrit :
>> Am 14.10.2015 um 09:59 schrieb Jean-Marc Lasgouttes :
>>
>>> Le 14/10/2015 08:02, Stephan Witt a écrit :
But I don't believe the effect of the clipped cached pixmaps is caused by
this
Am Dienstag, 13. Oktober 2015 um 16:48:15, schrieb Scott Kostyshak
> On Tue, Oct 13, 2015 at 02:03:22PM +0200, Kornel Benko wrote:
> > I'd like to add them to cmake export tests too.
> >
> > They are there since 2008, good test for lyx 1.5 files.
>
> Sounds good but can you wait a couple of wee
On Wed, Oct 14, 2015 at 7:55 AM, Guillaume Munch wrote:
>> the hard truth is that our manpower is limited and our devels barely
>> have the bandwidth to address crashes, regressions and the like (in
>> between monitoring tickets, triaging, helping on the MLs, and
>> implementing things sorely ne
Le 14/10/2015 10:16, Stephan Witt a écrit :
Am 14.10.2015 um 09:59 schrieb Jean-Marc Lasgouttes :
Le 14/10/2015 08:02, Stephan Witt a écrit :
But I don't believe the effect of the clipped cached pixmaps is caused by this.
I gave not enough information - to spare email size the posted screen s
Am 14.10.2015 um 09:59 schrieb Jean-Marc Lasgouttes :
> Le 14/10/2015 08:02, Stephan Witt a écrit :
>> But I don't believe the effect of the clipped cached pixmaps is caused by
>> this. I gave not enough information - to spare email size the posted screen
>> shots are to small to see it - the ef
Le 14/10/2015 08:02, Stephan Witt a écrit :
But I don't believe the effect of the clipped cached pixmaps is caused by this.
I gave not enough information - to spare email size the posted screen shots are
to small to see it - the effect isn't there globally. It happens on some line
ends and on
Le 14/10/2015 07:53, Pavel Sanda a écrit :
Guillaume Munch wrote:
I remember putting the remark about low priority in FAQ.
Here's all I could find about "enhancement" or "priority" on Trac, the
website, the wiki and the repository (with git grep):
?Enhancements have low priority and minor sev
24 matches
Mail list logo
