A GUI version with electron

[aseaday]

It should have:

• basic watching on repos
• distributed issue and wiki sub modules
• Other helpers function

I could write a basic demo in recent days.

[cjb]

@aseaday Sounds great, feel free!

[aseaday]

When i finish it, I hope you could create a repo and I will pr you . That is better for everybody to join you!

[Adjective-Object]

I'd be interested in getting in on something like this as well. Mind linking it in the comments once you've created the repo?

[cjb]

I haven't thought about it much, but in theory the Electron code could just live in this repo too?

[aseaday]

Hmmm, you could understand like this:

• Your code will be core backend server but should be split into some little modules for better developed later.
• Electron also use iojs but what we focus is GUI code.

[cjb]

Okay. Maybe just go ahead and make repos in your own github namespaces and mention them in this bug, and when it looks like something's working well we'll figure out where else to put it.

I registered the gittorrent organization (and gittorrent.org/net), so it could go under there too.

[ghost]

@aseaday Great idea! I'm also interested and willing to help.

[mastilver]

What is the status of that? I want to start working on it But I'm willing to help if something is already started

[cjb]

@mastilver No-one's working on it at the moment, feel free! :)

[mastilver]

@cjb cool, I've created: https://github.com/mastilver/gitTorrent-ui

[notpushkin]

@mastilver Are you planning on doing something with it? I could join in at some point too! :>

[thorsummoner]

Electron? Does your git torrent client really need two gigs of ram and thirty threads just for a front-end? On a desktop already running chrome, Atom, and Slack, in not sure there's enough room for another heavy weight RAM hog on the scene. :)

I will happily contribute gtk examples for a lighter approach if desired.

[mastilver]

@iamale I was planning to... But, I got sucks into a ton of work, I might resume my work in a month or two

[aseaday]

But A GTK version means rewrite a lot of codes.

[louy2]

I'd suggest we keep it lean and limited in terms of functions. I am imagining a taskbar icon which displays peer information and daemon status. Other things can be left to git.

[cjb]

@thorsummoner The core of gittorrent is written in JS, so if you wanted to use GTK you'd probably be rewriting the core (distributed hash table, etc) in another language, which doesn't seem like a good use of time.

(Or maybe you have a JS-GTK binding handy, I don't know.)

[thorsummoner]

There are js gtk bindings, but I'm not sure I would recommend them at this time. Especially if you're used to developing for chrome as their all based on other browsers, one is a WebKit based binding and the other a spidermonkey based binding, and neither have great docs.

[notpushkin]

There's node-gtk, and also plain Gjs (which is not based on Node, so would likely require additional work).

[notpushkin]

(Disclaimer: I'm not really good at GTK/Node pairing. I've tried GTK/Python though.)

---

Also, if you choose to go with Electron, it would be great if you've considered my project, electron-deb, as a way to package it on Linux. It keeps the Electron core separate from the apps, so it is stored once on the disk (resulting in less disk usage) and can be updated separately. Basically, it's the way apps in the other (interpreted) languages are packaged in Linux.