Add StringBuilder.appendCodePoint(int)

Change-Id: I60e008d4d7264f388492969a5042caf6a3aba435
Removes the DST workaround in CalendarUtil.

Due the way javascript handles DST new Date(YYYY,mm,dd) may result
in (YYYY, mm, dd-1). For example; in BST timezone:
 >> new Date("2013, Oct 20")
prints Sat Oct 19 2013 23:00:00 GMT-0300 (BRT)

To workaround this issue, DatePicker was patched in r5218:
https://code.google.com/p/google-web-toolkit/source/detail?r=5218

However later java.lang.Date emul fixed the issue in r6674:
https://code.google.com/p/google-web-toolkit/source/detail?r=6674

This workaround is no longer needed and causes other problems.

The patch is manually tested with setting the timezone to BST in
OSX and restarting Chrome.

partially fixes issue 4785

Change-Id: Ie534fce157c288df2bedcdc51abc882eb7ccba28
DatePicker improvements

Add the ability to navigate through the years
Add the ability to select the month via a dropdown list
Add the ability to select the year via a dropdown list
Keep the backward compatibility, the datepicker is rendered as before if we don't use any of the above options

Fix issue 3520
Change-Id: I43df1792216403f324df024fd3503f4136149a1a
cleans up Compiler.java by moving out CompilerOptionsImpl

Change-Id: Iaac0012658707ea7ade564a6b3f4281c4e4e8e25
Avoid naming clashes between static members and top level names.

Static functions and methods are defined in the global scope. Two potentially unsafe
situations might occur if a static variable/function gets assigned a name that is already
a top level name (e.g. NaN, URL)

(1) The global variable/function gets overwritten and that would affect non GWT code that
migh be running alongside a GWT application.

(2) Static variables are just declared at the top scope and left uninitialized unless they
had an explicit assignent in their declaration. These uninitialized variables would have a
value of undefined (in the absence of name clashes) which is equivalent to null, preserving
java semantics. However if the name was already used at the top scope, they might have already
a non null value resulting in an incorrect execution.

We avoid clashes by blacklisting names that are normally at the top scope.

A better solution is to ensure GWT code is always enclosed by its own scope.

Change-Id: Ifd4b3a111764c239863062b372c5a06e7f7d6ef4
Removes the extra precision from date when entered from picker or textbox

When thedate  entered from text box or date picker, the date might have higher
precision then the datebox can display. This causes an extra value change event
when the textbox loses focus or date picker closes - which happens any time a date
is selected from the date picker. So it ends up in two value change event fires.

The change makes a round-trip on format and parse while accepting the date from
user to ensure that precison is no higher than the precision that can be
represented in the datebox.

fixes issue 4785

Change-Id: I35f50d0d5239560c1466697678040d8eefedc2a4
Review-Link: https://gwt-review.googlesource.com/#/c/4631/
fixes two invalid Event rebind rule paths

Change-Id: Ib53d7cc7e116db80faed9cc9cd8e4bc6ee464d8b
Replace Java 7 code with Java 6

* Integer.compare was added in Java 7

Change-Id: If26fe293249ce236c9890e57b59a21316c87869b
Fixes a bug where MenuBar steals focus even focusOnHoverEnabled is set to false

fixes issue 3884

Change-Id: I8dcfabc7d05000e5ee6cd0fb84dc5bbf0bc35ce2
Tweak SDM UI to handle really long module names

Currently, SDM's modal "Choose a module to recompile" dialog has no
bounded width, so a really long module name could force the Compile
button way off the right side of the screen.

This patch makes two minor tweaks to SDM's CSS:

  1. It sets the 'right' property on the dialog container element, so
     that the dialog will stay within the visible area of the page.

  2. It sets the 'word-wrap' property to 'break-word' so that the
     browser is allowed to break really long words (e.g., module
     names) to fit within the containing element.

Change-Id: Iaf5684e04ff2f6e3a4a5633a3e969633445bcc36
Fix JsArray doc and coercion

Fixes issue 8361

Change-Id: I4e92eb2356354f862e216ae87e8b46ef24745f48
Remove type checks on Array.set if disabled.

Remove typechecking on array set if -XdisableCastChecking is set.
This speed up every Array.set and thus many Collections such as
Arraylist since they already do redundant checking.

Change-Id: Iaaa9c0cc077b0be185a65283f7f0fdff46727697
Further CodeSplitter related refactor.

Some passes after codesplitting need to reason about fragment load order. JsStringInterner is
an example of such a pass. JsStringInterner interns string that appear more than once in the
source by assigning them global variables. Because occurrences of the string might be spread
across fragments, it needs to ensure these variables are loaded before they are referred to.

This patch removes JProgram knowledge about fragment type and load order. Instead JProgram now
delegates these queries to FragmentPartitioningResult; making it easier in the future to
have different fragment load topologies (i.e. more than one leftover so to speak).

Change-Id: Ic16e8a88e2659368717d07442f47b384107388e7
Make StringBuilder.appendCodePoint consistent.

Change-Id: I150d7355b2cd51523348c6521602f196031d0a61
Review-Link: https://gwt-review.googlesource.com/#/c/4730/