* [Bitcoin-development] Suggestion for Simplifying development work
@ 2012-06-15 14:59 Peter Vessenes
2012-06-15 15:59 ` Wladimir
0 siblings, 1 reply; 2+ messages in thread
From: Peter Vessenes @ 2012-06-15 14:59 UTC (permalink / raw)
To: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
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>
[-- Attachment #2: Type: text/html, Size: 1034 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bitcoin-development] Suggestion for Simplifying development work
2012-06-15 14:59 [Bitcoin-development] Suggestion for Simplifying development work Peter Vessenes
@ 2012-06-15 15:59 ` Wladimir
0 siblings, 0 replies; 2+ messages in thread
From: Wladimir @ 2012-06-15 15:59 UTC (permalink / raw)
To: Peter Vessenes; +Cc: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Fri, Jun 15, 2012 at 4:59 PM, Peter Vessenes <peter@coinlab•com> wrote:
> 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.
>
Splitting the UI into a seperate *process* is a long-term goal. The UI code
is structured so that all communication with the core happens through a
"bottleneck" (consisting of the model classes), so preparation has been
under way.
However, the current RPC calls don't suffice to implement a full-featured,
responsive UI. I'm not even sure JSON-RPC is a good fit for a UI<->core
protocol, as it doesn't support bidirectional communication (at least
without pretty ugly hacks).
But what exactly is the problem with having a GUI as part of the main
client project? I don't see how it would "speed up development" to split
the project. By far most of the users use the program through the UI so it
is one of the drivers for requirements on the core, and I'd think it is
pretty important to keep it a first-class citizen.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1658 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-06-15 15:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-15 14:59 [Bitcoin-development] Suggestion for Simplifying development work Peter Vessenes
2012-06-15 15:59 ` Wladimir
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox