-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated GWT Widgets are not IsEditor #57
Comments
I'm having a similar problem. I'm interested in any possible solution. Thanks |
What do you guys suggest for implementing IsEditor? not all polymer widgets are thought for storing values, and some of them could store more than a value. |
Hi Manolo, I think that we can't really understand if a web-component is also an Editor and which kind of Editor. May be the best way is a command-line switch where, during the generation phase, we can set the kind of Editor, may be an "IsEditor<ValueBoxEditor>" or a ListEditorWrapper. What do you think ? |
We will discuss this for a future version, but not before we listen to community about the tendency on using Elements vs Widgets. It seems that GWT is encouraging the use of them instead of widgets, etc. |
In GWT we have only the Editor framework which does a correct databinding between POJOs and Widgets.
I've tried with no success Errai Databinding, to simplistic for a complex interface.
Unfortunately generated widgets are Panels, and as such they don't implement IsEditor interface, which is what the Editor framework uses for integration between generated Autobeans and Wdgets.
I would like the generator to change how it works so that we obtain Widgets compatible with it.
In case I can contribute, but I need to know if you have any suggestions for this.
Thank you.
The text was updated successfully, but these errors were encountered: