The first step is to make the rc interface work in such a way that it can control rclone entirely. That will be useful for lots of things, not just a browser interface.
To start with, I suggest something like rclone serve rc --serve-files /path/to/files/to/serve which would
start the rc with the new interface
open the index.html in the path in the browser
This would then enable experimentation with web technology GUIs.
I also made a new command rclone rcd which does nothing but serve the API.
So you can type
rclone rcd --rc-user user --rc-pass pass
or
rclone rcd --rc-noauth
to serve the remote control. Use rclone rc while it is running to see all the API. Youāll need authentication to do anything which involves looking at files (or use the --rc-no-auth flag).
show a split pane view of local and remote and allow dragging between the two
I think having the option to display many remotes at once is important. If itās limited to two, Iād like to be able to show two remotes side by side, whether it is a local and a cloud remote, two locals, or two cloud remotes.
Another feature Iād like is to see the generated command for an action and be able to copy it. It would help me build my scripts faster.
That saidā¦ I like all those features, haha. Rating them for me is hard but the ones I mentioned would be the most important ones for me.
Split view of local & remote isnāt super important IMO, I know a lot of apps have this UI but itās just as easy to have Finder open next to RCloneBrowser in my experience. Split pane for drag & dropping between multiple remotes might be cool, but having tabs for this is probably better.
The biggest thing for me will be multi-item selection as mentioned earlier in the thread, and the ability to drag & drop within a remote, or between remotes.
This would also go hand in hand with proper searching of remotes as well - if it could handle searching of both the current folder AND global search of the entire remote, and then generating public links from the search results, that would be amazing.
While Iām excited for all of this, this all should be separated from the current binary.
I think the best feature of current rclone that makes it the king of tool is that itās so versatile and being able to be deployed in so many platforms, old and new.
I can install rclone in compatible router, old android phones and tablets, latest NVIDIA shield etc. Old phones that have no use case has become rclone end point which is super awesome! I have an army of low-powered high-IO throughout devices and itās awesome because rclone binary is small and have small dependency of other stuff.
Absolutely, I donāt want to break any of that! Iām experimenting at the moment. If I can wedge a browser based GUI into rclone and expand the binary size by 1MB but otherwise leave all the above the same, what would you say?
Thank you, that sounds great. And as always thank you for your work.
In building gui please always take into consideration that router and old phones has less cpu power, memory and storage. Rclone via termux or other similar way on Android has been very great to turn old phones into something very powerful.
Honestly I would probably rarely or never use a gui because the best gui is the ones we already have, in my humble opinion. For example I use rclone + samba so my gui is a standard file Explorer in Linux, Windows, iPhone and Android. Thatās my daily drive for gui. File search, streaming etc all is handled very well by each apps on that platform.
Iām more interested in gui that abstract technical layer of rclone. For example in other thread thereās a person who built rclone gui with electron js to mount, upload, download etc. Thatās a good direction for wider rclone use. Things that normally require terminal would be great to be done in easier way in gui.
But then again I use rclone only for GDrive. A gui could be very useful for rclone for othercloyd providers.
Iām assuming that 1MB would be compressed assets within the rclone binary.
go get is something that I wish to maintain for rclone which means that there would be a separate build the GUI step and commit it. Iām fine with that though!
Additionally, could someone maybe just fork RCloneBrowser and update the most obvious areas where itās currently broken? The stats revamp in 1.43 has broken RCloneBrowserās stats readouts for example.