|Moritz Strohm 1d8473d26e||1 month ago|
|DefaultSettings||5 years ago|
|EngineInterfaces||1 year ago|
|oldcode||5 years ago|
|.gitignore||1 year ago|
|AUTHORS||5 years ago|
|BrowserTabWidget.cpp||1 year ago|
|BrowserTabWidget.h||1 year ago|
|COPYING||5 years ago|
|Changelog||5 years ago|
|ConfigurationWindow.ui||5 years ago|
|DevelopmentGuidelines.txt||2 years ago|
|EngineSettings.h||2 years ago|
|GUIHandler.cpp||2 years ago|
|GUIHandler.h||2 years ago|
|MoeNavigator.png||5 years ago|
|MoeNavigator.xpm||5 years ago|
|README.md||1 year ago|
|configurationwindow.cpp||2 years ago|
|configurationwindow.h||2 years ago|
|configurationwindow.ui||5 years ago|
|main.cpp||1 year ago|
|moenavigator.pro||1 month ago|
|moenavigatoraboutdialog.cpp||2 years ago|
|moenavigatoraboutdialog.h||2 years ago|
|moenavigatoraboutdialog.ui||1 month ago|
|moenavigatormain.cpp||1 year ago|
|moenavigatormain.h||1 year ago|
|moenavigatormain.ui||1 year ago|
|qbrowsertabwidget.cpp||2 years ago|
|qbrowsertabwidget.h||2 years ago|
MoeNavigator relies on Qt 4.8 dependencies. Please make sure to have the development files of the following libraries installed before you start compiling MoeNavigator:
To compile MoeNavigator you need to invoke qmake, followed by make. To avoid messing up the source directory with build files, you can create a subdirectory named “build” and call qmake from there:
After that, you can run make as usual:
(X represents the number of CPU cores your computer has)
The “build” directory is in the .gitignore file so that everything in there will not be committed.
There are no questions that are really frequently asked, so I decided to answer some questions that might be interesting.
You can contribute by reporting bugs or write patches that improve MoeNavigator or fix issues. Bug reports and patches can be sent by creating a ticket on codeberg.org or by sending an E-Mail to Moritz Strohm (see the AUTHORS file for the mail address).
No, there is no code of conduct. Everything is fine as long as people treat each other with respect.
I can explain the last point in more detail:
Once upon a time, Firefox was a privacy respecting browser by default. There were no telemetry antifeatures, no experiments with users and no tracking support. Oh, and addons weren’t suddenly disabled.
Today, Firefox is different:
The pocket “feature” which is based on a non-free service and collects intimate information: https://dustri.org/b/firefox-youre-supposed-to-be-in-my-pocket-not-the-other-way-around.html
Addons get suddenly disabled without a warning: https://bugzilla.mozilla.org/show_bug.cgi?id=1548973
The telemetry antifeature: https://www.ghacks.net/2018/09/21/mozilla-wants-to-estimate-firefoxs-telemetry-off-population/
Experiments with users:
Support for link tracking: https://www.bleepingcomputer.com/news/software/mozilla-firefox-to-enable-hyperlink-ping-tracking-by-default/
Other browsers like Chrome, Safari, Edge and Opera are not free software and therefore should not be trusted. There is Chromium as the free base of Chrome, but its integration of Google services might become problematic in regard to privacy, especially when you read news like these:
Absolutely not! EME is an antifeature that can be used to restrict the spreading of knowledge.