Plans for front-ends?

[l-n-s]

Any plans on adding front-ends for end-users? Like transmission torrent client has: cli version, GTK, and web front-end.

[majestrate]

i am considering implementing rtorrent compatible rpc but it depends on how complex that is, if it is too complex it'll be its own rpc dialect. any ui would talk via this rpc.

[majestrate]

i am not sure what UI i would prefer tho. first would be command line tools.

[ThePrudentNinja]

My vote is for a web frontend. Something that can be loaded in a browser, like i2psnark. That is the preferred gui. Having a backup cli interface might be a good idea too, but with a proper browser based gui, that shouldn't be needed (can use console browsers to view if need be).

[majestrate]

both a web ui and cli tools can use the same rpc. the question i'd ask is how much can be reused from other projects?

i need to research rtorrent's rpc api further as i was planning on implementing just that so that existing frontends can be dropped ontop.

[mathiasfriman]

Perhaps this is a starting point?

https://github.com/mrobinsn/go-rtorrent

[DiagonalArg]

If there was some way to use transmission's rpc (written in C), then you'd also be able to use a cute little curses terminal client called stig. I find it much better than any web page or gui. The developer is open to working with clients other than transmission.

[majestrate]

i am a lot more familiar with transmission's rpc than rtorrent

[ghost]

I concur on using transmission instead of rtorrent, since it has more (non abandoned) clients.

[majestrate]

Alright I'll update the roadmap to say transmission instead of rtorrent On Sun, Feb 25, 2018 at 01:03:33PM -0800, Q3CPMA wrote:

I concur on using transmission instead of rtorrent, since it has more (non abandoned) clients.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/majestrate/XD/issues/2#issuecomment-368344337