Sign in
gwt
/
gwt
/
cc2d0ea68a00456641ffd7ff55b890af8aacc841
/
eclipse
/
reference
/
code-museum
802da20
Update HistoryImpl to use modern browser standards
by Daniel Kurka
· 11 years ago
d54a4bd
Mirroring got broken around the merge from branches/2.1, although I'm
by gwt.mirrorbot@gmail.com
· 15 years ago
6020e7e
Updating code museum launch configurations to use platform independent jars, and to use DevMode.
by jlabanca@google.com
· 15 years ago
e0fa5b1
Merge farewellSwt into trunk.
by jat@google.com
· 15 years ago
e606905
Adding a white background the to noscript warning so it shows up against all backgrounds.
by jlabanca@google.com
· 15 years ago
3f17d37
Adding a code museum file to run Issue3892 tests that I missed in r6163.
by jlabanca@google.com
· 16 years ago
e0309fa
Allows multiple GWT apps to preview native events in IE.
by jlabanca@google.com
· 16 years ago
1d30610
Additional fix for issue 3903. Adds noscript tags to additional samples
by fredsa
· 16 years ago
085b3fe
Updates the code museum to use HostedMode instead of GWTShell, and adds a war/ directory.
by jlabanca@google.com
· 16 years ago
b4c03e2
A couple of pieces left out of the previous commit.
by jat@google.com
· 16 years ago
e7f61a7
Merge from releases/1.6:r4198:4268,4269:4297,4299:4320:4321:4366 into trunk
by jat@google.com
· 16 years ago
96c7556
Merging releases/1.5 into trunk
by scottb@google.com
· 17 years ago
fb085c3
Added a test for issue 1897 "Attaching and detaching a RichTextArea too fast crashes GWT" to the museum.
by jlabanca@google.com
· 17 years ago
8bf96e1
Modified the code museum to load all issues at starup and allow the user to select one at a time. Style sheets are loaded dynamically to avoid conflicts in style names.
by jlabanca@google.com
· 17 years ago
6fe8edd
Initial commit towards adding a new "reference" section for the project's own reference over time, including an HTML encyclopedia (to easily reproducible/check HTML behavior across browsers) and a "code museum" that will house little code snippets that we create when testing issues, etc. The point is to accumulate a set of reference materials we can continue to keep around instead of editing Hello locally and throwing it away :-)
by bruce@google.com
· 17 years ago