Hello John.
I'm glad to see that PagingScrollTable will make it to the GWT trunk.
Even now it is a useful widget but I can't wait to see the final
version. I would like to ask a few questions. I am sorry to hear that
the incubator will be shut down. I was wandering what (if anything)
will replace
Hi,
is there a workaround for :
public void onModuleLoad() {
LayoutPanel panel = new LayoutPanel();
panel.add(new Button(Hello!));
RootLayoutPanel.get().add(panel);
}
left: 0px; right: 0px; together do not work in Firefox 3.5.6 (top:
0px; bottom: 0px; work).
There is also the
Revision: 7434
Author: b...@google.com
Date: Wed Jan 20 07:00:41 2010
Log: Create 1/19 snapshot branch as a straight copy from tr...@7432.
http://code.google.com/p/google-web-toolkit/source/detail?r=7434
Added:
/branches/snapshot-2010.01.19-r7432
--
Revision: 7435
Author: b...@google.com
Date: Wed Jan 20 07:07:54 2010
Log: Add branch-info.txt file.
http://code.google.com/p/google-web-toolkit/source/detail?r=7435
Added:
/branches/snapshot-2010.01.19-r7432/branch-info.txt
===
--- /dev/null
+++
On Wed, Jan 20, 2010 at 6:52 AM, monkeyboy dilbert.elbo...@gmail.comwrote:
Hello John.
I'm glad to see that PagingScrollTable will make it to the GWT trunk.
Even now it is a useful widget but I can't wait to see the final
version. I would like to ask a few questions. I am sorry to hear that
Agreed that this is a really irritating bug in Firefox. Have you tried
w/h:100% just on the button itself? This is required for table and
iframe on all browsers, though it's not baked into the Layout code by
default, because it mis-lays-out slightly (pushes borders and margin off the
edge).
On
Comment by dkimmig:
I dont know whether this is the right time/place to add my comment, but I
would like to point you guys in the direction of the Dojo Data Grid. I
would love to be able to create a Databound-Grid somewhat similiar to the
following way that is currently available in Dojo:
Comment by dkimmig:
I dont know whether this is the right time/place to add my comment, but I
would like to point you guys in the direction of the Dojo Data Grid. I
would love to be able to create a Databound-Grid somewhat similiar to the
following way that is currently available in Dojo:
Comment by dkimmig:
I dont know whether this is the right time/place to add my comment, but I
would like to point you guys in the direction of the Dojo Data Grid. I
would love to be able to create a Databound-Grid somewhat similiar to the
following way that is currently available in Dojo:
Hi,
setWidth(100%) without any margin or border works
I was hoping there would be a custom css property that could fix that.
Thanks,
George.
On 01/20/2010 05:27 PM, Joel Webber wrote:
Agreed that this is a really irritating bug in Firefox. Have you tried
w/h:100% just on the button itself?
Comment by dkimmig:
I dont know whether this is the right time/place to add my comment, but I
would like to point you guys in the direction of the Dojo Data Grid. I
would love to be able to create a Databound-Grid somewhat similiar to the
following way that is currently available in Dojo:
Then, how about a list of new features in the trunk since the last
release. That way developers would know if they should become involved
in the nontrivial (but not too hard) task of compiling GWT from
source. I take the last comment back if such a list exists. I could
not find it.
Regards.
On
Libraries and widgets that we want to incubate will be moved into separate
projects. Instead of downloading one incubator jar, you'll be able to (have
to) download each project individually. Like Ray said, we're going to
commit most new features directly to trunk, but we may still want to
Can you explain why (A, B)() would have a different thisness than B()
?
http://gwt-code-reviews.appspot.com/132815/diff/1/2
File dev/core/src/com/google/gwt/dev/js/JsStackEmulator.java (right):
http://gwt-code-reviews.appspot.com/132815/diff/1/2#newcode719
Line 719: // Don't modify invokees,
Thank you John for your explanation. Now I understand the reason why
you are shutting down the incubator. What I am suggesting is that
developers should have a place where they can see what new features
(libraries,...) are being developed and not to stumble upon this new
features by chance (like I
Reviewers: Dan Rice,
Description:
JreDocTool generates the JRE emulation reference as an HTML fragment.
It currently prints the HTML to stdout; this version writes to a file
(specified by -out) instead.
Please review this at http://gwt-code-reviews.appspot.com/130816
Affected files:
Sorry, I wrote that up and then it disappeared during editing. The way
I expected foo.bar() to work is that foo.bar would give you a closure
specifying this=foo. JavaScript is full of creative approaches,
however. The way it actually works is that JavaScript looks at the
syntax of foo.bar and
Sam, for whatever reason, the stack emulator adds a line-number marker
for foo[bar] but not for foo.bar. At a guess, this is because with
foo[bar], bar can potentially be a complicated multi-line expression.
At any rate, it looks like a separate issue from issue 4512, though.
Reviewers: jgw,
Description:
The SuggestBox loses focus when the mouse hovers over the list of
suggestions because MenuBar steals keyboard focus on hover. This is
particularly annoying if a user leaves the cursor just beneath the text
box. As soon as the suggestions are shown, the text box
Revision: 7436
Author: sp...@google.com
Date: Wed Jan 20 12:24:08 2010
Log: Merge r7343 from trunk. Has arrays implement Serializable.
svn merge --ignore-ancestry -c 7343
https://google-web-toolkit.googlecode.com/svn/trunk .
Since JsArrayAccess and JsNameRef have such similar semantics, I'd be a
little suspicious of any solution that doesn't handle the two similarly,
especially since both can be multi-line. (foo.\nbar is legal).
Handling the two differently means that it's more likely that were
hiding subtle bugs,
Reviewers: jlabanca,
Please review this at http://gwt-code-reviews.appspot.com/132817
Affected files:
M user/src/com/google/gwt/user/client/ui/SplitLayoutPanel.java
M user/src/com/google/gwt/user/client/ui/StackLayoutPanel.java
M user/test/com/google/gwt/user/UISuite.java
A
These ideas sound good to me, Sam, but shall we fix the immediate
problem before getting into them?
There are only two places I'd quibble with your suggestions:
1. The current patch intentionally avoids rewriting things like foo()()
and (new Foo())(). Your proposal #1 is to rewrite in such
LGTM
Will these tests break in quirks mode? Our build system currently tests
most things in quirks mode.
http://gwt-code-reviews.appspot.com/132817
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Sam points out to me that delete foo needs the same care that foo()
gets.
http://gwt-code-reviews.appspot.com/132815
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
25 matches
Mail list logo
