* [Bitcoin-development] Roadmap for autotools / Qt gui merge
@ 2011-06-17 6:42 John Smith
2011-06-17 7:05 ` Brendan Molloy
` (4 more replies)
0 siblings, 5 replies; 12+ messages in thread
From: John Smith @ 2011-06-17 6:42 UTC (permalink / raw)
To: bitcoin-development
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
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?
JS
[-- Attachment #2: Type: text/html, Size: 285 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
@ 2011-06-17 7:05 ` Brendan Molloy
2011-06-17 10:31 ` Pieter Wuille
` (3 subsequent siblings)
4 siblings, 0 replies; 12+ messages in thread
From: Brendan Molloy @ 2011-06-17 7:05 UTC (permalink / raw)
To: John Smith; +Cc: bitcoin-development
Is there a link to this GUI code?
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?
>
> JS
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Regards,
Brendan Molloy
M: +61 434 069 776
T: @piecritic
W: http://bbqsrc.net
E: brendan@bbqsrc•net
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
2011-06-17 7:05 ` Brendan Molloy
@ 2011-06-17 10:31 ` Pieter Wuille
2011-06-17 13:29 ` Luke-Jr
2011-06-17 16:27 ` Gavin Andresen
` (2 subsequent siblings)
4 siblings, 1 reply; 12+ messages in thread
From: Pieter Wuille @ 2011-06-17 10:31 UTC (permalink / raw)
To: John Smith; +Cc: bitcoin-development
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 10:31 ` Pieter Wuille
@ 2011-06-17 13:29 ` Luke-Jr
2011-06-17 14:10 ` Douglas Huff
0 siblings, 1 reply; 12+ messages in thread
From: Luke-Jr @ 2011-06-17 13:29 UTC (permalink / raw)
To: bitcoin-development
On Friday, June 17, 2011 6:31:25 AM Pieter Wuille wrote:
> 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?
I'm not sure the Wallet protocol implementation needs to touch the GUI code at
all, except when porting the GUI to use it. Therefore, if the code is already
written, I don't see any harm in merging it.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 13:29 ` Luke-Jr
@ 2011-06-17 14:10 ` Douglas Huff
0 siblings, 0 replies; 12+ messages in thread
From: Douglas Huff @ 2011-06-17 14:10 UTC (permalink / raw)
To: bitcoin-development
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Agreed. The sooner qt gets merged the sooner real GUI improvements will be
made.
On Jun 17, 2011 8:30 AM, "Luke-Jr" <luke@dashjr•org> wrote:
> On Friday, June 17, 2011 6:31:25 AM Pieter Wuille wrote:
>> 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?
>
> I'm not sure the Wallet protocol implementation needs to touch the GUI
code at
> all, except when porting the GUI to use it. Therefore, if the code is
already
> written, I don't see any harm in merging it.
>
>
------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 1643 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
2011-06-17 7:05 ` Brendan Molloy
2011-06-17 10:31 ` Pieter Wuille
@ 2011-06-17 16:27 ` Gavin Andresen
2011-06-17 20:37 ` Luke-Jr
2011-06-19 0:30 ` Pieter Wuille
2011-06-19 1:37 ` Luke-Jr
4 siblings, 1 reply; 12+ messages in thread
From: Gavin Andresen @ 2011-06-17 16:27 UTC (permalink / raw)
To: John Smith; +Cc: bitcoin-development
I'm in favor of dropping the wxWidgets GUI and replacing it with a Qt
GUI. I think supporting more than one GUI for the reference client is
a bad idea.
Qt is LGPL, so license for that is not an issue.
John, you willing to release your code under the bitcoin MIT license?
Everybody else: anybody object to replacing "the devil we know"
(wxWidgets) with Qt?
--
--
Gavin Andresen
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 16:27 ` Gavin Andresen
@ 2011-06-17 20:37 ` Luke-Jr
2011-06-17 22:59 ` Jeff Garzik
0 siblings, 1 reply; 12+ messages in thread
From: Luke-Jr @ 2011-06-17 20:37 UTC (permalink / raw)
To: bitcoin-development
On Friday, June 17, 2011 12:27:22 PM Gavin Andresen wrote:
> I'm in favor of dropping the wxWidgets GUI and replacing it with a Qt
> GUI. I think supporting more than one GUI for the reference client is
> a bad idea.
>
> Qt is LGPL, so license for that is not an issue.
> John, you willing to release your code under the bitcoin MIT license?
>
> Everybody else: anybody object to replacing "the devil we know"
> (wxWidgets) with Qt?
So long as we can get a solid name for it. Obviously I can't continue to call
it wxBitcoin if it's strictly Qt...
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 20:37 ` Luke-Jr
@ 2011-06-17 22:59 ` Jeff Garzik
0 siblings, 0 replies; 12+ messages in thread
From: Jeff Garzik @ 2011-06-17 22:59 UTC (permalink / raw)
To: Luke-Jr; +Cc: bitcoin-development
On Fri, Jun 17, 2011 at 4:37 PM, Luke-Jr <luke@dashjr•org> wrote:
> So long as we can get a solid name for it. Obviously I can't continue to call
> it wxBitcoin if it's strictly Qt...
I've started calling the github/bitcoin/bitcoin.git the Satoshi
Client, GUI or not.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
` (2 preceding siblings ...)
2011-06-17 16:27 ` Gavin Andresen
@ 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
4 siblings, 2 replies; 12+ messages in thread
From: Pieter Wuille @ 2011-06-19 0:30 UTC (permalink / raw)
To: John Smith; +Cc: bitcoin-development
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?
The consensus seems to be to merge autotools and qtgui. However, autotools is
apparently not tested (enough) on native windows and osx platforms.
Anyone on this list with either development environnement, and willingness
to test?
--
Pieter
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
` (3 preceding siblings ...)
2011-06-19 0:30 ` Pieter Wuille
@ 2011-06-19 1:37 ` Luke-Jr
4 siblings, 0 replies; 12+ messages in thread
From: Luke-Jr @ 2011-06-19 1:37 UTC (permalink / raw)
To: bitcoin-development
On Friday, June 17, 2011 2:42:30 AM John Smith wrote:
> I think my Qt GUI is pretty much ready for merging. I've been using it for
> a while and all functionality works.
Before this gets merged, I'd like to check: does it work ok if Qt is built
without glib support?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge [Mac update]
2011-06-19 0:30 ` Pieter Wuille
@ 2011-06-20 2:34 ` Mark Visser
2011-06-22 14:18 ` [Bitcoin-development] Roadmap for autotools / Qt gui merge Pieter Wuille
1 sibling, 0 replies; 12+ messages in thread
From: Mark Visser @ 2011-06-20 2:34 UTC (permalink / raw)
To: Pieter Wuille; +Cc: bitcoin-development
Hi everyone,
I spent some time today with the bitcoin-qt client and autotools on mac. The qt client builds and runs with a few small changes (mostly just #including boost/filesystem/operations.hpp in a few places).
Autotools + qt will take a bit longer. I've got something *almost* working, but I won't have a chance to finish it for the rest of the week. I'll push the changes to github tomorrow (Monday) so anyone else can take a crack at it if they so wish.
cheers,
-Mark
On 2011-06-18, at 8:30 PM, Pieter Wuille wrote:
> 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?
>
> The consensus seems to be to merge autotools and qtgui. However, autotools is
> apparently not tested (enough) on native windows and osx platforms.
>
> Anyone on this list with either development environnement, and willingness
> to test?
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
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 ` Pieter Wuille
1 sibling, 0 replies; 12+ messages in thread
From: Pieter Wuille @ 2011-06-22 14:18 UTC (permalink / raw)
To: bitcoin-development
On Sun, Jun 19, 2011 at 02:30:49AM +0200, Pieter Wuille wrote:
> The consensus seems to be to merge autotools and qtgui. However, autotools is
> apparently not tested (enough) on native windows and osx platforms.
>
> Anyone on this list with either development environnement, and willingness
> to test?
Jaromil has his autotools branch rebased against git master, and included Mark's
NOSIGPIPE/NOSIGNAL patch (needs a commit summary, though).
Can people test this compiles+works on several systems (ubuntu, fedora(?), mingw
crosscompile, osx, ...)?
See https://github.com/jaromil/bitcoin/commits/autotools3
For me, it works on Ubuntu 10.10 amd64, including wx gui.
--
Pieter
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2011-06-22 14:18 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
2011-06-17 7:05 ` Brendan Molloy
2011-06-17 10:31 ` Pieter Wuille
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox