Date: Fri, 17 Jun 2011 12:31:25 +0200
From: Pieter Wuille <pieter.wuille@gmail.com>
To: John Smith <witchspace81@gmail.com>
Message-ID: <20110617103124.GA7177@ulyssis.org>
References: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
Precedence: list

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