hooks: make_lock is tristate

Missed in 260a7a01.

setup_rhodecode: fix --force-no - force_ask is tri-state

Missed in 260a7a01b.

fixed multiple IP addresses in each of extracted IP.
- different setup uses different proxy emthods. We make sure
we always select the first IP

fixed sort of permissions summary it's now perm+name
unified permissions summary for users and user groups

swap repo-size with settings in summary. It somehow
feels more natural to be on bottom, it's just easier to click

usermenu
- show more space for email
- move notification into link

summary: redirect from repo URLs with #branchname to changelog with this branch

This implements partial support for the Mercurial syntax for specifying
revisions so https://secure.rhodecode.org/rhodecode/#beta works both for
pulling with Mercurial and browsing.

This uses javascript, and has a bit of extra support for onhashchange in HTML5 browsers.

pullrequests: state "closed" explicitly

A closed-as-in-locked icon did not communicate the closed-as-in-inactive state
clearly.

Instead we say "Closed" and make the text greyed out. Not pretty but more
efficient.

config: rename options to show_revision_number and show_sha_length

'sha_show_numeric_rev' had nothing to do with the sha value.

The revision numbers are kind of native to Mercurial and there they are known
as 'revision numbers'.

'sha_len' was very short and didn't clarify that it only controlled what was shown.

These settings are currently only used in the changelog, but they should be used everywhere.

config: automatically assign instance_id for host and process if it has been set to *

It is no longer a problem to invent new instance_ids on startup - unused keys
will be deleted.

css: don't float the paginator - let it take the space it needs

Fixes rendering issue on the "messages" page.

more usage of fixture tools
in tests

- age tests cannot be dynamic, there are cases when age calculation
doesn't work
- use parametrized to test age

added new fixture classes
and detaching/deleting forks
tests

recursive forks detach
- added API attrs for option to delete or detach forks
- deleting repos with attached forks raises an special Exception

ldap: handle more elegantly that python-ldap isn't installed when trying to use ldap

Don't fail with
AttributeError: 'NoneType' object has no attribute 'SCOPE_SUBTREE'
in the log.

#749 and #516 Removed dupliciting of repo settings for rhodecode admins and repo admins
- repo admin now is allowed the same set of operations as the rhodecode admin
- single logic for forms/validations/permissions
- fixes #805 update external repo via webinterface
-

moved permission management into separate entity.
- this solves issues when whole form submision could influence permission management
particular case is that when repo group permission is revoked and user is no longer able to update repository settings

celery tasks: use None as special value

Use a more common pattern.

follow Python conventions for boolean values

True and False might be singletons and the "default" values for "boolean"
expressions, but "all" values in Python has a boolean value and should be
evaluated as such. Checking with 'is True' and 'is False' is thus confusing,
error prone and unnessarily complex.

If we anywhere rely and nullable boolean fields from the database layer and
don't want the null value to be treated as False then we should check
explicitly for null with 'is None'.

user group: sort lists of current and available members by username

It was hard to navigate lists with 200 users in "random" (user_id?) order.

sort permission lists by (repository) name

This also exhibits too much code in templates and code/template duplication.

missing changesets should return 404 not redirect + flash.
It feels more correct.

move the existing changeset checks bellow other checks else it can throw exceptions for non
existing repos

compare: reorder columns in changeset list - this feels more natural to me

- but we should probably also try to be more consistent.

templates: enforce more consistency by being less flexible in templates

All pages must define page_nav.

context_bar may only be used on relevant repository pages, and the 'current'
parameter is mandatory.

repository: cleanup and alignment of repository editing templates

Too much duplicated code.

pullrequests: fix non-js defaults for repo owner

Owner of default_other_repo was never sent to the the template ... and the
template would fail if it had been sent. Instead we set default_other_repo_info
to the other_repos_info struct and use that to find the owner.

pullrequest: use simple link for 'Change style'

This seems to be more obvious and not require any explanation.

The checkbox is kept but made invisible - just to avoid controller changes.

changelog / compare: adjust titles

Clarify what shows changesets and what more see changesets as revisions that
specify snapshots that are compared.