You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Moritz Strohm 1d8473d26e added missing Qt library in project file, updated about dialog 1 month ago
DefaultSettings Improvements to per-page settings (disabled by default) 5 years ago
EngineInterfaces EngineInterface_MNE: changed order of svg widget initialisation 1 year ago
oldcode Moved EngineInterface and DefaultSettings directory 5 years ago
.gitignore moved BrowserTabWidget class to separate files 1 year ago
AUTHORS Finished conversion to qmake project 5 years ago
BrowserTabWidget.cpp fixed MNE engine tab visibility 1 year ago
BrowserTabWidget.h fixed Qt slots in BrowserTabWidget class 1 year ago
COPYING Finished conversion to qmake project 5 years ago
Changelog Finished conversion to qmake project 5 years ago
ConfigurationWindow.ui GUI: Address bar, forward, back, reload buttons are working, User Agent string is set; change to https if no protocol specified 5 years ago
DevelopmentGuidelines.txt use shared_ptr when dealing with browser engine instances 2 years ago
EngineSettings.h improved coding style compatibility, added copyright header to files 2 years ago
GUIHandler.cpp improved coding style compatibility, added copyright header to files 2 years ago
GUIHandler.h improved coding style compatibility, added copyright header to files 2 years ago
MoeNavigator.png Finished conversion to qmake project 5 years ago
MoeNavigator.xpm Finished conversion to qmake project 5 years ago
README.md updated README file 1 year ago
configurationwindow.cpp improved coding style compatibility, added copyright header to files 2 years ago
configurationwindow.h improved coding style compatibility, added copyright header to files 2 years ago
configurationwindow.ui Worked on multi tab support (not enabled yet) 5 years ago
main.cpp main.cpp, moenavigatormain.h: improved coding style conformity, added documentation 1 year ago
moenavigator.pro added missing Qt library in project file, updated about dialog 1 month ago
moenavigatoraboutdialog.cpp improved coding style compatibility, added copyright header to files 2 years ago
moenavigatoraboutdialog.h improved coding style compatibility, added copyright header to files 2 years ago
moenavigatoraboutdialog.ui added missing Qt library in project file, updated about dialog 1 month ago
moenavigatormain.cpp fixed MNE engine tab visibility 1 year ago
moenavigatormain.h moenavigatormain: replaced poiners with QPointer instances 1 year ago
moenavigatormain.ui fixed qtabwidget layout problems, made EngineInterface_MNE a compatible EngineInterface implementation again 1 year ago
qbrowsertabwidget.cpp improved coding style compatibility, added copyright header to files 2 years ago
qbrowsertabwidget.h improved coding style compatibility, added copyright header to files 2 years ago

README.md

MoeNavigator README

Installation

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:

  • Qt 4.8
  • QtWebKit (libqtwebkit-dev)

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:

qmake ..

After that, you can run make as usual:

make -jX

(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.

Randomly answered questions

There are no questions that are really frequently asked, so I decided to answer some questions that might be interesting.

How can I contribute?

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).

Does this project have a code of conduct?

No, there is no code of conduct. Everything is fine as long as people treat each other with respect.

Why develop another web browser?

  1. To learn how to write a web browser.
  2. To have n+1 web browsers => more diversity ;)
  3. Major browsers suck.

I can explain the last point in more detail:

Firefox

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:

Other browsers

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:

Will MoeNavigator support Encrypted Media Extensions (EME)?

Absolutely not! EME is an antifeature that can be used to restrict the spreading of knowledge.