Furthermore, if you use setChildOpen(false)/setChildOpen(true)
recursively to trigger a data pull and reload of your CellTree, you
will run into this bug:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6246
--
You received this message because you are subscribed to the Google
There is a bug in IE, try this in IE Developer Tools (tried it in IE8, on an
about:blank page):
document.body.innerHTML=span id=foo/span bar
document.body.innerHTML
It'll output SPAN id=foo/SPANbar (notice that the space has
disappeared).
That bug can be worked around though:
This has been driving me nuts for some time and I finally figured out
what I did wrong. Maybe your problem is the same. I was using the
wrong hostname in the URL, i.e. localhost instead of 127.0.0.1.
Explanation:
The GWT-plugin's default URL when launching the app is http://127.0.0.1:/...
so
On Sat, Apr 9, 2011 at 7:54 PM, facundo schwindt facu0...@gmail.com wrote:
Hi everyone
I was developing an app in development mode.
Recently I got a Mac with snow leopard.
The app run perfectly in Windows7. But I've imported the project into
workspaces in Snow Leopard OS and when I try
On Mar 17, 3:28 pm, Jake Wharton jakewhar...@gmail.com wrote:
Is this possible using the editors as well?
When you flush the driver you get a RequestContext whose fire() only accepts
a ReceiverVoid.
Hi,
Did you find any solution for that?
I'm facing the same problem now in which I would like
The flush returns whatever was passed to edit() so it can be cast back to
the right type. You can also keep the context that is passed to edit() in
an activity and then simply re-use it.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To
No opinion or experience of production of one of theses solutions ?
Thanks for any help
On Apr 8, 8:36 am, Rodolphe Gomes rodolphe.go...@gmail.com wrote:
I am talking abouthttp://puremvc.org/(NOT the concept MVC).
There is a sample
I use MVP as described here
http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html
together with RF
http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.html and
editors http://code.google.com/webtoolkit/doc/latest/DevGuideUiEditors.html
So far there
java.lang.AssertionError: The style name 'margin-top' should be in
camelCase format
at com.google.gwt.dom.client.Style$.assertCamelCase$(Style.java:63)
at com.google.gwt.dom.client.Style$.setProperty$(Style.java:42)
at
In version gwt 1.5.2 I used margin-top, my application runs well.
So after upgrading to gwt 1.6.4, If I still use margin-top, apart
from the error message (AssertionError), isn't my application
affected ?
On Apr 11, 4:10 am, Paul Robinson ukcue...@gmail.com wrote:
java.lang.AssertionError: The
If anyone is interested, my approach was all wrong. Much better to disable
the windows scroll panels Window.enableScrolling(false); and then
use ScrollPanels (that resize to the window). That way the ScrollPanels
scroll bars will actually get disabled properly, and you can put
a ScrollPanel
-- Forwarded message --
From: jtuchsche...@gmail.com
Date: Sun, Apr 10, 2011 at 00:13
Subject: Trying to address issue 6234 (Support RequestFactory service
inheritance on the client) (issue1411802)
To: jtuchsche...@gmail.com
Cc: google-web-toolkit-contributors@googlegroups.com,
See my comments here http://gwt-code-reviews.appspot.com/1384802/ and
here
http://code.google.com/p/google-web-toolkit/issues/detail?id=5807#c3
In brief:
- there has to be an annotation added to these specific RequestContext
interfaces (also, they might not extend RequestContext and they don't
I followed the approach from the SafeStyles for the checks in the
generator, with the exception that I log a warning rather than throw
when a SafeUri is used outside a URL attribute context.
I updated the ClippedImageImpl's internal SafeHtmlTemplates so it
doesn't log such a warning, and fixed a
I think this is pretty much ready, except for one thing I just thought
of. Sorry, I should have thought of that earlier :/
In ClippedImageImpl, we're using a SafeUri in the context of a url()
style expression (background: url({3})). However, the contract of
SafeUri is currently not tight enough
On 2011/04/10 18:32:38, xtof wrote:
I think this is pretty much ready, except for one thing I just thought
of.
Sorry, I should have thought of that earlier :/
In ClippedImageImpl, we're using a SafeUri in the context of a url()
style
expression (background: url({3})). However, the
Reviewers: jat, skybrian, rjrjr, bobv,
Description:
First change for GWT end-to-end testing framework.
Please review this at http://gwt-code-reviews.appspot.com/1408803/
Affected files:
A user/src/com/google/gwt/testing/Testing.gwt.xml
A user/src/com/google/gwt/testing/client/After.java
17 matches
Mail list logo
