GitLab

Move the GET_COOKIE function to common.inc.php and sort by popularity by
default.

Calculate weighted popularity by normalising the download count against the
number of days an item has been available.

Highlight the current screen resolution in the resolution filter list

Rather than show a category list and search box, show a list of all
backgrounds, with options to filter this list.

[models]
 * Remove category parameter from filtered models
 * Add get_category_list function

[views/backgrounds]
 * Add category list to filter box

[controllers/backgrounds]
 * Always get a list of themes, even if no category is set

The cookie path needs to be set to prevent conflicts when two cookies are
set with the same name, but with paths that both apply to the current URL.

Remove scrollbars from theme and background items and make each item more
compact.

If the parameters need to be persistant, then they need to be stored in a
cookie.

Set the content type of all gtk2, metacity and icon themes to be
x-gnome-theme-pacakge.

Increase the vertical item size to allow for the new download count
information.

Escape the closing tags when written by javascript to avoid confusing
the w3 html validator.

See: http://www.htmlhelp.com/tools/validator/problems.html#script

Allow the user to select between sorting items by name and by popularity.

Calculate the sort field from the GET parameter or from a cookie.

If the GET parameter is available, store it for the user in a cookie in
case the GET parameter is lost later.

Obfuscate e-mail address to prevent harvesting by spam bots. Print the
address to html using rot13 encoding and then convert back to normal using
client side javascript. In the case that javascript is not available, the
e-mail addresses are not made available either.

Set the content type when downloading gtk, metacity or icon themes to allow
the browser to open the file in the theme installer. The extension is also
checked because the application/x-gnome-theme-package type can only be set
if the archive is gzipped.

Template variables need to be initialised in the controller, before the
view is run.

$search_text is always initialised, so the isset() check is redundant.

Accessing an non-existent index in an array will cause PHP to generate a
warning.

Don't try to access the sub-expression matches unless the match was
successful (i.e. the index exists in the matches array).

These variables are optional in the view, but must be initialised to
prevent PHP from warning that they are undefined.

Accessing an index in an array such as $_GET if it does not exist will
cause PHP to generate a warning.

Changes to the table structures where not reflected in the code, so
caused warnings from PHP about undefined indexes.