aboutsummaryrefslogtreecommitdiffhomepage
path: root/docs/FAQ
diff options
context:
space:
mode:
authorGravatar Dieter Plaetinck <dieter@plaetinck.be>2009-06-07 16:03:46 +0200
committerGravatar Dieter Plaetinck <dieter@plaetinck.be>2009-06-07 16:03:46 +0200
commit96f9618643fe17b09452974a59d67063c8de06d6 (patch)
tree7b270730c1f440ea8103c9cfa4794b05e84c2b47 /docs/FAQ
parentec14eba5433c5813af1a7bc99f450a413825a6df (diff)
faq entry about tabs + clarify url changing
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ16
1 files changed, 15 insertions, 1 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 79e1364..ef5df5f 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -17,12 +17,26 @@ useful with history/bookmarks) with a limited set of keystrokes. see man dmenu.
You can also use it to make edits to a uri (press tab to load it into the
search field) or type a url from scratch, though dmenu
is not the most suitable editor. We're looking into a better way to make edits.
-Zenity is also an option, if you want copy-paste support.
+Tools such as Zenity are also quite suited for this.
+And you can always make keybinds to load the current uri in the command field, paste/load urls from
+clipboard etc.
### Where are the widgets (forward, back,.. button etc)
Uzbl's layout only contains what you really need to see. we only have a statusbar, which even can also be disabled. There are no buttons, but we do
have lots of keybinding possibilities.
+### No tabs? Why do you need a new window for each page?
+We stick to "one page per uzbl instance" because that's a simple, clean and flexible method. We believe "multiple instances management" is something that must
+be handled outside of uzbl by a separate/different program. Here are some solutions:
+
+ * many window managers can (and should) handle this by default. Xmonads tabbed layout, Wmii's stacked layout and so on.
+ * you can write a custom script. The only thing you need to do is focus/maximize the instance you want,
+ keep the others out of sight and use tools like dmenu and wmctrl to switch instances.
+ This allows you to use application-specific properties (such as uzbl tag, name etc).
+ For more information about this approach, see docs/multiple-instances-management
+ (we'll maybe include some sample scripts in the future)
+ * We might implement a GtkPlug (Xembed child) in the future. So you could abuse that.
+
### What? No support for bookmarks/history/downloads/cookies/... ? Your project sucks!
We do not support *management* of those things, because we believe a browser should only do browsing. We are firm believers in the unix philosophy.
You have to look at the bigger picture. In fact, we do support all these things. Take bookmarks as an example: