It serves to illustrate the general idea of the project and does not yet provide proper sandboxing (among other things) - and plenty of details on the state of implementation are available in the form of annotations in the source code. This is a functional application written in HTML running on a pre-alpha version of the chromeless platform: the inner browser elements are iframes instead of XUL browser elements. The following screenshot is an example of a very simple browser application with page thumbnails used for tab handlers: We intend to create an experimental toolkit which will allow developers to build their own Web browser using standard Web technologies: HTML, CSS, and JavaScript. It’s questions like these that have motivated us to start a new Mozilla Labs experiment, codenamed “chromeless”. What if the parts of the browser that are most interesting to contributors were implemented in standard Web technologies such as HTML, CSS and JavaScript? What kinds of wild-eyed experimentation would we see if a new conception of browser UI could be prototyped in about the same time it takes to write a web page? Firefox is put together in a way that seasoned developers are able implement features with amazing efficiency, but at the same time, the browser interface in XUL represents a barrier for potential contributors.
Much of the user interface (browser chrome) of Firefox is implemented in XUL, which uses a lot of Web-based technologies such as the DOM and JavaScript. Have you ever had an idea to improve the user interface of your browser? Have you ever actually gone and tried to make that idea a reality? If you have, you would have probably used technologies like XUL and XPCOM. If you have questions then please ask them on the rclone forum.The “Chromeless” project experiments with the idea of removing the current browser user interface and replacing it with a flexible platform which allows for the creation of new browser UI using standard Web technologies such as HTML, CSS and JavaScript. The GUI is being developed in the: rclone/rclone-webui-react repository.īug reports and contributions are very welcome :-) Or instead of htpasswd if you just want a single user and password: If you want to run the GUI behind a proxy at /rclone you could use these flags: Example: Running a public GUIįor example the GUI could be served on a public port over SSL using an htpasswd file using the following flags: These flags can be overridden as desired. The rclone rcd may use any of the flags documented on the rc page. rclone will open the browser with a login_token so it can log straight in.rclone will start serving the files from the API bundle over the same port as the API.
#Ui browser download#
If the API bundle is missing then rclone will download it.The API is bound to localhost with an auto generated username and password.Rclone starts but only runs the remote control API ("rc").
When you run the rclone rcd -rc-web-gui this is what happens (More docs and walkthrough video to come!) How it works
#Ui browser series#
On the left hand side you will see a series of view buttons you can click on: Once the GUI opens, you will be looking at the dashboard which has an overall overview.
#Ui browser update#
If you find your GUI broken, you may force it to update by add -rc-web-gui-force-update.īy default, rclone will open your browser. If you wish to check for updates then you can add -rc-web-gui-update Possible to separate the rclone and the GUI - see below for details. This assumes you are running rclone locally on your machine. ĥ 11:40:16 NOTICE: Serving remote control on This will produce logs like this and rclone needs to continue to run to serve the GUI: 5 11:40:14 NOTICE: A new release for gui is present at ĥ 11:40:14 NOTICE: Downloading webgui binary. Run this command in a terminal and rclone will download and thenĭisplay the GUI in a web browser. Somewhat experimental at the moment so things may be subject to Rclone can serve a web based GUI (graphical user interface).