public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Daniel Edgecumbe" <email@esotericnonsense.com>
To: "M.K. Safi via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] I want to rebuild the GUI in JavaScript
Date: Sat, 23 Nov 2019 21:07:17 +0100	[thread overview]
Message-ID: <2efb057a-4838-4fca-a24e-432091a63ea9@www.fastmail.com> (raw)
In-Reply-To: <CAO7Y_eX2egYNw+h_jDGTYx1R5sC1zrTOXOHuJU4rY66rWKRwAw@mail.gmail.com>

You may find my (incomplete) front-end of interest:

https://bitcoin.electronrelocation.com

The live demo is backed by a -disablewallet node, but it was able to accept payments and send them via QR codes before I stopped development.

The source is available via AGPLv3.

https://git.esotericnonsense.com/pub/bitcoin-top.git

I am unable to continue development due to time constraints.

Daniel Edgecumbe | esotericnonsense
email@esotericnonsense.com | https://esotericnonsense.com

On Sat, Nov 23, 2019, at 17:49, Oscar Lafarga via bitcoin-dev wrote:
> Hi MK,
> 
> I very much share your interests and curiosities here and actually 
> don't have an answer on whether it's been tried before.
> 
> One of the few things I am imagining is that given the security-focused 
> nature of the Bitcoin Core software, any vulnerabilities in the way NPM 
> handles the dependencies of the Electron app would be a very high 
> priority (see 
> https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/) 
> 
> In NodeJS-land, my sense is that there is a "move fast and break 
> things" mentality that may have seeped into some practices that may be 
> considered standard. I have seen some recent developments over the past 
> few years to address these kinds of issues such as npm-audit (as of 
> Node v6+) but I would recommend doing some thorough research on this 
> front to make sure there is a secure dependency management solution in 
> place for such a GUI.
> 
> Another comment I'd make is that if we consider the GUI as a layer that 
> is separate from the protocol layer, this mailing list may not be the 
> best place to fully discuss this. However I think if anyone here who 
> has been around longer can contribute info on past attempts at this, it 
> could be quite productive. This could technically exist as an 
> independent client, but I guess there's a conversation on whether this 
> new Electron UI would ever replace the Qt UI, but since it doesn't 
> exist yet it could be far too early for that. 
> 
> Thanks,
> 
> 
> 
> 
> 
> 
> On Sat, Nov 23, 2019, 2:17 PM M.K. Safi via bitcoin-dev 
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I’d like to try to rebuild Bitcoin Core GUI using the JavaScript Electron framework. My goal is to get a real world understanding of the pros and cons of moving from Qt to Electron.
> > 
> > Before I start, I‘d like to know if this has been tried before or if there are ongoing efforts in this direction by anyone?
> > 
> > I spent sometime looking into how to implement this. One approach could be for Electron to drive the UI by running bitcoind and communicating with it through RPC. But I don’t know if such implementation can achieve feature-parity with the Qt implementation. Qt has the advantage of direct access to Bitcoin Core code.
> > 
> > Anyways, I just wanted to share these ideas before going further with them, so please let me know if you have any information on the above!
> > -- 
> > Sent from my iPhone
> >  _______________________________________________
> >  bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


  reply	other threads:[~2019-11-23 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23  6:45 [bitcoin-dev] I want to rebuild the GUI in JavaScript M.K. Safi
2019-11-23 16:49 ` Oscar Lafarga
2019-11-23 20:07   ` Daniel Edgecumbe [this message]
2019-11-23 18:27 ` Jonas Schnelli
2020-01-16 18:30   ` M.K. Safi

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=2efb057a-4838-4fca-a24e-432091a63ea9@www.fastmail.com \
    --to=email@esotericnonsense.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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