On 2-5-2011 3:15, Andre Poenitz wrote:
> On Mon, May 02, 2011 at 12:58:59AM +0200, Pavel Sanda wrote:
>> [...]
>> my fear is also that while the extensive branch usage is superior from
>> the geeky point of view, its hindrance for people not so technically
>> skilled. do we want only geeks to be ar
Hi Joost,
I want to use the lib/images/banner.png as background image of the disk image
of the Mac distribution.
Do you have a vector graphics version of it or a version with higher resolution?
I'm not sure who is the original author of the banner image...
Stephan
On Sun, May 1, 2011 at 10:33 AM, Vincent van Ravesteijn wrote:
> On 1-5-2011 16:28, BH wrote:
>> I haven't tried compiling branch in a while, but trying today leads to
>> a compile error (using Qt-4.4):
>
>
> This is the error:
>
> "This file was generated using the moc from 4.7.1. It
> cannot be
On Mon, May 02, 2011 at 12:58:59AM +0200, Pavel Sanda wrote:
> [...]
> my fear is also that while the extensive branch usage is superior from
> the geeky point of view, its hindrance for people not so technically
> skilled. do we want only geeks to be around?
> [...]
Very good point. I don't think
I think it is a good idea to have commits on a rather fine granularity,
such that each commit represents one independent feature, bug fix, or
refactoring. A feature can be much smaller than a user-visible feature,
for example, just a small enhancement or new function; it may also be a
set of new t
On Mon, May 02, 2011 at 12:58:53AM +0200, Pavel Sanda wrote:
> Peter Kümmel wrote:
> >> - Less noise in commits: a new feature in SVN sometimes comprises over 20
> >> commits in
> ..
> > The commits are the beats of LyX's development heart, so why kill them.
>
> there is actually something on this
Pavel Sanda wrote:
> 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 send me
Dear developers
I just compile lyx-2.0.0 in my netbook running Ubuntu 10.10.
The problem is related to the LyX: Preferences window:
- The height is too high so that I cannot see the buttons at the
bottom. The size of the LyX: Document Settings window is ok.
therefore my request is to make the hei
On 2011-05-01, Richard Heck wrote:
... [Resons for not up-and-downgrading on a regular basis] ...
> People who want to collaborate with users of earlier versions (or use
> development versions for their own work, etc) should have the users of
> those earlier versions install their (newer) version
Peter Kümmel wrote:
>> - Less noise in commits: a new feature in SVN sometimes comprises over 20
>> commits in
..
> The commits are the beats of LyX's development heart, so why kill them.
there is actually something on this.
its good idea that having some "final" tree where 1 feature=1 commit.
it
Julien Rioux wrote:
>>> a) make new code available early
i have been thinking about the proposed changes last couple of days
and from many small things the main issue occuring to me again and
again is that the new model of each 6 months release is going to be
harmful for the overall stability of
Richard Heck wrote:
> etc, but I'm not sure we really want to people to try to collaborate
> across major versions and then start reporting bugs when it doesn't work.
+1
pavel
Diego Queiroz wrote:
> Is there some consensus about what version of Python LyX scripts should be
> compatible?
consensus is that we dont support python 3. so 2.6 code should be fine.
pavel
On 05/01/2011 04:49 PM, Jean-Marc Lasgouttes wrote:
> Le 30/04/11 15:38, Richard Heck a écrit :
>>> Would it be difficult to automate this? I was thinking that the best
>>> solution to the problem, from a LyX point of view, was to provide---in
>>> addition to the current message---a button that wou
On Sun, May 1, 2011 at 11:41 PM, Liviu Andronic wrote:
> On Sun, May 1, 2011 at 10:54 PM, venom00 wrote:
>> This requires a "permanent" connection to the Internet while LyX is an
>> offline
>> application.
>>
> This might actually work: after receiving a problematic LyX file by
> e-mail make sur
On Sun, May 1, 2011 at 10:54 PM, venom00 wrote:
> This requires a "permanent" connection to the Internet while LyX is an offline
> application.
>
This might actually work: after receiving a problematic LyX file by
e-mail make sure that you have an internet connection for couple more
minutes. :) Th
On Sat, Apr 30, 2011 at 02:41:55PM +0200, Pavel Sanda wrote:
> hi all,
>
> some stats for 2.0 development.
> (you will need mail client with fixed chars & proper tabs handling).
>
> * commit activity:
>
> Trunk 2.0: ...
>
> ...
> [...]
> ... 38 ...
> ...
*gosh*
This makes the release look
>> However, you should then set the text in the textfield and then
>> manually reset all widgets to enabled. This means you have to either
>> block the signals, but better .. listen to textEdited instead of
>> textChanged.
>>> +
>>> + connect(search_, SIGNAL(textChanged(QString)), this,
>>> SLOT(
> IMO the problem is more what happens when someone hits this
> button with
> LyX version 2.0 and current version is 4.1. Are we sure we
> have kept the
> same interface to lyx2lyx? Are we going to be bound by that forever?
Well, if we want to make big changes giving a new name to the file is
Le 30/04/11 15:38, Richard Heck a écrit :
Would it be difficult to automate this? I was thinking that the best
solution to the problem, from a LyX point of view, was to provide---in
addition to the current message---a button that would download most
recent lyx2lyx from SVN or trac and place it to
> hideView() doesn't work as this is only called when the Ok or Close
> button are pressed. Not when the dialog is canceled by Escape.
>
> Maybe you should put the resetSearch function in a showEvent function
> which is called when the dialog is shown.
OK, that's a good idea, this makes the patch
On 04/30/2011 09:14 PM, venom00 wrote:
>> I've looked briefly at this one before, and I find it confusing. It
>> looks as if it is saying that we are leaking the docstring
>> word itself,
>> i.e., that it's not being cleaned up, but why would that be?
> Mmmh, I find it pretty simple: we have some
On 1-5-2011 16:28, BH wrote:
> I haven't tried compiling branch in a while, but trying today leads to
> a compile error (using Qt-4.4):
This is the error:
"This file was generated using the moc from 4.7.1. It
cannot be used with the include files from this version of Qt.
(The moc has changed too
BH wrote:
> I haven't tried compiling branch in a while, but trying today leads to
> a compile error (using Qt-4.4):
Did you try with a make distclean'ed tree?
Jürgen
I haven't tried compiling branch in a while, but trying today leads to
a compile error (using Qt-4.4):
In file included from SignalSlotPrivate.cpp:15:
SignalSlotPrivate_moc.cpp:14:2: error: #error "This file was generated
using the moc from 4.7.1. It"
SignalSlotPrivate_moc.cpp:15:2: error: #error
On 29-4-2011 15:03, venom00 wrote:
>> 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
>
> I'm also glad that my only objection with the above list is
> c) develop new features in branches. I don't think it's necessary
> for most features, only for largish ones that are likely to take
> time and break the normal bug-free level in the main dev branch.
>
I understand that it sounds
On 28-4-2011 19:23, Rob Oakes wrote:
>> I'm happy to go with git, as long as we're all going to get this kind of
>> help.
>
> 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 f
28 matches
Mail list logo
