On Mon, Apr 21, 2008 at 08:22:11PM -0400, rgheck wrote:
> Can you redirect me to the script?
It's in the repository: development/tools/lyxpak.py
> I'm doing some conceptual work on a different approach, more along the
> lines of what JMarc suggested. I'll be doing that in a private branch,
> s
Enrico Forestieri wrote:
On Mon, Apr 21, 2008 at 02:57:58PM -0400, Richard Heck wrote:
Martin Vermeer wrote:
I think it would be good to start from Enrico's script, as it doesn't
add complexity to the core.
There's no reason not to have such a script. Indeed, it could b
On Mon, Apr 21, 2008 at 02:57:58PM -0400, Richard Heck wrote:
> Martin Vermeer wrote:
> > I think it would be good to start from Enrico's script, as it doesn't
> > add complexity to the core.
> >
> >
> There's no reason not to have such a script. Indeed, it could be
> integrated into LyX via
>>> What I lack right now is time, and I don't expect to have very much until
>>> mid-May. (After final exams.) I don't think this will be very hard, but
>>> it will take a little while, at least.
>>>
>>
>> what is your opinion about postponing this to 1.7 ?
>>
>>
> We keep crossing messa
Pavel Sanda wrote:
What I lack right now is time, and I don't expect to have very much until
mid-May. (After final exams.) I don't think this will be very hard, but it
will take a little while, at least.
what is your opinion about postponing this to 1.7 ?
We keep crossing messages...
José Matos wrote:
On Monday 21 April 2008 13:31:17 Pavel Sanda wrote:
which is the key question. in case embedding is going to be part of 1.6
then my estimate is + 3 month of release delay.
IMHO it depends on what is going on.
Take Enrico's script as an example, if it goes in I don
> What I lack right now is time, and I don't expect to have very much until
> mid-May. (After final exams.) I don't think this will be very hard, but it
> will take a little while, at least.
what is your opinion about postponing this to 1.7 ?
pavel
Martin Vermeer wrote:
On Mon, 21 Apr 2008 13:42:17 +0100
José Matos <[EMAIL PROTECTED]> wrote:
On Monday 21 April 2008 13:31:17 Pavel Sanda wrote:
which is the key question. in case embedding is going to be part of 1.6
then my estimate is + 3 month of release delay.
IMHO it d
José Matos wrote:
On Monday 21 April 2008 12:17:53 Pavel Sanda wrote:
i agree that the code movements bring new bugs but its wrong to complain to
devs about playing with the code. the pressure should be imposed on the
release manager which in some moment decides to release, which stops
develo
> my own feeling is, that i would like to see 1.6 out more than having embed
> feature.
Also my opinion. Before we delay LyX 1.6 by months, we should postpone the embedding feature to LyX
1.7. We have enough features for the next release, there is no urgent reason why to add more new
features l
> (possible compromise would be to make it experimental and _not_ visible to
> normal users, so
p
On Mon, 21 Apr 2008 13:42:17 +0100
José Matos <[EMAIL PROTECTED]> wrote:
> On Monday 21 April 2008 13:31:17 Pavel Sanda wrote:
> > which is the key question. in case embedding is going to be part of 1.6
> > then my estimate is + 3 month of release delay.
>
> IMHO it depends on what is going on.
> > which is the key question. in case embedding is going to be part of 1.6
> > then my estimate is + 3 month of release delay.
>
> IMHO it depends on what is going on.
> Take Enrico's script as an example, if it goes in I don't expect a delay of
> 3 months. :-)
i dont believe it. alpha rele
On Monday 21 April 2008 13:31:17 Pavel Sanda wrote:
> which is the key question. in case embedding is going to be part of 1.6
> then my estimate is + 3 month of release delay.
IMHO it depends on what is going on.
Take Enrico's script as an example, if it goes in I don't expect a delay of
3 mo
Pavel Sanda wrote:
the only
question is we will have an embedding feature tracking the different ideas
that come during the different threads.
which is the key question. in case embedding is going to be part of 1.6 then
my estimate is + 3 month of release delay.
As a first step, mayb
> the only
> question is we will have an embedding feature tracking the different ideas
> that come during the different threads.
which is the key question. in case embedding is going to be part of 1.6 then
my estimate is + 3 month of release delay.
pavel
On Monday 21 April 2008 12:17:53 Pavel Sanda wrote:
>
> i agree that the code movements bring new bugs but its wrong to complain to
> devs about playing with the code. the pressure should be imposed on the
> release manager which in some moment decides to release, which stops
> development and star
>>> Besides this, we are on the way to stabilize LyX.
>> Are we?
>
> Yes! We discussed this topic two weeks ago and since then we have a release
> schedule. We are feature ready!
to be frank i have seen already three release dates and not single one was
adhered (imho from good reasons), so talks
Andre Poenitz schrieb:
I do not feel responsible for scons. So far the autotool build chain
is the chosen one. If you want scons to take over, make it feature
complete.
All other developers take care of SCons. I just need a build system to
compile LyX.
Besides this, we are on the way to stab
Andre Poenitz schrieb:
I do not feel responsible for scons. So far the autotool build chain
is the chosen one. If you want scons to take over, make it feature
complete.
All other developers take care of SCons. I just need a build system to compile
LyX.
Besides this, we are on the way to sta
On Mon, Apr 21, 2008 at 12:55:39AM +0200, Uwe Stöhr wrote:
> André,
>
> you haven broken the compilation again:
>
> D:\LyXSVN\lyx-devel\src\frontends\qt4\FileDialog.cpp(91) : error C3861:
> 'makeAbs
> Path': identifier not found
> D:\LyXSVN\lyx-devel\src\frontends\qt4\FileDialog.cpp(94) : error C2
André,
you haven broken the compilation again:
D:\LyXSVN\lyx-devel\src\frontends\qt4\FileDialog.cpp(91) : error C3861: 'makeAbs
Path': identifier not found
D:\LyXSVN\lyx-devel\src\frontends\qt4\FileDialog.cpp(94) : error C2664: 'QFileDi
alog::getSaveFileName' : cannot convert parameter 4 from 'c
22 matches
Mail list logo