X-Git-Url: https://git.armaanb.net/?p=chorizo.git;a=blobdiff_plain;f=README;h=373d692a0d7d09a965c3f75a23f2b5303f044a87;hp=0d91d11e431243056d933e3d4e4c080e7e58b27c;hb=HEAD;hpb=76edc528c4245391b53a08a8fb56cfdba926e57d

diff --git a/README b/README
index 0d91d11..373d692 100644
--- a/README
+++ b/README
@@ -1,36 +1,108 @@
-sn - sonst nix
-==============
+        _                _
+    ___| |__   ___  _ __(_)_______
+   / __| '_ \ / _ \| '__| |_  / _ \
+  | (__| | | | (_) | |  | |/ / (_) |
+   \___|_| |_|\___/|_|  |_/___\___/
+  https://sr.ht/~armaan/chorizo
 
-This is a minimalistic web browser using Gtk3 and WebKit. "Sonst nix" is
-german and translates roughly to "nothing else". sn is simple and meant
-to stay simple.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+
+A simple web browser using GTK+ 3, GLib and WebKit2GTK+.
 
 Features:
+    - A WebKit2 viewport
+    - An input box to change the URI, search the current page, or
+      search the web
+    - Tab management
+    - Full keyboard control
+    - An ini configuration file
+    - Built-in download manager
+    - Web feeds indicator
+    - Global content zoom
+    - Cooperative instances using FIFOs
+    - Certificate trust store
+    - User script support
+    - Extensions
+
+Refer to the manpages chorizo(1), chorizo-usage(1), and
+chorizo-config(5), for more information.
+
+Installation
+------------
+
+The following C libraries are required:
+
+    - GTK+ 3
+    - WebKit2 API for GTK+ 3
+    - gst-libav, gst-plugins-good - for media playback
+
+To generate the manpages, scdoc is required. This isn't necesary on
+release tarballs.
+
+chorizo expects to be run on a POSIX-ish operating system.
+
+To build and install the program:
+
+    $ make
+    # make install
+
+
+Background information
+----------------------
+
+What chorizo is and what it's not
+
+  chorizo does what I need. It won't do other things. I'm open for
+  contributions but please don't be upset if I turn them down -- which
+  might happen if it's a feature that I simply don't need.
+
+  chorizo does not compete with powerful browsers like dwb or luakit, nor
+  with monstrous applications like Firefox or Chromium. Because under
+  the hood chorizo is powered by WebKit, however, it is on par with
+  browsers like Safari for page rendering features.
+
+How is chorizo related to lariza?
 
-	- A WebKit viewport
-	- Global content zoom
+  chorizo is a fork of the lariza browser by Peter Hofmann. I wanted
+  to take it in a slightly different direction (mostly just adding
+  features not considered to be in the spirit of lariza), so I forked
+  it. The name was changed in order to reduce confusion between the
+  two browsers as they grew apart. The versioning scheme was also
+  moved away from being calendar-based.
 
-Planned features:
+  Features that this fork has that lariza is missing:
+    - Configuration file
+    - Revamped download manager
+    - New, ergonomic keybindings inspire by both Emacs and Vim
+    - Better default directories
+    - Easily togglable images and JavaScript
+    - Cleaned up source code
+    - Easy web searching
+    - User stylesheet support
+    - A variety of tweaks and adjustments that make the experience nicer
 
-	- An input box to change the current URL
-	- vi-like shortcuts
-	- Adblock
-	- Pluggability into suckless' tabbed (preferred) or native tabs
+Migrating from another browser
+------------------------------
 
+From lariza:
+  1. Copy the relevant paths from ~/.config/lariza to
+  ~/.local/share/chorizo. Read chorizo(1) for full details on the
+  correct paths.
 
-Why WebKit instead of WebKit2?
-==============================
+  2. Your symlinks from /usr will broken, so you should relink everything.
 
-While WebKit2 has fancy process separation and all that stuff, it turned
-out to be pretty slow and clunky. Plus, ideally, sn will be plugged into
-suckless' tabbed -- so it wouldn't benefit from process separation
-anyway.
+  3. Read lariza-config(5), as the keybindings are radically different
+  out of the box. Everything is configurable, however, and you can
+  reconfigure the bindings to act just like your previous browser.
 
+From Firefox/Chromium/Brave/etc:
+  1. Set your expectations right. Read the background information
+  section of the README.
 
-Literature
-==========
+  2. Copy the cookie database into ~/.local/share/lariza/cookies.db.
 
-API references:
+  3. Read all the manpages.
 
-	- http://webkitgtk.org/reference/webkitgtk/stable/index.html
-	- https://developer.gnome.org/gtk3/stable/index.html
+Copyright
+---------
+MIT License, see the LICENSE file for more information.