Web editor improvements, and added tips page

[Justin B Rye]

Enrico Zini wrote:
> Do you think you can produce the relative javascript error messages?
> There should be some sort of javascript console that shows them.

On http://debtags.alioth.debian.org/edit.html:

 Error: missing name after . operator         
 Source File: http://debtags.alioth.debian.org/js/debtags.js         
 Line: 632, Column: 6         
 Source Code: node.class = val;         
         
 Error: Tagset is not defined         
 Source File: http://debtags.alioth.debian.org/edit.html  
 Line: 27         
	          
 Error: getQuery is not defined         
 Source File: http://debtags.alioth.debian.org/edit.html
 Line: 423         

Meanwhile on http://debtags.alioth.debian.org/todo.html there's an
obvious <./p> and the following errors:

 Error: missing name after . operator
 Source File: http://debtags.alioth.debian.org/js/debtags.js
 Line: 632, Column: 6
 Source Code: node.class = val;

 Error: getQuery is not defined
 Source File: http://debtags.alioth.debian.org/todo.html
 Line: 15

 Error: setVisible is not defined
 Source File: http://debtags.alioth.debian.org/todo.html
 Line: 95

No problems on http://debtags.alioth.debian.org/cloud/.

> I'm not very sure what you mean with neighbours in "dpkg-list-space".

The package's "neighbours" in an old-style dpkg -l, or aptitude
listing; I always used to go through debtags-edit in alphabetical
order... I can use

 apt-cache --generate pkgnames | sort |  grep -C5 ^xfonts-foo

... then find how they're tagged (assuming my local tag-data is up
to date), and then find those tags in the editor and add them, but
that's not much fun compared to the magic tag-guesser!
-- 
JBR
Ankh kak! (Ancient Egyptian blessing)