This site is specially designed for those people who feel tired while
surfing internet or during work on internet. You can enjoy your time
here. Hope you all like and send your best comments to update site.
http://itstime2enjoy.blogspot.com/2009/08/beware-of-two-way-mirrors-in-trial.html
--~--~--
Having MapWidget implement RequiresResize would seem to be the right
approach. I can see how the maps code would need to be informed when it is
resized, as it needs to create the appropriate number of tiles on each axis.
Does this sound reasonable to you, Eric?
On Mon, Sep 28, 2009 at 9:18 PM, jd
Yeah sorry I was not sure if this was more of a development topic or
typical user problem.
I tried your suggestion of map.checkResizeAndCenter() and it works
perfectly. It also seems a better solution than my original
SimplePanel place holder.
It seems that the Google map object initializes its
Revision: 6243
Author: j...@google.com
Date: Mon Sep 28 18:13:04 2009
Log: Fix remote tests.
Patch by: jat
Review by: rjrjr (TBR)
http://code.google.com/p/google-web-toolkit/source/detail?r=6243
Modified:
/branches/farewellSwt/user/src/com/google/gwt/junit/JUnitShell.java
===
Revision: 6242
Author: j...@google.com
Date: Mon Sep 28 17:01:43 2009
Log: Fix inadvertent removal of -batch module from remoteweb and selenium
tests.
Patch by: jat
Review by: fabbott
http://code.google.com/p/google-web-toolkit/source/detail?r=6242
Modified:
/branches/farewellSwt/user/build
Revision: 6241
Author: j...@google.com
Date: Mon Sep 28 16:56:34 2009
Log: Add -web to Selenium and RemoteWeb tests (otherwise the browsers have
to have
the OOPHM plugin).
Patch by: jat
Review by: fabbott (TBR)
http://code.google.com/p/google-web-toolkit/source/detail?r=6241
Modified:
/bran
Okay, I've made these code changes. New patch coming soon.
What shall we do about -resources? Is it okay to make it a no-op
immediately, or should we continue to support it a little while longer?
http://gwt-code-reviews.appspot.com/69801/diff/1001/2022
File
dev/core/src/com/google/gwt/core/e
Revision: 6240
Author: fabb...@google.com
Date: Mon Sep 28 13:22:48 2009
Log: Reversion of one line of r6234; it introduced some dev test failures
by putting the binary bin-test path ahead of the source; ClassPathEntryTest
and ResourceOracleImplTest look at the first matching classpath entry (
Revision: 6239
Author: fabb...@google.com
Date: Mon Sep 28 12:14:04 2009
Log: Ant fix; junit.stop.build should be set by the junit.failure property,
not whatever property is named by its ${junit.failure} value. Up-merge
from r6234.
Review by: amitmanjhi
http://code.google.com/p/google-web-to
Revision: 6238
Author: kpro...@google.com
Date: Mon Sep 28 10:53:24 2009
Log: Undoing an inadvertent (albeit inconsequential) change to
Showcase.gwt.xml.
http://code.google.com/p/google-web-toolkit/source/detail?r=6238
Modified:
/branches/crawlability/samples/showcase/src/com/google/gwt/s
On Mon, Sep 28, 2009 at 1:39 PM, wrote:
>
> I'll rename everything to "compile report". The command-line option
> would also be good to update, but I don't have any ideas about what to
> change it to at the moment.
>
Maybe -soyc => -compileReport or maybe just -report?
--~--~-~--~~-
Revision: 6237
Author: jlaba...@google.com
Date: Mon Sep 28 10:40:06 2009
Log: Adding recent merge into branch-info.txt.
Patch by: jlabanca
http://code.google.com/p/google-web-toolkit/source/detail?r=6237
Modified:
/branches/snapshot-2009.09.23-r6200/branch-info.txt
Reviewers: kathrin,
Message:
Thanks, Kathrin!
I'll rename everything to "compile report". The command-line option
would also be good to update, but I don't have any ideas about what to
change it to at the moment.
Some quick responses are below. I'll go through your review more
carefully as so
Revision: 6236
Author: jlaba...@google.com
Date: Mon Sep 28 10:38:32 2009
Log: Merging tr...@6234:6235 into this branch.
- Fixes an NPE in JUnitMessageQueue when a test times out before any client
retrieves it.
svn merge -r6234:6235 https://google-web-toolkit.googlecode.com/svn/trunk .
http:/
Revision: 6235
Author: jlaba...@google.com
Date: Mon Sep 28 10:31:06 2009
Log: Fixed a possible NPE that can occur if a test times out before any
clients retrieve the test.
Patch by: jlabanca
Review by: jat
http://code.google.com/p/google-web-toolkit/source/detail?r=6235
Modified:
/trunk/u
This looks great! It looks good to me, but there are a couple of things
I would think about:
1) Right now, the dashboard gets created only if users do NOT use the
detailed stories, but otherwise by default. Is this what we want, and
if yes, we need to make sure users know what their options are.
LGTM.
On Mon, Sep 28, 2009 at 9:09 AM, Freeland Abbott wrote:
> Amit, one part of the same fix from farewellSwt that I think we want in
> trunk "early". It shouldn't cause upmerge issues, and seems important:
> Index: common.ant.xml
>
Amit, one part of the same fix from farewellSwt that I think we want in
trunk "early". It shouldn't cause upmerge issues, and seems important:
Index: common.ant.xml
===
--- common.ant.xml (revision 6233)
+++ common.ant.xml (working co
Revision: 6234
Author: fabb...@google.com
Date: Mon Sep 28 08:46:02 2009
Log: Ant fixes to make test failure correctly blocking, and to cover the
core/*,oophm/* pattern in dev more properly. TODO to remove that part once
core & oophm merge, and there's (normatively) just src, super, test.
Re
LGTM
On Mon, Sep 28, 2009 at 8:17 AM, wrote:
> Reviewers: amitmanjhi,
>
> Description:
> Two changes:
> 1. test failures were non-halting because we want the property named
> junit.failure, not the property named by the contents of
> ${junit.failure},
> 2. moved the dev classpaths (core/*, oophm
Reviewers: amitmanjhi,
Description:
Two changes:
1. test failures were non-halting because we want the property named
junit.failure, not the property named by the contents of
${junit.failure},
2. moved the dev classpaths (core/*, oophm/*) into dev's
rather than global.
Please review this at htt
Revision: 6233
Author: j...@google.com
Date: Mon Sep 28 07:44:53 2009
Log: Update properties on new files added in merge, somehow got dropped.
http://code.google.com/p/google-web-toolkit/source/detail?r=6233
Modified:
/changes/jat/noswt-merge6200/samples/mail/war/default_photo.jpg
/changes/j
Revision: 6232
Author: kpro...@google.com
Date: Mon Sep 28 07:22:01 2009
Log: Adding additionl HtmlUnit dependencies to gwt-servlet.jar
http://code.google.com/p/google-web-toolkit/source/detail?r=6232
Modified:
/branches/crawlability/servlet/build.xml
===
Actually, can I at least ask for a cross-posting here? I would very much
like to know if there are common cases that get broken by the new layout
system, and this seems like a pretty important one. I don't actually know
much about how maps tends to initialize itself, but I'll keep an eye on this
th
Also, this discussion would be more appropriate for the gwt-google-apis
group. GWT contributors is for the developers of the Google Web Toolkit core
product.
On Mon, Sep 28, 2009 at 10:13 AM, Eric Ayers wrote:
> Have you tried the method map.checkResizeAndCenter()?
>
>
> On Mon, Sep 28, 2009 at
Have you tried the method map.checkResizeAndCenter()?
On Mon, Sep 28, 2009 at 9:42 AM, jd wrote:
>
> Actually I think that was a red herring - setting the parentElem style
> just forced a re-render and changing the map size had the same effect.
>
> I think the problem is due to the map trying to
Revision: 6231
Author: kpro...@google.com
Date: Mon Sep 28 07:05:23 2009
Log: Updates to CrawlServlet (throws another exception) and Showcase
eclipse project.
http://code.google.com/p/google-web-toolkit/source/detail?r=6231
Modified:
/branches/crawlability/eclipse/README.txt
/branches/cra
Actually I think that was a red herring - setting the parentElem style
just forced a re-render and changing the map size had the same effect.
I think the problem is due to the map trying to initialize itself
before layout() is called. If I add a holder panel like this:
SimplePan
I have found the issue and am not sure how to fix it using the current
API. After setting 100% height and width on both the DockLayoutPanel
and RootLayoutPanel the map still reported a span of 0 and did not
render correctly. In Safari's Inspector I could see that the only
element without 100% he
Hi,
I am trying to use the new DockLayoutPanel with a Google map in the
center panel which takes up what ever space remains. The map does not
render properly due to not being able to figure out its dimensions. I
have modified the sample below to demonstrate this by adding a map
with 100% height
30 matches
Mail list logo
