1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mith@jrbobdobbs.org>) id 1QXaAw-0003eV-E6
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jun 2011 14:37:34 +0000
X-ACL-Warn:
Received: from mail-gx0-f175.google.com ([209.85.161.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1QXaAr-0001uh-QV
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jun 2011 14:37:34 +0000
Received: by gxk3 with SMTP id 3so1751720gxk.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Jun 2011 07:37:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.146.47.14 with SMTP id u14mr2527533yau.35.1308319835171; Fri,
17 Jun 2011 07:10:35 -0700 (PDT)
Sender: mith@jrbobdobbs.org
Received: by 10.147.34.11 with HTTP; Fri, 17 Jun 2011 07:10:35 -0700 (PDT)
Received: by 10.147.34.11 with HTTP; Fri, 17 Jun 2011 07:10:35 -0700 (PDT)
In-Reply-To: <201106170929.57750.luke@dashjr.org>
References: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
<20110617103124.GA7177@ulyssis.org>
<201106170929.57750.luke@dashjr.org>
Date: Fri, 17 Jun 2011 09:10:35 -0500
X-Google-Sender-Auth: VrQ0PuS7XOFvP50zPqrj-onYO78
Message-ID: <BANLkTi=g5-xHk4rCo=0zm4GFeLNMuONe2w@mail.gmail.com>
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=000e0cd349fa072a5004a5e8f35e
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1QXaAr-0001uh-QV
Subject: Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 14:37:34 -0000
--000e0cd349fa072a5004a5e8f35e
Content-Type: text/plain; charset=ISO-8859-1
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
--000e0cd349fa072a5004a5e8f35e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p>Agreed. The sooner qt gets merged the sooner real GUI improvements will =
be made.</p>
<div class=3D"gmail_quote">On Jun 17, 2011 8:30 AM, "Luke-Jr" <=
;<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br type=
=3D"attribution">> On Friday, June 17, 2011 6:31:25 AM Pieter Wuille wro=
te:<br>
>> The only disadvantage of another GUI is that the (necessary) clean=
up of<br>>> RPC/GUI code will now need makes changes in 3 places inst=
ead of 2, but as<br>>> I understand it, there are much more people wi=
lling to work on Qt code<br>
>> than on wx code?<br>> <br>> I'm not sure the Wallet prot=
ocol implementation needs to touch the GUI code at <br>> all, except whe=
n porting the GUI to use it. Therefore, if the code is already <br>> wri=
tten, I don't see any harm in merging it.<br>
> <br>> -------------------------------------------------------------=
-----------------<br>> EditLive Enterprise is the world's most techn=
ically advanced content<br>> authoring tool. Experience the power of Tra=
ck Changes, Inline Image<br>
> Editing and ensure content is compliant with Accessibility Checking.<b=
r>> <a href=3D"http://p.sf.net/sfu/ephox-dev2dev">http://p.sf.net/sfu/ep=
hox-dev2dev</a><br>> _______________________________________________<br>
> Bitcoin-development mailing list<br>> <a href=3D"mailto:Bitcoin-dev=
elopment@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</=
a><br>> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-=
development">https://lists.sourceforge.net/lists/listinfo/bitcoin-developme=
nt</a><br>
</div>
--000e0cd349fa072a5004a5e8f35e--
|
