forked from OpenUserJS/OpenUserJS.org
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Replace `NB`'s **NOTE** Minimal usage of `kbd` markup for keyboard sequence emphasis but still centric on markdown Applies to OpenUserJS#202 and OpenUserJS#909
- Loading branch information
Martii
committed
Mar 31, 2016
1 parent
cddac52
commit e5732c0
Showing
6 changed files
with
55 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,65 @@ | ||
## QupZilla | ||
|
||
QupZilla is a new and very fast Qt browser. It is actively developed and uses open standards (so it's easier for programmers to work with it). It aims to be a lightweight web browser available through all major platforms. | ||
![QupZilla icon][qupzillaIcon] | ||
|
||
This project has been originally started only for educational purposes. But from its start, QupZilla has grown into a feature-rich browser. The very first version of QupZilla has been released in December 2010 and it was written in Python with PyQt4 bindings. After a few versions, QupZilla has been completely rewritten in C++ with the Qt Framework. | ||
QupZilla is very fast Qt based browser. It is actively developed and uses open standards *(so it's easier for programmers to work with it)*. It aims to be a lightweight web browser available through most major platforms. | ||
|
||
The project was originally started for educational purposes. From the start QupZilla has grown into a feature-rich browser. The very first version of QupZilla was released in December 2010 and it was written in Python with PyQt4 bindings. After a few versions QupZilla has been completely rewritten in C++ with the Qt framework. | ||
|
||
QupZilla ships with its own port of Greasemonkey as an extension. | ||
|
||
### Installing GreaseMonkey | ||
|
||
To get userscripts going with the GreaseMonkey Extension, first you have to enable it from the Preferences → Extensions menu item by selecting GreaseMonkey in the list and then click the checkbox, and finally clicking the "OK" button. | ||
|
||
![Screenshot of QupZilla Extensions][qupzillaExtensionsScreenshot] | ||
|
||
Once it is enabled turning on the View → Status bar menu item will show the GreaseMonkey icon in the status bar. | ||
|
||
![Screenshot of QupZilla with GreaseMonkey status bar][qupzillaScreenshot3] | ||
|
||
### Installing Userscripts | ||
|
||
Once GreaseMonkey is enabled, installing userscripts from OpenUserJS.org is simple. Navigate to the OpenUserJS page for the script, then click the blue "Install" button at the top of the page. | ||
|
||
![Screenshot of an OpenUserJS script page][oujsScriptPageScreenshot1] | ||
|
||
QupZilla via the GreaseMonkey Extension will display a screen showing you what websites it can access, optionally the source code, and a warning to only install scripts from sources that you trust. If you do want to install the script, click the "Yes" button, otherwise click "No". | ||
|
||
![Screenshot of QupZilla script installation][qupzillaScreenshot4] | ||
|
||
Installing userscripts from other sources is a similar process. You just need to find the installation link for the script. This will be a button or link to a file with a name that ends ".user.js" | ||
|
||
After installing a userscript, you won't normally notice any further changes until you visit a website that it runs on. | ||
|
||
### Managing Userscripts | ||
|
||
Clicking on the GreaseMonkey icon at any time will pop up a dialog that shows you what userscripts are installed. This is also available from the Preferences → Extensions menu item by selecting GreaseMonkey in the list and then clicking the "Settings" button. | ||
|
||
![Screenshot of QupZilla script management][qupzillaScreenshot5] | ||
|
||
### Trouble shooting | ||
|
||
If you think a userscript is causing problems, the easiest way to check is to switch off GreaseMonkey, reload the web page, and see if the symptoms go away. You can do this by opening Preferences → Extensions menu item and select GreaseMonkey and then untick the checkbox, then the "OK" button. If it looks like a script problem and you have more than one script running on a web page, you can disable them all in GreaseMonkey's dialog "Settings" button, or the status bar icon, then re-enable them one by one, until you find the culprit. Remember to reload the web page each time - userscripts normally only run when a web page loads. | ||
|
||
Sometimes, when you use more than one userscript on the same web page, they need to run in a particular order. You can change the order by renaming the .user.js files manually by clicking the Open scripts directory button. | ||
|
||
Curently to enable the remote debugging feature in QupZilla with <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>i</kbd> an environment variable with a name of `QTWEBENGINE_REMOTE_DEBUGGING` needs to be set with an available numeric TCP port such as `12345`. This applies to all platforms. | ||
|
||
### More | ||
|
||
* [Get QupZilla][qupzillaBrowser] | ||
* [QupZilla on Wikipedia][wikipediaQupZilla] | ||
* [QupZilla Issue Tracker][qupzillaIssueTracker] | ||
|
||
[githubFavicon]: https://assets-cdn.github.com/favicon.ico | ||
[oujsFavicon]: https://raw.githubusercontent.com/OpenUserJs/OpenUserJS.org/master/public/images/favicon16.png | ||
[qupzillaIcon]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/qupzilla_icon.png "QupZilla" | ||
[qupzillaExtensionsScreenshot]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/qupzilla1.gif "Enabling the GreaseMonkey Extension" | ||
[oujsScriptPageScreenshot1]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/openuserjs_script.gif "Ready to install a script" | ||
[qupzillaScreenshot3]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/qupzilla3.png "QupZilla start page with GreaseMoneky enabled" | ||
[qupzillaScreenshot4]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/qupzilla4.gif "Installing a script" | ||
[qupzillaScreenshot5]: https://raw.githubusercontent.com/wiki/OpenUserJS/OpenUserJS.org/images/qupzilla5.png "Script management" | ||
[qupzillaBrowser]: http://qupzilla.com/ | ||
[wikipediaQupZilla]: https://www.wikipedia.org/wiki/QupZilla | ||
[qupzillaIssueTracker]: https://github.com/QupZilla/qupzilla/issues |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters