pulling in latest code from dusanx

1 files changed, 17 insertions, 4 deletions

diff --git a/TODO b/TODO
index 2f5bef8..c6eeda3 100644
--- a/TODO
+++ b/TODO
@@ -1,11 +1,24 @@
+ASAP
 * implement all the ideas from README
+* get a logo
+* improve site
 * Support for binding keyboard shortcuts in config file.
+* when launching new instance, don't just try 'uzbl' and then './uzbl', rather launch a new uzbl in the same way the current uzbl instance was started. (same command, same arguments, except --uri)
 * where to put proxy config? webkit support?
-* do not store the 'http://' part in the history file
-* improve commandline arguments
-* have a better look at /merge the fifo code from barrucadu and friends
-* history logging broken. logs always starting url because i made uri const
+* implement XDG basedir spec (config is done, but not cache/data, which I presume we'll need at some point)
+* check configured commands if they end on .sh so users don't need to prepend /bin/<shell>
+* implement a more advanced dmenu alike that behaves like FF's awesomebar and where you can search in url + window title
+* recognize -h with GOption?
+* implement a vimperator-like link following scheme.  but let user pick his favorite characters to construct the "link identifiers" with.
+* add a keybind to hand the current url to an external scrips, so you can edit it and/or store it in the primary and secondary clipboards
+* use http://library.gnome.org/devel/glib/stable/glib-Hash-Tables.html#g-hash-table-insert for tracking bindings and wherever we use structs and ugly loops
+* fifo -> socket. so you can do question-response. socket is slightly more complicated so we'll need to create a uzblctrl
+* select/fork based instead of the pthread stuff -> drops dependency, more lightweight.
+* on website, see if we can <pre><?php include('..'); ?></pre> the documentation inside the uzbl project itself, so we need to maintain the stuff on only 1 place
+* see if we can use the github bugtracker (anonymous posting allowed?)
+* allow user to change bindings for navigation (up,down,left,right, page up, page down etc)
 
 SOMEDAY:
+check if we can make the settings loading less hard coded. eg( keep a list of all settings, and for each one, try to load it)
 figure out caching with webkit and in general how we can speed up everything
 figure out how webkit intercepts key input