That site runs on a GWT app built from Google's internal Bazel BUILD rules,
not from the open-source Maven pom-gwt.xml...
On Sunday, December 20, 2015 at 8:13:24 AM UTC+8, Thomas Broyer wrote:
>
>
>
> On Saturday, December 19, 2015 at 5:09:23 PM UTC+1, Michael Zhou wrote:
>>
>> Well there's a .no
I have content that goes under the TabPanel. (a StackLayoutPanel actually),
so a scroll bar inside does not solve an issue like that.
My question isn't necessarily aimed to solve that particular problem, but
to understand the way the LayoutPanels are suppose to be used to create an
app. The ve
I have content that goes under the TabPanel. (a StackLayoutPanel actually),
so a scroll bar inside does not solve an issue like that.
My question isn't necessarily aimed to solve that particular problem, but
to understand the way the LayoutPanels are suppose to be used to create an
app. The ve
Basically ScrollPanel has an internal div element (the "scollable" element)
that does not have any height. That is generally fine because the
scrollable area should adapt to the size of its single child but that also
means you can not use "height:100%" for the child (percentages require
height
I've been reading a lot about the LayoutPanels introduced in 2.0 and trying
to understand their purpose. I keep seeing that I should be using these
instead of the older panels, but they seem way more complicated and
limiting.
Take my app, for example. It's got a straight forward interface: A fi
On Monday, December 21, 2015 at 2:12:50 PM UTC+2, Paul Robinson wrote:
>
> You appear to be adding an item without also creating that item. That
> suggests the item already exists, and is possibly already displayed. You
> can't have the same widget appearing more than once. That may be your
>
You appear to be adding an item without also creating that item. That
suggests the item already exists, and is possibly already displayed. You
can't have the same widget appearing more than once. That may be your
problem.
Paul
On Mon, Dec 21, 2015 at 9:02 AM, wrote:
> Hello all,
>
> I hav
@ VADIM Thank You!!!
I think I have solved the issue by switching to a pure maven build rather
that using the gwt plugin.
I think having multiple projects using multiple JDK. GWT Versions may have
confused Eclipse MARS.
So I refreshed the build into a new directory using:
2.8.0-SNAPSHOT
MAVEN
P
Hello all,
I have a Composite with Widgets that are populated from the
database. Let's assume I need to add new Item object and ID for this
object comes from database after object is persisted on the server. So I
did:
private void addItem(String title, String description) {
Hello Ed,
I am working with polymer elements 1.2.1.0 and GWT 2.8.0-beta1
closely and I found one missing thing at your configuration. Particularly
at your gwt.xml should be:
* *
The problem may be connected to GSS that is switched off by default,
but must be "ON" for
Hello Ed,
I am working with polymer elements 1.2.1.0 and GWT 2.8.0-beta1
closely and I found one missing thing at your configuration. Particularly
at your gwt.xml should be:
* *
The problem may be connected to GSS that is switched off by default,
but must be "ON" for
11 matches
Mail list logo