summaryrefslogtreecommitdiff
path: root/38/9a3f9d7238c17dda2943a83b91a23a8ace62a0
blob: 45739057b90d79e464c99e69b8f331eda04d7439 (plain)
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 <peter@coinlab.com>) id 1SfY0T-0000Am-0b
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jun 2012 15:00:13 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of coinlab.com
	designates 209.85.210.47 as permitted sender)
	client-ip=209.85.210.47; envelope-from=peter@coinlab.com;
	helo=mail-pz0-f47.google.com; 
Received: from mail-pz0-f47.google.com ([209.85.210.47])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1SfY0N-0003lw-Ep
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jun 2012 15:00:12 +0000
Received: by dalh21 with SMTP id h21so4104867dal.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jun 2012 08:00:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type
	:x-gm-message-state;
	bh=MVTkD7xM27YLOhF+iFweutqKv1vNLvbpYLyM6qeCwmg=;
	b=ah5hSZrBO9cMlCUr23bltONNDoM/DuYeBB6uKlOsKrKCmGX4jsUwpHIdb4zA8jPfZR
	YkZ//0NZPkanrKdyD9YhKtQs/t3MmGo0WNRh30YidPvxOTYpBO8SrtyCiYQlA7njdboe
	UzFLnVJMpKJKoxbJD1NcPrtuBVkAUnqDW9tvWCFJeaCCxuA4urfYLdgAMsPjrAiE7ayl
	n9AtTHbA8LFQVYyRaXml4U384jmar+mwh9ckWQtBNpJmtZB8vOmm2uvNcnES7e9/pZTf
	aYRADyTtTNrlTYtRAMqBeeJVLBOiSmgwYhiUGTOl+x0T4OvVaPjCKinsT62F40TZ8GXa
	YQDQ==
Received: by 10.68.189.65 with SMTP id gg1mr21228364pbc.10.1339772401282; Fri,
	15 Jun 2012 08:00:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.141.21 with HTTP; Fri, 15 Jun 2012 07:59:40 -0700 (PDT)
From: Peter Vessenes <peter@coinlab.com>
Date: Fri, 15 Jun 2012 10:59:40 -0400
Message-ID: <CAMGNxUuPyS+NCfHaoBuc-dvm+m7wyqj2sUReyZiP3hbEQnNeRg@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e89a8ff1cae00eef1104c2841267
X-Gm-Message-State: ALoCoQkQi5RwNWY+H7iNkbshRAk9mAl3Io2mdhLNDjQ0Nou4BeNbFqty4mDuumhvQdtles9ECfb3
X-Spam-Score: 0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.6 HTML_IMAGE_ONLY_12 BODY: HTML: images with 800-1200 bytes of words
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 T_REMOTE_IMAGE         Message contains an external image
	-0.8 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SfY0N-0003lw-Ep
Subject: [Bitcoin-development] Suggestion for Simplifying development work
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, 15 Jun 2012 15:00:13 -0000

--e89a8ff1cae00eef1104c2841267
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I've been wondering about whether it would be possible to wipe out the GUI
completely from the satoshi client, and reimplement any necessary data
requests as RPC calls, allowing us to fork -QT and other GUIs over and
(hopefully) dramatically simplifying the codebase that you all have to work
on.

Any thoughts about this? Once a week at least I find myself wanting to find
ways to help speed up development, this seems like it could be a big win.

Peter

-- 
Peter J. Vessenes
CEO, CoinLab
M: 206.595.9839
Skype: vessenes
Google+ <https://plus.google.com/112885659993091300749>

--e89a8ff1cae00eef1104c2841267
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,<div><br></div><div>I&#39;ve been wondering about whether it would b=
e possible to wipe out the GUI completely from the satoshi client, and reim=
plement any necessary data requests as RPC calls, allowing us to fork -QT a=
nd other GUIs over and (hopefully) dramatically simplifying the codebase th=
at you all have to work on.</div>

<div><br></div><div>Any thoughts about this? Once a week at least I find my=
self wanting to find ways to help speed up development, this seems like it =
could be a big win.</div><div><br></div><div>Peter<br clear=3D"all"><div>

<br></div>-- <br><table style=3D"font-family:Times"><tbody><tr><td><img src=
=3D"http://coinlab.com/images/coinlab-logo.png"></td><td valign=3D"bottom">=
<div style=3D"font-family:RobotoLight,&#39;Lucida Grande&#39;,Helmet,Freesa=
ns,sans-serif;font-size:16px;line-height:20px">

Peter J. Vessenes<br>CEO, CoinLab<br>M: 206.595.9839<br>Skype: vessenes<br>=
<a href=3D"https://plus.google.com/112885659993091300749" target=3D"_blank"=
>Google+</a></div></td></tr></tbody></table><br>
</div>

--e89a8ff1cae00eef1104c2841267--