| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reduces boilerplate and helps with config file robustness: if a
field is missing from the config file, it will be replaced with its
default value.
|
|
|
|
|
|
|
|
| |
* stores: reactive data structures to hold application state
* controllers: subscribe to store changes and call store actions in
response to external events from services
* services: integrate with the nodejs and electron environment (should
be mocked for unit testing)
|
|
|
|
|
|
|
|
| |
The architecture in the main process is split into 3 main parts:
* services: interfaces for services are injected into the stores through
the MainEnv interface (for testability)
* services/impl: electron-specific implementations of services
* stores: the actions of the stores can invoke (asynchronous) services
|
| |
|
|
|
|
|
| |
If we watch the containing directory, we can use inotify instead of stat
polling.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Since we don't plan to shim any APIs that must be present immediately
when the service loads, we might as well switch to asynchronous IPC for
fetching the script to inject into the main world.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Inject CSS and main world scripts synchronously to avoid race conditions
with page loading.
Don't try to miming userAgentData for now, since it won't bypass
google's checks. However, simply omitting chrome from the user agent
does bypass them, at least for now.
|
|
|
|
| |
Not good enough for google, we'll need a different approach.
|
| |
|
| |
|
|
|
|
|
| |
Unfortunately, the reduced user-agent doesn't fool the google login
form, but at least reduces the amount of leaked information.
|
| |
|
|
|
|
|
|
|
| |
Let's try injecting CSS to set the background color of html to
white (instead of transparent) into the loaded pages. The CSS is
injected before the website's own styles load, so they should always
have the lowest priority.
|
| |
|
| |
|
|
|
|
|
| |
* Remove sophie and electron from the user-agent sting whenever possible
* Disable MPRIS integration
|
| |
|
|
|
|
|
| |
Centralizes vite configuration to be able to add license banners to
outputs in one place.
|
|
|
|
|
|
| |
Moves all typings to the dist-types directories from the dist
directories so that we can let vite clean the dist directories on build
without clobbering the typings generated by tsc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patches are send in one direction only, from the main to the renderer,
so all actions have to go through the context bridge and the renderer
IPC to modify the store in the renderer. This makes the store in the
main process a single source of truth, which simplifies debugging and
state persistence.
The store in the renderer is connected to redux devtools for inspection,
but playing back the state in the devtools won't change the sotre in
main process.
|
| |
|
| |
|
|
Project skeleton based on
https://github.com/cawa-93/vite-electron-builder
but we use react instead of vue and yarn instead of npm.
|