From: Pieter Wuille <pieter.wuille@gmail•com>
To: John Smith <witchspace81@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
Date: Fri, 17 Jun 2011 12:31:25 +0200 [thread overview]
Message-ID: <20110617103124.GA7177@ulyssis.org> (raw)
In-Reply-To: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
On Fri, Jun 17, 2011 at 06:42:30AM +0000, John Smith wrote:
> Hello,
>
> I think my Qt GUI is pretty much ready for merging. I've been using it for a
> while and all functionality works.
>
> What is the current roadmap for including the autotools build system, so
> that it will be possible to support multiple GUIs? 0.4.0?
I'm in favor of merging autotools now, unless there are still known issues with
it, such as mingw32 compatibility?
If the Qt port is functionally complete and stable, I'd vote to have it merged as
well under these conditions:
* the changes to the 'core' are minimal/trivial
* marked as 'experimental', and not enabled by default
The only disadvantage of another GUI is that the (necessary) cleanup of RPC/GUI
code will now need makes changes in 3 places instead of 2, but as I understand
it, there are much more people willing to work on Qt code than on wx code?
--
Pieter
next prev parent reply other threads:[~2011-06-17 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:42 John Smith
2011-06-17 7:05 ` Brendan Molloy
2011-06-17 10:31 ` Pieter Wuille [this message]
2011-06-17 13:29 ` Luke-Jr
2011-06-17 14:10 ` Douglas Huff
2011-06-17 16:27 ` Gavin Andresen
2011-06-17 20:37 ` Luke-Jr
2011-06-17 22:59 ` Jeff Garzik
2011-06-19 0:30 ` Pieter Wuille
2011-06-20 2:34 ` [Bitcoin-development] Roadmap for autotools / Qt gui merge [Mac update] Mark Visser
2011-06-22 14:18 ` [Bitcoin-development] Roadmap for autotools / Qt gui merge Pieter Wuille
2011-06-19 1:37 ` Luke-Jr
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=20110617103124.GA7177@ulyssis.org \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=witchspace81@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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