It seems that VBulletin membergroupids have changed.  ID 7 no more
means a moderator - instead all moderators have 2 and dev team
has additional ID of 19.

The mapping of membergroupids to moderator status is now done just
once at login time.  Previously the group number was checked whenever
one wanted to determine moderator status, although a boolean moderator
field had been set at login.

Additionally fixed emailHash saving in ForumUser#clientUser - previously
the result of calculation was just thrown away.

Not the prettiest solution, but at least it results in correct code
(unlike the previous concatenation without spaces).

So that by specifying --ext-namespaces=Foo.Bar we're able to recognize:

    Foo.Bar.define("MyClass", {
    });

CSS Specification uses the term <length> to denote 2em, 3px, etc
values with units.

Using CSS lexer instead of JavaScript lexer simplifies CSS parsing
quite a bit (which is kind of obvious :)

It also removes some of the strange cases where CSS parsing failed
(like when the CSS identifier contained the word "default" which is
a keyword in JavaScript).

The sort data had been changed so that it now contained meta field
instead of private and removed fields directly.

Fixed it, so that public members are now again listed before deprecated,
private and removed ones (as a new thing now also taking account the
deprecated ones).

Enhanced the documentation to further explain how the algorithm works.

Eliminated lots of magic numbers from code and replaced them with
variables - most of which are calculated from the three main constants
defined at the beginning.  This should make it much simpler to enhance
the function in future.

For some reason they were previously saved as strings.

Previously only editing the comment was logged, but logging the deletion
and undo of deletion are quite important too.

Users aren't really able to decide whether they just want to post a
comment or report a problem.  Practice showed that the "problem" action
was used more or less randomly.  So getting rid of it completely.

Removed the whole action-combo and related HTML.  Incorporated some of
the help text into the general commenting help section.

To clean up "action" field from database, run:

    db.comments.update({}, {$unset: {action: 1}}, false, true)

For over month old comments, showing the date is more informative -
people usually know which month it is now.  Telling 6 months ago doesn't
tell me if the comment was posted in previous year - much more
informative is to just say it was posted in November '11.

Use round() instead of ceil() when calculating "x units ago". Using
ceil() resulted in:

 - 59 seconds ago --> just now
 - 60 seconds ago --> 1 minute ago
 - 61 seconds ago --> 2 minutes ago

The same happened with other units.  With rounding the 1 minute period
is much larger than just 1 second.

The output of parsing was only barely tested and so some things were
just completely missing from output.

Encapsulate the checkboxes completely inside commentindex view, which
does the saving of checkbox states completely within itself, only
firering settingChange event for the controller to listen on.

No need to use cookies, we already have Docs.Settings class that uses
localStorage and is meant just for that - storing various settings.

Add #setMasked method to comments view and use that for
masking/unmasking.

Also rename #recentcomments-container to #comment-index-container for
consistency.

And remove absolute positioning from comment controls that's no more
needed.

Also remove check for commentMeta.reads - copy paste error.

Masking recent comments while loading, and remembering of filters
of recent comments.

Recent comments page now has two checkboxes:

  - hide read
  - sort by score

Not an efficient implementation, but should be good enough as only
moderators use the feature.

Loading the recent comments page caused a crash when there were no
comments.

Add Windows platform.