Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Qbrt Alternatives
Similar projects and alternatives to qbrt
-
Fenix
Discontinued ⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
gecko-dev
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
qbrt reviews and mentions
- Mozilla QBRT, a tool to create desktop apps with Gecko (Firefox rendering engine) similarly to Electron, has not been updated in years. Don't let it fade into obscurity, Electron is a resource hog!
-
Building a Desktop Application for Datasette
I assume they meant https://en.wikipedia.org/wiki/XULRunner, which was Mozilla's spiritual predecessor to Electron.
Some abandoned modern alternatives included Positron[1][2] and qbrt[3][4].
While technically possible using Firefox's XULRunner functionality (`firefox --app app.ini` — mostly undocumented, potentially unsupported in the future), as far as I can tell, Mozilla has abandoned the Electron approach for XUL/Gecko bundling, which is a shame since Firefox itself is basically just an implementation on top of the Gecko XUL runtime.
> "[Firefox] is distributed as the combination of a Gecko XUL runtime — libxul, other shared libraries, and non-browser-specific resources like those in toolkit/ — plus a Firefox XUL application — mostly just the files in Contents/Resources/browser/, plus the 'firefox' stub executable that loads Gecko and points it at a XUL application" [5]
[1]: https://github.com/mozilla/positron
[2]: http://web.archive.org/web/20210227132731/https://mykzilla.o...
[3]: https://github.com/mozilla/qbrt
[4]: http://web.archive.org/web/20210601133844/https://mykzilla.o...
[5]: https://mykzilla.org/2017/03/08/positron-discontinued/#comme...
-
Firefox 91 Release Notes
The issue with this is that the more deeply customisable a fork would be the further it would stray from upstream (and by extension the more dev resources it would require to maintain).
> I keep hearing the Firefox codebase isn't very modular and makes it hard to pursue such a project, and I don't doubt it. But aren't there enough of "us" out there to make a concerted effort?
There's been plenty of people making such an effort, but yeah it does appear to be "hard". If you're interested in following previous work, some relevant links:
- Overview of Myk Melez's efforts in this space https://mykzilla.org/2017/03/08/positron-discontinued/
- https://mozilla.github.io/geckoview/ (official but Android-only)
- https://github.com/mozilla/qbrt
It may also be worthwhile reading about CEF which has become something of a defacto standard: https://en.wikipedia.org/wiki/Chromium_Embedded_Framework
-
A note from our sponsor - InfluxDB
www.influxdata.com | 8 May 2024
Stats
mozilla/qbrt is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of qbrt is JavaScript.
Sponsored