Am Dienstag, 5. Dezember 2006 18:46 schrieb Bo Peng:
> 1. Theoretically, we may have more frontends later so it does not make
> sense to remove this option. I mean, the most you can do is making qt4
> the default frontend.
I did not mean to remove this option. Making qt4 the default is perfectly
PS: Bo, making a bug WONTFIX does not help much in this case. We knew
it would have to be done, but it was not high priority.
My concern was that Status.15x was getting too big. Going through the
not-for-1.5.0 ones (again and again) is a waste of time.
I also notice that some items are not repr
On Tuesday 05 December 2006 5:54 pm, Jean-Marc Lasgouttes wrote:
>
> OK, what about that?
If it works you can commit it.
> JMarc
>
> PS: Bo, making a bug WONTFIX does not help much in this case. We knew
> it would have to be done, but it was not high priority.
--
José Abílio
On Wed, Dec 06, 2006 at 11:46:21AM +1800, Bo Peng wrote:
> 1. Theoretically, we may have more frontends later so it does not make
> sense to remove this option. I mean, the most you can do is making qt4
> the default frontend.
Theoretically I've already rewritten LyX in Python. Hurrah!
> 2. I do
copy)
@@ -9,7 +9,7 @@ These four steps will compile, test and
0) Linux users beware: if compiling the Qt frontend, you need
qt and qt-devel packages of the same version to compile LyX.
- 1) ./configure --with-frontend=qt4
+ 1) ./configure
configures LyX according to your syst
Hi, Georg,
If anybody moves this to WONTFIX again I'll get really upset.
Does nobody see how ridiculous it is to require the user to choose
the one existing frontend? If this does not get fixed for 1.5.0
we'll get many complaints, and a bad reputation.
I do not see your points.
1. Theoretical
patch, but I hope it makes this unnecessary.
>
> Doesn't lyx use pkg-config to determine qt4 config'ness? If it did, it
> should "just work" (on Fedora Core 4+ anyway).
On Debian/testing, installing libqt4-dev (with a bit of concern, as the
dependencies triger quite an inte
On Monday 23 October 2006 15:54, Jean-Marc Lasgouttes wrote:
> Supposedly, we will be allowed to have several frontends again some
> day. Not that I count on it.
You are forgetting qt5. ;-)
PS: We thought about removing qt4 as well, or at least putting it in a
branch of its own. ;-)
PPS:
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Because someone already removed all the other options. There's
John> no point being able to select from one mandatory option.
Supposedly, we will be allowed to have several frontends again some
day. Not that I count on it.
JMarc
Martin Vermeer wrote:
> In order to build the qt4 front-end, you should either define QT4DIR on
> the command line before configure, or use the --with-qt4-dir switch. I
> haven't checked John's patch, but I hope it makes this unnecessary.
Doesn't lyx use pkg-config to determine qt4 config'ness?
On Mon, Oct 23, 2006 at 03:36:18PM +0300, Martin Vermeer wrote:
> As for getting rid of --with-frontend, I am squarely against that. Sure,
> by all means make qt4 the default. It is not about keeping up the
> pretence of multiple front-ends; rather, it is about keeping an easy
> ca
On Mon, 2006-10-23 at 11:39 +0200, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Mon, Oct 23, 2006 at 10:28:08AM +0100, John Levon wrote:
> |
> | > configure: error: "Please select a frontend using --with-frontend"
> |
> |
On Mon, Oct 23, 2006 at 11:40:16AM +0200, Jean-Marc Lasgouttes wrote:
> Lars> John Levon <[EMAIL PROTECTED]> writes: | configure: error:
> Lars> "Please select a frontend using --with-frontend"
> Lars> |
> Lars> | Can we remove this now please?
>
>
>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> John Levon <[EMAIL PROTECTED]> writes: | configure: error:
Lars> "Please select a frontend using --with-frontend"
Lars> |
Lars> | Can we remove this now please?
John Levon <[EMAIL PROTECTED]> writes:
| On Mon, Oct 23, 2006 at 10:28:08AM +0100, John Levon wrote:
|
| > configure: error: "Please select a frontend using --with-frontend"
|
| And the config needs fixing to just work on Fedora 4. It can't find qt4
| at all.
Are you s
On Mon, Oct 23, 2006 at 11:31:09AM +0200, Lars Gullik Bjønnes wrote:
> | configure: error: "Please select a frontend using --with-frontend"
> |
> | Can we remove this now please?
>
> I am not sure that we should.
Why? You'd like to maintain the pretence that we
On Mon, Oct 23, 2006 at 10:28:08AM +0100, John Levon wrote:
> configure: error: "Please select a frontend using --with-frontend"
And the config needs fixing to just work on Fedora 4. It can't find qt4
at all.
john
John Levon <[EMAIL PROTECTED]> writes:
| configure: error: "Please select a frontend using --with-frontend"
|
| Can we remove this now please?
I am not sure that we should.
--
Lgb
configure: error: "Please select a frontend using --with-frontend"
Can we remove this now please?
john
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> John Spray <[EMAIL PROTECTED]> writes:
| Revised patch attached.
Lars> This is ok.
I applied it. Thanks, John.
JMarc
John Spray <[EMAIL PROTECTED]> writes:
| Revised patch attached.
This is ok.
--
Lgb
used for the GUI])
AC_ARG_WITH(frontend,
[ --with-frontend=THISUse THIS frontend as main GUI:
- Possible values: xforms, qt],
+ Possible values: xforms, qt, gtk(EXPERIMENTAL)],
[FRONTENDS="$withval"], [FRONTENDS="xforms"])
AC_MSG_RESULT($FRONTENDS)
AC_SUBST(FRONTENDS)
John Spray <[EMAIL PROTECTED]> writes:
| Hi,
>
| Attached patch documents the --with-frontend=gtk option in INSTALL and
| "./configure --help". No point writing about it along the Qt frontend
| in most of the docs, but I think it should be mentioned at least
| somewhere (I h
Hi,
Attached patch documents the --with-frontend=gtk option in INSTALL and
"./configure --help". No point writing about it along the Qt frontend
in most of the docs, but I think it should be mentioned at least
somewhere (I had to check mailing list archives to even find out how to
On Mon, Aug 06, 2001 at 12:02:50PM +0200, Pascal Francq wrote:
> > messageboxes). I think we agreed on the following naming scheme (did we?):
> > > QXXX.[Ch]
> > > ui/QXXXDialog.[Ch]
> > > QXXXDialogImpl.[Ch]
> >
> > gr.ed.
>
> So, it is better if I wait a liitle bit before starting something?
> So, it is better if I wait a liitle bit before starting something?
No, just keep the naming scheme in mind when you decide to add stuff...
gr.ed.
On Friday 03 August 2001 14:53, Edwin Leuven wrote:
> > Is there enough people to work on the qt2 port.
>
> the more the merrier
>
> > I can perhaps spent a
> > little of my time to try to do some port of the dailogs to qt2.
>
> I think John is planning to do a renaming operation in the qt2 direct
> Is there enough people to work on the qt2 port.
the more the merrier
> I can perhaps spent a
> little of my time to try to do some port of the dailogs to qt2.
I think John is planning to do a renaming operation in the qt2 directory so
for the moment I am not touching it (and still breeding
John Levon <[EMAIL PROTECTED]> writes:
| On 25 Sep 2000, Jean-Marc Lasgouttes wrote:
|
| > > "John" == John Levon <[EMAIL PROTECTED]> writes:
| >
| > >> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck)
| >
| > John> and looking further I have found the answer. LyX specifi
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> JMarc, I will investigate exactly what breaks when
John> __STRICT_ANSI__ is defined later. I would like if possible to
John> leave this defined so we don't lie to header files ;)
It would indeed be much better...
JMarc
On 25 Sep 2000, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> >> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck)
>
> John> and looking further I have found the answer. LyX specifically
> John> removes this define (and in fact won't c
> "John" == John Levon <[EMAIL PROTECTED]> writes:
>> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck)
John> and looking further I have found the answer. LyX specifically
John> removes this define (and in fact won't compile with it). I
John> assume this won't change anytime
On Fri, 22 Sep 2000, John Levon wrote:
> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck)
>
> john
>
and looking further I have found the answer. LyX specifically removes this
define (and in fact won't compile with it). I assume this won't change
anytime soon, so I will just
On Thu, 21 Sep 2000, John Levon wrote:
> I have seen this myself. It is to do with Qt breaking by trying to use xor
> which is a keyword in standard c++. In my opinion this is a broken header
> used in Qt. For the benefit of the list the relevant section is :
>
> #if !(defined(__STRICT_ANSI__) &
On Thu, 21 Sep 2000, Edwin Leuven wrote:
> I get the following error message:
> /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src
>-I../../../src/ -I../../../src/frontends/-I../../.. -I../../.. -I./kde
>-I/usr/lib/qt-1.45/include -I/usr/include/kde -I../
When compiling lyx-devel, cvs sep 21, on a redhat 6.2 system, with
qt1x-1.45-3
qt1x-devel-1.45-3[
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
and doing
./configure --disable-nls --with-frontend=kde --with-qt-dir=/usr/lib/qt-1.45
I get the following error message:
/bin/sh
36 matches
Mail list logo
