From: Wladimir <laanwj@gmail•com>
To: Peter Vessenes <peter@coinlab•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Suggestion for Simplifying development work
Date: Fri, 15 Jun 2012 17:59:02 +0200 [thread overview]
Message-ID: <CA+s+GJBrXL0QVPraM6mR1_ZpRtVri_kN6iy5Q8C0_EegrL+_6w@mail.gmail.com> (raw)
In-Reply-To: <CAMGNxUuPyS+NCfHaoBuc-dvm+m7wyqj2sUReyZiP3hbEQnNeRg@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2012-06-15 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 14:59 Peter Vessenes
2012-06-15 15:59 ` Wladimir [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJBrXL0QVPraM6mR1_ZpRtVri_kN6iy5Q8C0_EegrL+_6w@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=peter@coinlab$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox