From: Michal Marek <mmarek@suse.cz>
To: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig qconf: port to QT4
Date: Mon, 07 Jun 2010 23:29:06 +0200 [thread overview]
Message-ID: <4C0D64A2.9020701@suse.cz> (raw)
In-Reply-To: <201006071912.54313.alexander.stein@informatik.tu-chemnitz.de>
On 7.6.2010 19:12, Alexander Stein wrote:
> Hello Michal,
>
> Am Montag 07 Juni 2010, 14:45:48 schrieb Michal Marek:
>> I've only very little experience with Qt 3 or 4. The patch basically
>> changes most QSomeClass to Q3SomeClass, which is the Qt3-compatible
>> wrapper around QSomeClass. Now is it possible to still support Qt3? E.g.
>> have a header file that #defines Q3SomeClass back to QSomeClass and does
>> similar with the Qt headers, would that be possible? I know that Qt4 has
>> be there for five years already, but if the cost of keeping support for
>> old userspace is not too hight, I would try it.
>
> I never thought about qt3 compatibility but It seems to me that renaming the
> qt3 compat classes and revert the header file name changes should suffice to
> compile against qt3 again. But then somebody else has to do the makefile magic
> to support both versions. Also which version should be prefered if both are
> available?
I'd say the Qt4 version, leaving the qt3 for those who have no other
option (and then letting it bitrot once the last user installs Qt4 :-)).
>> BTW, after applying your patch, make xconfig starts ok, but clicking in
>> the main menu does nothing, and if I close the close button, it does not
>> exit, but stops reacting to any input (but it still handles window
>> resize). The qt3 version would display the "Save changes?" dialog here.
>
> I can click in the window around and closing the window using the X button
> asks me about saving the changes. Which QT version do you use actually?
Strange, now it works fine. I'll play with it a bit more and then I'll
tell you for sure.
Michal
next prev parent reply other threads:[~2010-06-07 21:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1275846668-17863-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de>
2010-06-07 12:45 ` [PATCH] kconfig qconf: port to QT4 Michal Marek
2010-06-07 17:12 ` Alexander Stein
2010-06-07 18:01 ` Gene Heskett
2010-06-07 21:29 ` Michal Marek [this message]
2010-07-13 19:26 ` [PATCH v2] " Alexander Stein
2010-07-26 12:44 ` Michal Marek
2010-07-26 12:47 ` Michal Marek
2010-07-30 11:15 ` [PATCHi v3] " Alexander Stein
2010-08-01 14:32 ` Ed Tomlinson
2010-08-01 19:28 ` [PATCH] " Alexander Stein
2010-08-02 12:01 ` Ed Tomlinson
2010-09-18 14:22 ` Ed Tomlinson
2010-09-20 12:03 ` Michal Marek
2010-09-21 17:31 ` [PATCH 1/2] " Alexander Stein
2010-09-21 17:31 ` [PATCH 2/2] Fix QT4 moc, cflags libs detection on dual QT3/Qt4 systems Alexander Stein
2010-08-02 21:29 ` [PATCHi v3] kconfig qconf: port to QT4 Michal Marek
2010-08-31 15:34 ` [PATCH v4] " Alexander Stein
2010-09-01 14:57 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0D64A2.9020701@suse.cz \
--to=mmarek@suse.cz \
--cc=alexander.stein@informatik.tu-chemnitz.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox