Skip to content

Conversation

@anton-johansson
Copy link
Contributor

Because the MaterialTextBox doesn't extend the GWT standard TextBox, but
we still want to provide the same possibilities as the TextBox has, we
need to implement all the interfaces that TextBox does and redirect the
methods to the internal TextBox.

Also, the inner components should be protected instead of package
private, to expose them to extensions.

Because the MaterialTextBox doesn't extend the GWT standard TextBox, but
we still want to provide the same possibilities as the TextBox has, we
need to implement all the interfaces that TextBox does and redirect the
methods to the internal TextBox.

Also, the inner components should be protected instead of package
private, to expose them to extensions.
@anton-johansson
Copy link
Contributor Author

I came across this flaw when I tested out stephenh/tessell, a data binding library for GWT. I couldn't do any bindings what so ever with MaterialTextBox.

kevzlou7979 added a commit that referenced this pull request Jul 3, 2015
Expose same functionality in MaterialTextBox as TextBox
@kevzlou7979 kevzlou7979 merged commit 1aa1f04 into GwtMaterialDesign:master Jul 3, 2015
@masterdany88
Copy link

masterdany88 commented Jul 7, 2016

I have compilation error: Could not find a getter for path asTextBox in proxy type java.lang.String and I wonder is it related to this merge? Error occured after changing up the version from 1.5.1 of gwt material to 1.6.0-Snapshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants