Ability to configure browser "shell"

[RangerMauve]

• Pass in a URL for loading the browser shell
• Should have a browser.html which will define the browser chrome for the URL bar and the such
• Should have a theme.css to export CSS variables for the browser theme (to be used in stuff like the markdown rendering extension)
• Should have a welcome.html to load as the home page in new tabs (optional?)

This will give people the ability to fully customize the browser UI of Agregore and anything relying on styling.

One thing that will be done is a modification to the IPC API to enable creating multiple browserViews and resizing them / destroying them dynamically. This will enable folks to build tabs themselves if they want to.

Also, it'd be good to have an IPC message for getting the set of capabilities a browser is providing so that extensions could account for older versions or newer versions and prompt users to update or downgrade.

The URL should be configurable in the .agregorerc file for now, maybe a shell parameter.

Ideally the agregore:// protocol should try to redirect the hyper:// URL of the shell when one exists. Or maybe to load content from it?

[RangerMauve]

The shell should have the option of being able to make the window frameless so it can customize the title bar.

For this we'll need IPC APIs for all the functions that normally happen in the title bar

• Getting the title of the web contents
• Maximizing, Minimizing, Resizing the window
• The names of all the menu items and the ability to invoke them

[sull]

This is a great feature. Not to discourage the general idea of forking but it could consolidate contributions to Agregore and avoid splintering in early phase of dev, which sometimes can happen.