search

manolo / gwt-api-generator

Generator for creating GWT JSInterop clients from Polymer Web Components
Apache License 2.0
50 stars 24 forks source link

Generated GWT Widgets are not IsEditor #57

Open masini opened 8 years ago

masini commented 8 years ago

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.

knives85 commented 8 years ago

I'm having a similar problem. I'm interested in any possible solution.

Thanks

manolo commented 8 years ago

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. A very simple solution could be consider only widgets having the getValue() method. Could you write a bunch of examples of the widgets modified so as they work for you? for instance modify PaperInput, PaperSlider. Another possibility is that you override each class with your own implementation. thoughts ?

masini commented 8 years ago

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 ?

manolo commented 8 years ago

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.