| Age | Commit message (Collapse) | Author |
|---|
|
- Resolves: #9229
|
|
|
|
in the end, depending on webengine didn't seem to be such a great idea:
it makes bundles more complex, heavy and brittle.
I tried compiling qt5 and the maintained qtwebkit fork, but that had
also its own set of problems (lastly, pyinstaller didn't work properly;
pyqt also adds a lot of garbage even if you disabled lots of modules you
don't need).
so, this is a fallback to a stretch-based build. it fixes the libGL
library by adding the right version into the bundle.
in this commit I also add a dockerfile for an image that can build
bundles by installing pip dependencies directly in the system. this has
the advantage that the build process is very fast, but the downside that
a new image needs to be pushed to the registry each time that new
dependencies are added; we'll also miss any bug due to introducing new
dependncies (but hopefully it will be catched by other steps in the CI).
The good side of it is that it reduces the need for some hacks in the
build process when bundling from a virtualenv.
|
|
|
|
- Resolves: #8794
|
|
|
|
for some usages, specially with autostart enabled, user might want to
launch only the systray.
this commit implements a simple ``--nowindow`` switch that just avoids
showing the main window for now. in the future, we can have a different
entrypoint that just launches bitmaskd and a minimal systray widget.
I'm not documenting this feature properly since I think this is still
missing some functionality: the ability to switch on and off the vpn,
and the ability to pass the --autostart as a flag to the bitmask
entrypoint.
|
|
|
|
this commit deprecates qtwebkit usage.
|
|
used from both entrypoints for linux and mac apps.
|
|
some juggling to make systray (qt5 for now) and browser (pywebview,
native) start and stop coordinatedly.
I will explore a more lightweight systray for coming releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Resolves: #9094
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since in OSX the user sees Bitmask in the Dock, I assume that re-launching
Bitmask.app from the /Applications folder means that we can kill the previous
process.
It probably should be able to terminate it gracefully, but we're hitting this
during early testing because of the move to native webview - because the
window.close() method is still not properly hooked.
- Resolves: #9001
|
|
|
|
|
|
|
|
The bundled version of bitmask is unable to find the bitmask_helpers
binary. Let's include it as part of the frozen binary generated by
pyinstaller.
- Resolves: #8862
|
|
|
|
The icon it was introduced and then deleted by mistake on the recent
window refactor after pixelated integration.
- Resolves: #8826
|
|
- Resolves: #8823
|
|
- Resolves: #8838
|
|
- Resolves: #8837
|
|
|
|
a bit hacky and all, but this should launch the service
and allow interacting from the default site (localhost:9090).
this is the first example of a pyqt-js bridge, it's an interesting
mechanism that we can use more in the future.
no efforts made so far in authenticating the app.
|
|
implements a global auth token for the app.
this token is written to .config/leap/authtoken, and passed to the
anchor part of the landing URI when opening the index resource by the
browser.
- Resolves: #8765
|
|
|
|
- Resolves: #8676
|
|
some hacks needed, it seems pyinstaller is choking again on namespace
packages for some reason that is beyond my current comprenhension.
|
|
|
|
basically, I give up trying to compile pyqt5 for python2. not worthy.
fortunately, the api changes are minimal so we can support two.
the way forward should be Py3.
still some bugs with rendering the viewport.
trying to help that, I introduced the web inspector, use DEBUG=1 flag to
have it visible.
|
|
|
|
|
|
|
|
|
